Going From Engineer to Founder: A Practical Transition

What you actually need to know

• Engineering skills carry over but are not sufficient.
• Sales, customer development, hiring, fundraising, operations are new skills.
• The transition takes a year or two to find the shape.
• Spending too much time on engineering is the biggest trap.
• A co founder often helps especially on the first transition.

The core argument

The engineer to founder transition is one of the most common career moves in tech and one of the most poorly prepared. The engineer assumes that being a strong engineer translates to being a strong founder. The translation is partial. The skills overlap less than people think.

The skills that carry over are real. Architecture thinking maps to business strategy. The discipline of shipping maps to execution. The systems thinking maps to cross functional decisions. The technical depth helps with product judgment and engineering hiring. The engineer founder has real advantages that the non technical founder lacks.

The skills that are new are also real. Sales. The engineer has rarely run sales conversations. Customer development. The engineer has rarely interviewed customers. Hiring beyond engineering. The engineer has rarely hired marketing or operations. Fundraising. The engineer has rarely raised money. Operations. The engineer has rarely run the day to day of a business.

The transition takes a year or two because the new skills take practice. The first sales conversation is awkward. The fifth is better. The fiftieth is fluent. The same pattern holds for each new skill. The founders who deliberately practice the uncomfortable skills move through the transition faster than the founders who avoid them.

The biggest trap is spending too much time on engineering. The instinct is to do what the engineer is good at. The startup needs the founder to do sales and customer development as much as it needs engineering. The engineer who hides in the code produces a beautiful product nobody knows about. The fix is to deliberately spend time on the things that feel uncomfortable.

The new skills and how to learn them

How much does this take

The transition is two years of deliberate practice. The first year is uncomfortable. The second year is competent. The third year is fluent. The cost is engineering time the founder is not spending on the product, but the alternative is a product that nobody knows about.

Features the transition must have

• A clear charter of what the founder will own.
• A deliberate practice schedule for the new skills.
• A peer group of founders who have done this.
• A mentor who has made the transition.
• A way to measure progress on each new skill.
• A budget for the time spent on non engineering work.
• A co founder where applicable.
• A clear plan for when to step out of engineering work.

Expert opinion

The engineer to founder transition is one of the most common moves in tech and one of the least well prepared. The engineer assumes the skills transfer more than they do. The new skills are real and learnable but take practice. The engineers who prepare deliberately move through the transition faster than the ones who improvise. The cost of the practice is real. The cost of the avoidance is the company that does not work.

>

Yashveer Singh, founder of Yashveer Labs

How this is playing out for me

I am in the early phase of this transition. The engineering work is what I do most fluently. The sales conversations, the customer development, the writing this blog, are deliberate practices that I am running so the skills build over time. The first conversations are uncomfortable. The pattern is to keep doing them anyway.

The engineers I have advised through similar transitions share the pattern. The first year is awkward. The second year is competent. The compounding effect of the practice across the new skills is what produces a founder rather than an engineer with a startup attached.

The work that compounds for me right now is the writing. Eight hundred blog posts is the practice schedule for the writing skill that the founder role requires. The conversations with customers come next. The other skills follow.

For more on the related work, see becoming a senior engineer in three years and building a service business as a senior engineer.

Common mistakes engineers make

1. Treating the founder role as a senior engineering role.
2. Spending too much time in the code.
3. Avoiding sales conversations.
4. Avoiding customer development.
5. No deliberate practice of the new skills.
6. No peer group of founders.
7. No mentor who has made the transition.
8. Picking the wrong co founder under time pressure.

A first year founder plan

1. Months one to three. Get the product to a place where it can demo. Start customer conversations.
2. Months four to six. Run twenty customer conversations. Adjust the product based on what you hear.
3. Months seven to nine. Run twenty sales conversations. Close the first paying customers.
4. Months ten to twelve. Hire the first non engineering person. Practice delegation.

For more on the related work, read becoming a senior engineer in three years and going independent freelancing vs consulting vs agency. On the broader career side, building a personal brand as an engineer without becoming an influencer is the natural next read.