Junior QA Engineer (Platform & Analytics)

About the role

This is the QA position for the whole development team. Whatever gets built here passes through you before it reaches a user or a dollar of traffic: a new feature on the dating platform, a fix in the payment flow, a change to the event map, a landing page for a campaign that launches tomorrow.

The breadth is deliberate. In a traffic team the failures do not respect team boundaries: a bug in the registration form and a tracking event that fires twice cost exactly the same thing, which is spend against a funnel that does not work. Splitting those between different people usually means both get checked halfway.

ROIcamp has worked in the dating vertical since 2011. You report to the Tech Lead and work alongside the developers, the analyst and the buying team. This is a junior position, but not a zero-experience one: we are looking for someone who has already tested web products or worked inside ad accounts.

What you’ll do

• Test what the dev team ships: new features and fixes on the platform, covering registration, profiles, matching, messaging, settings and the admin panel. You check before the release, not after a complaint.
• Verify the event map: that every event fires exactly once, at the right moment, with a complete set of parameters, and reaches the pixel, the Conversion API, the tracker and GA4 alike.
• Follow parameters end to end through click, landing, registration, subscription and payment, checking that the subid survives every step. A subid is the identifier that ties a conversion back to a specific buyer and campaign.
• Reconcile numbers between the ad account, the tracker and the BI dashboard, find the source of any discrepancy, and describe it so an engineer reproduces it on the first read.
• Test landings and prelanders before traffic goes live: layout, loading speed and forms across devices, browsers and GEOs. A prelander is the short intermediate page between the ad and the main offer page.
• Check the advertising side before a launch: campaign links and their tags, redirects, rotation rules, and deeplink transitions into the app.
• Test the marketing pages across languages, since a broken layout or an untranslated block in one locale stays invisible until traffic hits it.
• Occasionally help run down a user report, when reproducing it is the fastest route to the bug. This is a small part of the job and we intend to keep it that way.
• Grow the test matrix: every bug that gets through becomes a new line in it.

Requirements

• Around a year of web testing experience, or an adjacent role where you regularly investigated why data did not add up.
• Hands-on exposure to advertising: you have seen an ad account from the inside and understand where a conversion in a report comes from.
• Confident use of DevTools: the Network tab, reading requests, parameters, cookies and redirect chains.
• A grasp of basic web mechanics: GET and POST, query parameters, response codes, and the difference between a client-side and a server-side event.
• Willingness to read JSON without hesitation and to write findings up in a structured way rather than as “something is broken”.
• Comfort switching context. A day can move from a platform release to a tracking check to a landing page, and that rhythm has to suit you.
• Consistency: the test matrix gets completed even when everything appears to be fine.

Nice to have

• Google Tag Manager and GA4, either configured yourself or at least understood well enough to read someone else’s container.
• Experience with a tracker such as Keitaro, Binom or any equivalent.
• Postman or a similar tool for checking postbacks and API responses by hand.
• Basic SQL, enough to pull a number from a table yourself instead of asking the analyst.
• An understanding of mobile attribution and mobile measurement partners such as AppsFlyer.
• English sufficient for reading platform documentation.

What we offer

• Unusual breadth for a junior role. Within a year you will have worked across the product, the tracking, the advertising and the analytics, which is a rare vantage point and the reason people move up quickly from here.
• Work on live systems rather than a training environment: real volumes, real GEOs, real event counts.
• Direct access to the Tech Lead, the developers and the analyst, so questions get settled in one message rather than three approvals.
• A visible result: you can see how much budget a broken event you found protected.
• Fully remote work, full salary from day one, and payouts on a fixed date.

Growth path

Three directions open from here, and the breadth of the role means you will have seen enough of each to choose honestly. Deeper into QA toward the middle level and the automation track. Toward the tracking infrastructure engineer, who designs the event map instead of checking it. Or into marketing analytics, since you work with the same cohorts as the BI analyst, only from the other side. We discuss all three at the six-month review and measure them by results rather than by tenure.

Compensation

$300 to $500 base, depending on how independently you can work from the start. Salary review after six months. Payouts on a fixed date each month.

Hiring process

A 30-minute screening call, then a practical task on a test landing page with broken tracking (up to two hours, reviewed together), then an interview with the Tech Lead, then an offer. The whole process takes up to 8 business days from your application.