Junior QA Engineer (Platform & Analytics)

Невідома компанія

Що робити

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.

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".

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