In the last three years "growth engineer" turned into a job title, and most of the people holding it are growth marketers with a database credential. The salary band moved; the deliverable did not. So here is the one question that separates the two roles faster than any portfolio review or take-home test:
"What will I be able to open when the month is over?"
A marketer will name things you receive: a plan, a content calendar, a report, a channel audit. An engineer will name things that exist: the page, the event in the analytics property, the sequence that is still sending, the repository where the tooling lives, the sending domain with its DNS records. Deliverables you receive can end with the invoice. Artifacts you own keep running without the operator.
That difference is not philosophical, it is a line item in the contract. Here is how to price it.
The four things a growth engineer leaves behind
| Growth engineer | Typical agency / growth-marketer model | |
|---|---|---|
| Deliverable | A live path with a measured event | A campaign, a plan, a deck |
| After the engagement | The asset keeps running in your accounts | Activity stops with the invoice |
| How you audit a month | The artifact you can open | The report they wrote |
| Who owns the tooling | You — built inside your own accounts | Usually the agency |
| First question asked | "Where is the bottleneck?" | "What is the budget?" |
Both models are legitimate, and they buy different things. Hire a marketer when the path exists and only needs more volume pointed at it. Hire an engineer when the path itself is the problem.
Where the bottleneck usually is
Four of the five cases below are not traffic problems, and buying traffic for them makes the disappointment arrive faster:
- Nothing is instrumented. Emails go out, pages exist, and no event records a conversion. The first deliverable is one event and one analytics property, otherwise every later decision is an opinion.
- The offer, not the channel. Wiring more traffic into a page nobody wants to enter is the most expensive way to avoid rewriting the page.
- Numbers too small to read. Two variants, forty sends, and a confident conclusion. A two-variant test needs a send count computed before the test, not a vibe check after it. There is a free email test planner that returns the required sends for the effect size you claim to be chasing — it runs in the browser, no account, no email gate.
- Tests with no kill rule. A test without a stop rule is not a test, it is a subscription. The kill-rule calculator applies the Wilson interval and the rule of three so "it is working" has a floor under it before you scale it.
- Pages that answer engines cannot quote. Crawlers reward the same things readers do: a direct answer near the top, structure, dated numbers, something checkable. The 23-point AEO readiness checklist scores a page on exactly that.
All three tools are static pages, MIT-licensed, and part of Marketing Mindset — a skill that teaches an AI agent how a marketer decides, which is the other half of the job now.
What "measured" actually means
An event that fires is not measurement. Measurement is an event with a denominator: sends, sessions, or accounts touched — plus the sample size that makes the numerator readable. The honest version of a weekly update reads either
41 replies from 1 200 sends, 95% CI [2.5%, 4.6%], two variants still running
or
not enough data yet, the test needs 380 sends per arm and has 120
Both are useful. "Engagement is up" is neither.
What a month should leave in your accounts
- The entry point — landing page, form, inbox or sending domain — built, not described.
- The sequence behind it, with a current owner and a documented failure mode.
- One conversion event wired to one analytics property you control.
- A written kill-or-scale rule, agreed before the first send: how many data points, what result stops it, what happens to the winner.
- The tooling in your repository, not in someone's private workspace.
If a proposal cannot be reduced to those five, the title on the contract is doing work the deliverables are not.
The check before you pay
Every line above is testable before a contract exists. My own artifacts are published rather than described: proof page with live links, the difference between a growth marketer and a marketing engineer, and the packages with prices on them — Sprint $900, Engine $1,900/month, full build $2,900 — published before the first call. The growth engineer for hire page is the long version: what one path, one number and one kill rule cost.
Ask the question at the top of this post in your next three conversations with candidates. The answer you get back will tell you which column you are buying from — and whether the person in front of you has ever had to live with a number they shipped.
Top comments (0)