Growth Engineer, Lifecycle and Outbound
Ships the code, and carries the number it produces.
This role owns how a stranger becomes an account. You will work inside the codebase, not around it: read the schema, change the flow, instrument the path from a first visit all the way to a signed-up account, and hold yourself to conversations created rather than messages sent.
Most of what you need is already built and running. Your job is to find where people fall out of it, fix that, and prove the fix with a number. Bring the ability to ship the change yourself and the judgement to know which change is worth shipping.
The tour
This role runs as a two-year tour. That is the term on both sides. Near the end of it we sit down together and decide whether to run another one.
You will know in your first week what the tour is for: what you own, what has to be true by the end of it, and how that is measured.
By day ninety
One instrumented path from first visit to created account, measured end to end, with the drop-off at each step visible.
The outreach rebuilt around whatever the data says actually gets a reply.
A weekly number for how many real conversations it produced, on the board every Monday.
And whatever does not work turned off rather than left running.
Apply
One page. Five questions, a short block on how you work, and a link to something you built or grew. There is no resume to attach and nothing to upload.