Those who quit Software Eng. to do something else, what did you do?

Transitioning out of software engineering (SWE) is a common move, often driven by burnout, a desire for different impactful work, lifestyle changes, or a search for greater personal alignment. Many paths leverage existing technical skills, while others represent a more complete shift.

1. Adjacent Technical Roles (Non-SWE)

Many former engineers choose roles that allow them to use their technical acumen in a different context or with a shifted focus.

• ·Data Science / Machine Learning Engineering: This is a popular transition point, leveraging programming skills but shifting towards modeling, statistical analysis, and product analytics. While Data Science can sometimes involve extensive SQL and dashboarding, ML Engineering is closer to SWE with a focus on productionizing models and optimizing pipelines. Paths into this field include ML theory courses (e.g., Andrew Ng), building projects (Kaggle), and targeting hybrid roles.
• ·DevOps / SRE / Cloud Engineering: Engineers seeking to move beyond application-level coding often find a home here, focusing on infrastructure automation, distributed systems, and reliability. Although high-stress during incidents, these roles offer significant impact. Relevant certifications (AWS, Kubernetes CKAD) and GitOps experience (ArgoCD) are valuable.
• ·Cybersecurity: Moving from building applications to securing them is a natural progression for some. While entry-level roles can involve ticket triage, advanced roles like red teaming or application security are highly technical. Experience can be gained through platforms like Hack The Box, OSCP certification, or bug bounties.

2. Product-Adjacent Roles

For engineers who enjoy problem-solving and strategy but want less direct coding, product-focused roles are a common choice.

• ·Product Management (PM): This path leverages an understanding of software development but shifts focus to 'what should be built' rather than 'how to build it.' It requires strong scoping, user empathy, and people skills. Many PMs at leading tech companies have a SWE background. Leading small feature projects or taking PM courses are good starting points.
• ·UX Engineering: These roles blend design and development, focusing on creating user-friendly interfaces and design systems. This niche but growing field combines engineering with user empathy, often involving tools like Figma and React. Contributing to design-focused open-source projects can be beneficial.

3. Non-Technical Transitions

Some engineers make a clean break from the tech world, seeking entirely different challenges.

• ·Finance / Quant Trading: The intellectual rigor and high compensation attract many engineers to quantitative finance. This can involve quant research (requiring strong math and stats) or software quant roles focused on low-latency systems. Learning stochastic calculus and using backtesting platforms can be helpful.
• ·Entrepreneurship / Startups (Non-Engineering Role): For those seeking autonomy and mission-driven work, starting a business or joining an early-stage startup in a non-engineering capacity (e.g., operations, marketing) is appealing. The hardest part often isn't coding, but user acquisition. Entrepreneurship can also take the form of building micro-SaaS products.
• ·Consulting: Offering expertise to businesses on a project basis, whether in IT or strategy, provides variety and allows engineers to leverage their problem-solving skills across different industries.
• ·Teaching/Education: Sharing technical knowledge as an instructor, professor, or content creator is a fulfilling path for some, allowing them to educate future generations of engineers or technical professionals.
• ·Creative Fields: Some engineers transition into fields like technical writing, developer advocacy, or even entirely different creative pursuits like digital art or filmmaking, where their analytical and problem-solving skills can still be applied.

Factors Influencing the Decision and Key Takeaways

The decision to leave SWE is often multifaceted:

• ·Burnout and Work-Life Balance: The demanding nature, long hours, and on-call responsibilities are frequent drivers for change.
• ·Lack of Growth or Bureaucracy: Feeling stagnant or frustrated by organizational inefficiencies can lead engineers to seek new environments.
• ·Desire for Different Impact: A wish to contribute in ways beyond pure coding, whether through strategic decisions, direct user interaction, or addressing societal issues.
• ·Personal Interests and Values: A shift towards careers that align more closely with personal passions or offer greater meaning.
• ·Financial Motivations: While some paths might initially lead to a salary decrease, others, like quant finance or successful startups, offer significant financial upside or equity opportunities.

Engineers possess a versatile skill set that is valuable across many industries. When considering a transition, it's crucial to reassess existing skills, identify how they can be repurposed, and manage the risks associated with a career change, such as financial stability. Networking, further education, and strategic career planning are vital for a successful pivot. Often, the best approach is to explore 'adjacent lateral' moves first, to find roles that scratch a new itch without leaving the industry entirely, with many ex-engineers eventually circling back to coding in a different capacity.