What an agency cannot ship, no matter how clean the code, is a group of people who, over time, become part of the problem with you. That is what the title “founding engineer” aims to capture, and it is the part of the job hardest to explain to engineers considering making the same move.
When I moved from running an agency to a founding engineer role at a consumer AI startup, the work looked the same on paper. Code, features, production. But something shifted in what you’re allowed to ignore. The shift sits somewhere harder to point at, in what you start noticing during the day and what you no longer allow yourself to walk past without comment.
The onboarding flow that taught me the difference
A few months into the role, I built a new onboarding flow for our product: design, code, ship. The flow worked as intended. Then we launched it, and as the numbers came in, the ad bringing users into that onboarding was clearly underperforming, for reasons unrelated to the flow itself.
Support authors and subscribe to content
This is premium stuff. Subscribe to read the entire article.
