10 Career Paths Tech Workers Can Explore Beyond Tech
A comparison of ten directions tech workers might explore beyond their current role, with trade-offs and first tests to help you investigate each one. This is not a promise that every path is available in every market.
The lists already exist. You've seen them. "Ten careers for software engineers" — they tend to be some combination of the obvious (consulting), the aspirational (entrepreneur), and the ones that require qualifications you don't have yet (lawyer, therapist). A list is only useful if it helps you test a real option against your constraints.
Here are ten directions to investigate, with the trade-offs and first small tests to consider. This is a comparison guide, not a promise that every path is available in every market. For the decision and exit process itself, see the guide to leaving tech and the checklist for preparing while employed.
A note before the list
Before treating an idea as a plan, check four things: what the day-to-day work is actually like; what qualifications or local requirements apply; how people in your target market get hired or find clients; and what the income and benefits would mean for your household. Job postings, informational conversations, short projects, and introductory courses can help test assumptions while you still have options. They are evidence to gather, not guarantees of a smooth transition.
The list isn't a menu to choose from. It's a set of possibilities to test against the actual work, requirements, and constraints of your situation.
1. Independent consultant or fractional executive
If you've built deep expertise in engineering, product, design, or data, consulting may let you sell a defined outcome rather than apply for another full-time role. It is a business as well as a technical job: finding clients, scoping work, pricing it, and handling gaps between projects are part of the work.
Test it: speak with a few potential buyers about a specific problem you could solve, then draft a small paid pilot with a clear scope. Do not assume interest in your skills will automatically become paid work.
2. Product management in a different sector
This can be a lateral move for engineers, designers, and technical leads who already work closely with product teams. Moving into product at a company outside tech may also require learning a new sector, such as healthcare, financial services, manufacturing, or retail.
Requirements, pay, and hiring demand vary by sector and location. Read current postings for the specific market you have in mind; note which domain knowledge is required and which skills transfer from your current role.
Test it: ask a product manager in that sector what a typical week involves, then try a small case study using a real user or service problem.
3. Technical writing and developer relations
If you have depth in a technical domain and can explain complex things clearly — in writing, talks, documentation, or demos — technical communication may be worth exploring.
These roles can combine research, writing, documentation, demos, events, and community work in very different proportions. Read role descriptions carefully: a job called DevRel may be primarily marketing, support, or travel, while technical-writing roles can differ in how much product ownership they include.
Test it: create a short tutorial or demo for a tool you know and ask a target reader to use it without your help.
4. Founding a company or joining an early-stage startup
Founding or joining an early-stage company is one possible direction, but the day-to-day work and financial risk differ sharply from an established employer.
Early-stage work can mean broad ownership and fast feedback, alongside uncertain funding, shifting priorities, and less predictable compensation. A specific customer problem is a stronger starting point than a general wish to escape your current role.
Test it: talk to prospective customers about the problem before building a product, or try a short project with an early-stage team before relying on startup equity or future revenue.
5. Teaching and education
Coding bootcamps, university-level courses, curriculum design, and corporate training have different entry requirements and working conditions. Check whether a role requires formal teaching credentials and compare actual compensation and contract terms.
Test it: teach a short workshop or internal session, then ask learners what helped and where they got stuck.
Teaching involves more than explaining a subject: preparation, assessment, classroom or learner support, and administrative work may all be part of the role. Compare the specific workload and compensation rather than assuming the experience will match the appeal of the subject.
Before committing to a teaching path
- Have you actually taught anything in a structured setting? A workshop, an internal training, a bootcamp guest lecture? Teaching in theory and teaching in practice are quite different, and most people don't know which one they enjoy until they've done it.
- Are you energised by explaining things to people who don't understand them, or is it something you're merely good at? The difference matters more after year one than it does on day one.
- Have you looked at what the actual income looks like for the specific teaching role you're imagining? It varies enormously — from well-compensated curriculum roles at edtech companies to unpaid adjunct positions that would genuinely surprise you.
6. Non-profit and public sector
Public-interest organisations hire for technical and product work, but budgets, hiring processes, and compensation differ widely. Compare current openings in your region rather than assuming that mission alignment predicts the role or its conditions.
The daily reality can differ from commercial tech, but it varies by organisation. Check decision-making pace, funding, compensation, and how much of the role is hands-on delivery versus coordination before deciding that a mission fit is also a work fit.
Test it: review several current job descriptions and speak with someone doing similar work about decision-making pace, funding, and the day-to-day responsibilities.
7. Venture capital and startup advising
These are selective paths and usually depend on relevant operating experience, a track record, and relationships in the startup ecosystem. An operator-in-residence role or a focused advisory project may be a way to learn what the work involves, but availability varies by fund and market.
Angel investing and formal advising are more accessible routes into the ecosystem without the institutional constraints of a fund. Both require either capital or reputation to be meaningful. Neither is something you walk into with nothing to bring — the value of an advisor or angel investor is almost entirely their network, track record, or domain expertise. If those things are strong, it's a real path. If they're not yet built, it's worth being honest about what you'd actually offer.
Test it: offer a clearly bounded mentoring or operator project through an existing professional relationship and see whether you enjoy the work and can point to a useful outcome.
8. Creative fields — writing, design, photography
A portfolio and some experience with real briefs can make this path easier to assess before you rely on it for income. A technical newsletter, a design portfolio, or a small client project can reveal whether you enjoy the work and what buyers actually value.
Income and workload can vary with the type of work and client base. Before relying on a creative path financially, learn how people in that niche find paid work and what a realistic mix of client, employed, and independent work could look like for you.
Test it: complete one small portfolio project to a brief and deadline, then ask a potential client or editor what would make it useful to them.
9. Healthcare-adjacent roles
Health technology, patient experience, and advocacy roles differ substantially from clinical practice. Coaching, therapy, and other regulated services may require specific qualifications or licences; requirements vary by jurisdiction. Do not treat personal experience as a substitute for professional training.
Test it: interview people in the exact role you are considering and confirm the required training with the relevant professional or licensing body before budgeting for a transition.
10. Skilled trades and physical craft
This one appears on fewer lists and probably deserves more space on this one.
Carpentry, ceramics, horticulture, farming, and plumbing offer very different day-to-day work from screen-based roles. Some require apprenticeships, licences, physical demands, or tools and workspace that take time and money to arrange. A short class or supervised trial can help you understand the work before making a larger commitment.
Test it: take an introductory class or speak with a working professional about the physical demands, training route, local pay, and typical first-year conditions.
The pattern across all of these
What these ten paths have in common is that each asks for a different combination of skills, credentials, relationships, and tolerance for uncertainty. There is no single best option; the useful next step is to gather evidence about the path that fits your circumstances.
There is no reliable universal timeline for a career change. Before setting an exit date, use the small tests above to replace guesses with evidence, check the financial and practical constraints of your own situation, and decide what you would do if the first version of the plan did not work.
If you're at the beginning of working out which direction makes sense for your situation, the career pivot track on the Start Here page has more. When a specific path starts to feel plausible, test it in a small way and check its practical requirements before you set an exit date.
One honest letter, every Sunday.
Join 1,200+ tech workers getting real talk about burnout, career pivots, and what comes next. No hustle culture. No spam.