Most JDs for this role are a marketer's JD with "engineer" typed over the title — and then the hire fails in month three because nobody wrote down what should exist at the end of it. Pick the level and the surface, and this generates the version that names artifacts, numbers and kill rules instead of "passion for growth".
Copy this into your hiring doc. It states numbers and artifacts on purpose: the wrong candidates self-select out before the first call.
| Question to ask | Marketer's answer | Engineer's answer |
|---|---|---|
| What can I open when the month is over? | A plan, a calendar, a report | URLs, events, accounts, a repo |
| How many sends does an email test need? | "Depends on the audience" | ~1,500–2,000 per variant for a 3% baseline and a 20% lift |
| When do you kill a channel? | After a review | When the volume is met and conversions are at or under the floor |
| Who owns the tracking? | "Our analytics person" | "I instrumented it; here is the event" |
The numbers above are the same floors the free test planner and the kill-rule calculator compute in the browser.
The same work is available as a fixed package: what a marketing engineer does, Sprint $900 / Engine $1,900 per month / Full build $2,900, and what to check before you pay a retainer. Tool, method and case pages are all linked from the agent-readiness checklist.
Related free tool: llms.txt generator — the file that tells models what the site answers and which pages are canonical.
Also: Service / Offer schema generator — copy-ready Service + OfferCatalog JSON-LD with the price, url and description checks.
Also: UTM + GA4 event naming builder — the tagged url and the event name that ends a test, with the checks that decide whether the number is readable.
Also: AI crawler robots.txt generator — who may cite you and who may train on you, written as robots.txt groups you can paste.
Also: A/B verdict calculator — was the difference separated from zero, and was the volume ever above the floor the observed lift needs?
Also: honest test queue planner — turn volume into a queue: the floor per arm, the days each test needs and the day each verdict lands.
Also: what one honest test costs to finish — the contacts a verdict needs, the days it takes and how many funded tests a budget carries.
Also: which step of your funnel can fund a verdict — the floor, the events each arm sees in a month, and the months a readable unit takes at your volume.
Also: which of your channels can actually fund a verdict — floor per arm, months to verdict, the cost of one full two-arm test and the channel to run first at your volume.