Growth engineer · for hire · fixed packages
Growth engineer for hire
A growth engineer is the person who builds the path and proves whether it works: the capture point, the sequence, the tracking, the sample size, the kill rule. Not a deck, not a channel audit — a working asset with an event attached, inside your own accounts. Packages are published before the call: Sprint $900, Engine $1,900/month, Full build $2,900.
What you actually get
Built, not described
The entry point (landing page, form, inbox, or sending domain), the sequence behind it, and the event that fires when someone goes through. Yours from the first commit.
Measured honestly
A conversion rate with the sample size that makes it readable — or the explicit statement that there is not enough data yet. Most “wins” in this market are sample sizes in disguise.
Kill or scale
A written rule set before the test starts: how many data points, at what result do we stop, what happens to the winner. Decisions made after seeing the numbers are not decisions, they are stories.
Growth engineer vs growth marketer: the test that matters
Ask a candidate what you will be able to open when the month is over. A marketer will name deliverables (a plan, a calendar, a report). An engineer will name URLs, events and accounts: the page, the dashboard, the sequence that is still sending, the repository where the tooling lives. That single question separates the two roles faster than any portfolio review.
| Growth engineer | Typical agency / growth-marketer model | What an engineer leaves behind |
|---|---|---|
| Deliverable | A campaign, a plan, a deck | A live path with a measured event |
| After the engagement ends | Activity stops with the invoice | The asset keeps running in your accounts |
| How you audit a month | The report they wrote | The artifact you can open |
| Who owns the tooling | Usually the agency | You — built inside your own accounts |
| First question asked | “What is the budget?” | “Where is the bottleneck?” |
Both models are legitimate — they buy different things. Hire a marketer when the path exists and needs more volume pointed at it; hire an engineer when the path itself is the problem.
Where the bottleneck usually is
- 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 makes disappointment arrive faster. That work starts on the page and the offer.
- Numbers too small to read. Two variants, forty sends, and a confident conclusion. The free test planner computes the sends a two-variant test needs before the result means anything.
- Tests with no kill rule. The kill-rule calculator returns the Wilson interval and the rule of three, so “it is working” has a floor under it.
- Pages that answer engines cannot quote. The 23-point readiness checklist scores a page on the things crawlers actually reward.
All three tools are free, run in the browser, and need no account.
How the engagement works
One path, live in a week
Pick the broken or unmeasured path; it gets built, instrumented and running. The right first purchase when something is already being sent but nobody can say whether it works.
The continuing block
Build, measure, kill the losers, scale the survivor. Fourteen days notice to cancel, because a retainer you cannot leave is a lease, not a service.
Handed over running
Offer, pages, outbound, measurement and documentation, so the system survives without the operator.
Check the work before you pay for it
- Proof page — every artifact of this engine with a live link.
- What shipped — the same artifacts with dates.
- Cost page — the three packages and the honest comparison.
- AI marketing engineer — the machinery marketing runs on: agent skills, quotable pages, automation and kill rules.
- Marketing engineer services — the seven deliverables, each with something you can open before paying.
- How to become a marketing engineer — five steps, each with something you can open: one channel, a measurement stack, three dated public artifacts.
- Marketing engineer vs freelancer — what you are actually buying: who owns the number, how the work is checked, and what you keep at handover.
- Marketing engineer vs growth marketer — what each role owns by default, the first readable result, and four signs that decide the hire.
- Marketing engineer for agencies — an agency cannot pool its clients' traffic, so every client needs its own floor and its own read-out date: 13,914 per arm (27,828 total), 14 months for a client at 2,000 contacts a month, and 4,638 contacts a month as the smallest client readable inside 6 months. li>Marketing engineer for marketplaces — two funnels that must be readable at the same time, liquidity as the readable unit, why each side needs its own floor (13,914 per arm; 27,828 in total; 70 months for a 400-seller-a-month supply side) and the four decisions taken before the first contact.
- Marketing engineer interview questions — the six questions that separate an engineer from a marketer with tools, what each answer really measures, the volume a verdict needs (13,914 contacts per arm; 27,828 in total), and the four things the interview cannot decide. li>Marketing engineer for devtools — why the readable unit is the first successful call rather than the signup, the volume a verdict needs, and the stop rule that has to exist before the spend.
- Marketing engineer for fintech — why the readable unit sits after identity and funding, the volume a verdict needs, and the stop rule that has to exist before the spend. li>Marketing engineer retainer — the invoice line by line, the four decisions a retainer cannot make for you, and how many honest tests a month can actually hold at your volume.
- Marketing engineer job description — the four decisions and six lines to write instead of a tool list, the artifact due each week, the volume a strict test needs, and a free generator. li>Marketing engineer for B2B — the lead, source and reply definitions that decide whether a channel can be judged, the five things that exist before the first send, and the floor an honest test needs. li>Marketing engineer for SaaS — the five numbers most plans are missing, what gets instrumented first, and what ships in a $900 Sprint.
- Marketing engineer for startups — the three routes a seed-stage team compares, what the first 30 days produce, and the floors the numbers have to clear.
- Marketing engineer for ecommerce — why last-click revenue is not a verdict, the spend gate, and the traffic floors a store test has to clear.
- Fractional marketing engineer — when a monthly seat beats a project.
- Marketing automation engineer — the machinery under the marketing.
- npm: marketing-mindset — the method as a package you can run.
Questions people actually ask
What is a growth engineer?
Someone who ships the machine that growth runs on: the capture point, the sequence, the tracking, the experiment, the kill rule. The difference from a growth marketer is not seniority — it is the unit of output. A marketer delivers a plan and a campaign; an engineer delivers a working path with a number attached, and can show you the page and the event it fires.
How is a growth engineer different from a growth marketer or a growth hacker?
A growth marketer owns messaging and channels and usually needs someone else to build. A growth hacker chases one-off tricks and rarely leaves an asset behind. A growth engineer owns the whole path end to end — page, offer, tracking, sending, measurement — and is judged by whether the path keeps producing after the engagement stops.
What happens in the first week?
The bottleneck gets named in writing, one path gets built and instrumented, and you get the numbers rather than an opinion: what came in, what was measured, what the sample size allows you to conclude. The deliverable of every week is an artifact with an openable link.
How is the engagement priced?
Three published packages, no hourly rate: Sprint $900 one-time for one channel or one path built and live; Engine $1,900 per month for the continuing block (build, measure, kill or scale, 14 days notice to cancel); Full build $2,900 one-time when the whole system has to be handed over running. Details on the cost page.
What can I check before paying anything?
Every artifact from this engine is public: the proof page lists each one with a live link, the cases page carries dates, the free tools are open in the browser, and the packages and the scope are written down before any call. If something in that list does not hold up, walk away.