Careers /

Tech Lead — Tracking & Infrastructure

$2,200–3,200Remote

Apply ↓

About the role

When postbacks go down at night, buyers spend the morning flying blind — and every hour without data burns real budget. That is why this role is not “tracker admin” but the owner of the entire buying-side stack: Keitaro/Binom, S2S postbacks, domains, servers, landings, and integrations with a product that has run in dating since 2011. The product side already exists; the new department’s tracking stack is yours to design and deploy from scratch, with the freedom to pick the tools and the accountability that comes with it. You report to the Head of Media Buying.

The scale is honest: one buying team and moderate volumes at the start, millions of events a month within a year or two. What we value is not “configured it quickly” but an architecture that survives a tenfold increase without a rewrite. There is zero legacy in your zone — the first technical decision here will be yours. And every piece of the stack has a direct price tag: an extra second of landing load eats conversion, a lost postback is someone’s bonus, a redundant redirect is a percentage of traffic gone.

What you will do

  • Design and roll out the tracking stack: tracker, traffic distribution, S2S postbacks to the product — architected for millions of events a month.
  • Wire the postback chain so every funnel step — click → registration → subscription → rebill — reaches the tracker without loss.
  • Run domain infrastructure: registration, DNS, SSL, landing and prelander rotation, speed, fault tolerance.
  • Integrate ad-source APIs and internal systems: automated stats, cost sync, exports into BI.
  • Build monitoring and alerting so a postback outage pings you first — not a buyer at breakfast.
  • Automate buyer routine: landing deploys, account infrastructure, small scripted tools the team uses daily.
  • Guarantee data integrity together with the analyst: tracker numbers must match the product to the cent — open buyer bonuses are computed from them.
  • Document the stack: diagrams, runbooks, procedures — so the system does not live only in your head.

What matters to us

Required:

  • Tracker administration (Keitaro / Binom) at real volumes, not on a demo.
  • S2S postbacks, API integrations, webhooks — you can debug a chain where “the conversion went missing”.
  • Domains, DNS, SSL, Linux servers, basic CDN.
  • Scripting (PHP / JS / Python) at the level of “ship a tool the team actually uses”.

Nice to have:

  • Time inside a traffic team or CPA network.
  • Anti-detect infrastructure and proxies.
  • Cloudflare Workers, automated landing deployment.
  • A monitoring stack: Grafana, uptime bots, messenger alerts.

What you get

  • A stack you choose yourself and answer for yourself — a rare setup for a senior engineer.
  • Fully remote, with no office timezone to orbit.
  • Backup from product engineers with 15 years of expertise instead of “figure it out alone”.
  • Budget for servers, services and licenses — defended with numbers, approved fast.
  • Salary on a fixed date, reliably.

Growth track

Solo tracking owner → Tech Lead hiring into your own area as the department grows → technical head of the whole buying infrastructure. The stack scales with volume — and so does your role. Year one is maximum engineering and minimum management: a rare mode for someone who wants to build rather than coordinate.

Compensation

$2,200–3,200 base. Payouts on a fixed date.

Process

30-min screening → technical interview → compact practical task → offer. Up to 10 business days.

Questions about this role

What is already deployed vs built from scratch?

The company product infrastructure has run for 15 years. The new department tracking stack (tracker, postbacks, domains, integrations) you deploy from scratch — with the right to choose tools.

What event volumes are expected?

Moderate at the start (first buying team), scaling to millions of events per month. Architect for growth from day one.

Am I solo or will there be a team?

Year one — you own tracking solo, supported by the company product engineers. As the department grows, we hire into your area.

What about on-call and incidents?

No formal 24/7. But tracking is critical: if postbacks fail at night, buyers fly blind. We build monitoring and alerts so incidents are rare, not a lifestyle.

How free am I in choosing tools?

Almost fully: justify choices with numbers and maintainability. Keitaro/Binom are market-experience recommendations, not dogma.

Apply

We reply within 2 business days — even when the answer is no.