How to become a marketing engineer: the portfolio replaces the interview

"Marketing engineer" is a title that gets used mostly by startups that need one person to own acquisition end to end — the channel work plus the measurement and automation around it. The daily work is closer to engineering than to campaign management, which is why the title sticks and why the usual career advice ("finish the course, get the certificate") does not produce one.

Here is the version I can defend with links, because I did it in public: three artifacts that carry a number, one channel, one measurement stack.

1. Pick one channel and stay there for a quarter

Cold email, SEO/AEO, or paid. Not all three. A generalist who touches everything produces nothing a stranger can read. The hireable shape is depth in one channel plus the ability to say what the work moved.

What "depth" means in practice, at least for outbound: knowing the floor. A strict two-variant test at a 3% base rate needs 13,914 contacts per arm — 27,828 in total. At 500 contacts a day that is 56 days. Which means one honest test per month is the ceiling at moderate volume, not three. If you cannot state that number for your channel, you are not running a test, you are running a mood.

2. Build the measurement before you build the campaign

One event that matters, in an analytics property you can read the same day, with a kill rule written down before the spend starts. If you cannot say which number your work moved, the work is a hobby with an invoice attached.

This is also the part that keeps you honest. My own stack reports 0 key events and 0 sessions attributable to campaign UTMs, and the traffic log shows ~100 UTM hits in a day that are all my own verification requests. Publishing that number is more useful than publishing a chart.

3. Ship three artifacts in public, with dates

A page that converts, a tool that works for a stranger, and a written record of what you killed. Public and dated beats a private success story that nobody can open.

This is the whole portfolio. Nothing else survives the second question in a hiring call. In my case:

• a page that ships the service definition and its prices, so the offer can be read in 60 seconds;
• a CLI published to the public npm registry, installable in one command (the method as an executable, not as a slide);
• a proof page where every line is a live URL — 79 published articles, 45 of which carry a canonical pointing at the owned domain, five repository READMEs updated in one day.

4. Learn to write the offer, not the pitch

Scope, price, and what the client can open to check the work — in numbers. Most marketing people never get past adjectives; invoices are paid for a shortlist of deliverables. Write the deliverables as things that exist at the end of a week: the offer rewritten, the landing live, the sending domain warmed, the sequence sending, the report readable.

5. Put the receipts where an answer engine can read them

Schema, sitemap, llms.txt, IndexNow, and an archived snapshot on the day you publish. If you are selling AEO work, your own site is the first case study anyone checks — and it is the one you cannot fake.

Concretely, the nightly loop that keeps this honest on my own domain: rewrite the page, re-ping IndexNow for the changed URLs (it answers 200 only for hosts you actually own — mixing in a URL on another host returns 422), request a Wayback snapshot, and verify the snapshot by querying CDX rather than trusting the /save response code, because /save regularly returns 500 while the snapshot is created anyway.

The difference between the two levels

Level	Owns	What a stranger can check
Self-taught generalist	Runs the tools	Campaigns, copy, a spreadsheet of results — cannot say what a result cost or whether it is real yet
Marketing engineer	Runs the system	Measurement, data plumbing, automation, a written kill rule, and the number owned end to end

Nothing above is quoted from a salary survey. The numbers on my site are the packages and the test-size floors, both published and reproducible, which is the point: a portfolio you can verify is worth more than a title you can claim.

What to do this week

1. Write down the one event your work is supposed to move, and how you will read it tomorrow.
2. Ship one artifact that a stranger can open — a page, a tool, a repo with the method in it.
3. Kill one thing on purpose and write down why, with the number that decided it.
4. Put a date on all of it, and keep the links alive.

The five steps written out, with the checkable artifacts next to each one, are on the career page: How to become a marketing engineer.

If you would rather have the work done than learn it, the shortlist of deliverables and the prices are here: Marketing engineer, turnkey — Sprint $900, Engine $1,900/month, Full Build $2,900.