Senior Data Engineer, Pipelines and Data Quality

About GetHookd

GetHookd is an ad intelligence platform. Marketers and e-commerce teams use it to search a library of more than 20 million ads, follow competing brands and shops, and turn what works into their own creative. The same data is open to AI agents through a public API and an MCP server. The engineering team is growing to eight engineers and a QA lead.

Why this role exists

Our product is only as good as its numbers: how many ads a brand is running, since when, in which countries, and how each ad performs. Those numbers are collected all day from sources we do not control, then processed into a database and a search index. You will own making every number match its source and be defined once.

What you will own

• Whether our numbers match the source: automated checks against the source, an alert when a count moves away from it, and the fix.
• One written definition for each shared number, such as „active ad“, used alike by the app, the API and the search index.
• The processing pipeline: the queue jobs that turn collected data into what customers see.
• Backfills on a table of over 200 million rows, which you write and the reliability engineer approves.
• Test data for agents: with the reliability engineer, production-sized read-only data that our coding agents can check their work against.

You report to the head of engineering.

What we look for

• You have owned data pipelines in production where correctness was measured against an outside source.
• Strong SQL on large tables. You know what a query costs before you run it, and how to backfill without locking.
• You have built queue jobs that are safe to retry.
• You work in TypeScript or PHP today and can review the other.
• You use coding agents every day, and you check their output against real data, not sample data.
• Good to have: large-scale ingestion from sources you do not control (rate limits, retries, formats that change without notice), Laravel Horizon, serverless platforms, Typesense or Elasticsearch, MySQL 8 internals.

How we work

Coding agents write most of our code, and about 40 changes merge every day. Engineers here do what an agent cannot: decide what to build, write the specification, set the checks, review what matters and confirm the result in production. If your satisfaction comes from the outcome more than from typing the code yourself, you will like it here.

What We Offer

• Hybrid: week 1 in-office, then Mon–Wed office / Thu–Fri remote
• 20+ days paid leave, growing with tenure
• Private health insurance and an optional sports card
• Real product ownership. No red tape. No fluff.
• A small, honest team that ships things that matter

The Process

Four steps, two weeks total:

• a short written screen (3 questions, 20 minutes)
• a technical conversation including a review of a real endpoint or MCP tool from our codebase
• a technical assesment
• and a founder conversation.

Happy to hear from you!