First check whether it is the path or the circumstances: a bad team, a bad first job or burnout can feel like a wrong career. If the path really is wrong, you are rarely starting from zero. Map what transfers, test the new direction cheaply while still earning, and plan a bridge rather than a leap.
What people tell me
I spent years studying and working in one direction, maybe a field outside tech, maybe a tech role that no longer fits me, and I have realised it is not what I want. I feel like I have wasted time and money, and everyone around me seems settled. I do not know whether to start again, what I can keep from my experience, or how to afford the change.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Separate a wrong path from a wrong environment. A bad team or burnout can look like a bad career.
- Time spent is not wasted if you can name what it taught you and what transfers.
- Test the new direction cheaply before committing: a small project, a course, conversations with people doing the work.
- Build a bridge: move gradually using adjacent roles, while protecting your income.
- Give the change a realistic timeline, usually one to two years, and measure progress monthly.
First, the feeling of wasted time
When people write to me about this, the heaviest part is usually not the practical question. It is the grief of feeling that years were thrown away. I want to say clearly: they were not. You learned how to study, how to work, how to handle pressure and how to finish things. You also learned what you do not want, which many people only discover much later. The task now is to decide what to carry forward.
Is it the path, or the circumstances?
Before changing direction, check honestly whether the problem is the career itself:
| Sounds like the path | Sounds like the circumstances |
|---|---|
| You dislike the core daily work even on good days | You dislike your manager, team or company |
| You have tried several teams or roles in it | You have only experienced one workplace |
| The work you are drawn to is fundamentally different | You are exhausted and nothing feels enjoyable |
| You feel relief imagining leaving the field entirely | You feel relief imagining leaving this job |
If most of your answers are in the right column, a new team, a different company or proper rest may fix more than a career change would. If they are in the left column, a change is worth planning seriously.
Map what transfers
Very little of your experience is truly lost. Write down:
- Domain knowledge. Someone from finance, healthcare, logistics or teaching understands problems that software for those industries needs to solve.
- Working skills. Communication, managing deadlines, working with clients, writing, leading people.
- Technical overlaps. Data analysis, scripting, spreadsheets, testing, support, systems thinking.
Then look for roles where your old field and the new one meet. A commerce graduate moving into data analysis, a support engineer moving into backend development, or a QA engineer moving into automation or DevOps all have a head start over someone starting cold.
Test before you leap
Do not quit to find out whether you like something. Test it while you still have stability:
- Talk to three people doing the work. Ask what an ordinary day looks like and what they wish they had known.
- Build one small real project in the new area over four to six weeks.
- Notice what you do when nobody is watching. If you keep working on it past the time you planned, that is a strong signal.
- Check the market. Are there junior or transition roles in this area where you can work?
If the test goes well, you have evidence and a first project. If it does not, you have saved yourself a much more expensive mistake.
Build a bridge, not a leap
Most successful career changes I see happen gradually:
- Take on tasks in your current job that lean toward the new direction.
- Move into an adjacent role first, such as support, QA, analysis or operations, inside a tech company.
- Freelance or build small projects on the side to create evidence.
- Keep enough savings or income to handle a slower search.
A leap sometimes works, but a bridge rarely leaves you stranded.
A realistic timeline
| Period | Focus |
|---|---|
| Months 1 to 2 | Honest diagnosis, conversations, small test project |
| Months 3 to 8 | Structured learning with two substantial projects |
| Months 9 to 12 | Applications, networking, adjacent roles, freelance work |
| Year 2 | First role in the new direction, keep building depth |
It may be faster or slower depending on your background, but planning for roughly a year helps you avoid panicking in month three.
Dealing with other people's opinions
Family and friends may see a change as going backwards, especially if you are leaving a respected field. You do not need their approval to start testing. Once you have evidence, such as a project, a course completed or a first freelance job, the conversation becomes much easier. Explain the plan, not just the feeling.
Keep measuring progress
Each month, ask:
- What did I build or learn that I can show?
- Who did I talk to in the field?
- Am I closer to my first role than I was a month ago?
If the answers stay empty for several months, adjust the plan rather than abandoning the direction.
If you are still stuck
Read Moving Into Tech From a Commerce Degree, Fourteen Questions Worth Answering Before You Change Jobs and Returning to Software Engineering After a Career Break. If you want someone to look at your specific situation, join Sefism and, as a member, book a 1:1 session.
Was this answer helpful?
Read next
- Moving Into Tech From a Commerce Degree: Which Paths Actually PayAn honest guide for commerce graduates who want a better paid career in tech: how salaries really grow, which paths turn a finance and business background into an advantage (data analytics, business analysis, ERP consulting, fintech, QA, development), a six month plan, how to switch without quitting, and the pitfalls that cost people years.
- Fourteen Questions Worth Answering Before You Change JobsThe typical job change starts with one specific bad month, and within a fortnight the applications are out. Sometimes that is right, and often it produces a lateral move into a different set of problems discovered around month four. Fourteen heuristics for the whole arc: deciding, choosing, not being talked into or out of it, and leaving well.
- Returning to Software Engineering After a Career Break: A Realistic PlanA practical guide to getting back into software development after years away: the skills that matter today, which area to focus on, how to rebuild confidence, what to build for a portfolio, how to explain the gap, where to find returnships, and a month by month path to your first role that fits around family life.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open to X and Instagram followers and university students. Prefer to talk? A free call works too.