Growth Engineer
The marketing site is live and the waitlist is the audience the product will launch to. This role exists to grow it: programmatic pages that deserve to rank, free tools worth a bookmark, and measurement that respects the visitor. The honest-marketing constraint isn't a limitation on this job; it's the reason the job works.
- Remote · US & Canada
- SEO
- Analytics
- Conversion
- TypeScript
The work
What this role actually does.
Ship programmatic pages
Build SEO and programmatic page sets on the marketing site in TypeScript: pages specific enough to actually answer what a contractor searched for at 9 p.m.
Build the free tools
Tools a shop uses before there's a product to sell them: useful on their own, worth returning to, and honest about what they are.
Measure without dark patterns
Analytics that tells us the truth without surveilling the reader. No fake urgency, no countdown timers, no tricks a contractor would resent if they saw the code.
Own conversion to the waitlist
The page says what's true (pre-launch, waitlist, what ships first) and makes the next step obvious. Your job is to remove friction, never to add pressure.
Document the experiments
What was tried, what moved, what didn't, and why, written down, so growth compounds as knowledge instead of resetting with each campaign.
What matters here
What you bring.
01
Engineer first, marketer close second
You ship pages, not decks. TypeScript in a real codebase is your working medium, and SEO judgment tells you which pages deserve to exist.
02
Constraints read as leverage
No invented claims, no dark patterns, pre-launch honesty on every page, and you see the trust that buys as the actual growth channel.
03
Empathy for the reader
A plumber deciding whether to trust one more software company. You write and build for that person, not for a funnel diagram.
04
No field-service background required
The domain is teachable, and the monthly customer calls will teach it. Bring the judgment; we'll supply the trade.
The first ninety days
How the role starts.
Weeks 1-2
Audit what's live
Read the site, its measurement, and its search footprint. Join a customer call. Ship one fix that makes a page more honest or faster.
Weeks 3-6
Ship the first set
One programmatic page set or one free tool, live and measured, with the experiment written down before and after.
Weeks 7-12
Make it a pipeline
A repeatable loop (pages, tools, measurement, learning) visibly moving the waitlist, documented well enough that the next experiment starts from evidence.
The terms, in the open
No surprises at the end.
Compensation, in the open
Compensation is discussed openly in the first call: the thirty-minute intro with the hiring manager, not the final round. You'll have the number in writing before the final interview, and the offer itself arrives in writing within five business days of it. No stage of this process exists to find out what you'll accept.
Five stages, about four hours
A person reads your application within two to three business days. Then the intro call, a sixty-to-ninety-minute technical screen on work like the work (no surprise algorithm puzzles) and three forty-five-minute conversations with the people you'd ship with. The written offer follows within five business days of the final interview. All told, about four hours of actual conversation.
The benefits, as stated
Comprehensive medical, dental, and vision with monthly wellness stipends; a minimum of three weeks PTO plus two company-wide recharge weeks; and an annual learning budget. Roles are remote-first across the US and Canada with quarterly onsites in rotating cities. We don't currently sponsor visas (reviewed annually), and we'd rather say that here than three interviews in.
Apply
One email. A person reads it.
Send your story to careers@thorbis.com. A résumé helps, but the judgment shows in how you describe the work you’ve shipped.