When work starts to feel unsustainable, “Should I leave tech?” can sound like one decision. It often bundles three different questions:
- Do I need a different role?
- Do I need a different workplace or working conditions?
- Do I want to leave the industry?
Those choices can overlap, but they are not interchangeable. A new employer may not fix work that is wrong for you; a career change may be more than you need if a role or team change would help. You do not have to know the answer before you begin gathering evidence.
1. Write down what you want to stop and what you want more of
For one week, make a short note at the end of each workday. Record one task or condition that drained you, one that felt worthwhile, and what was happening around each. Keep the notes factual: “on-call incident from 11 p.m. to 2 a.m.” is more useful than “I’m bad at tech.”
At the end of the week, look for patterns. Are the difficult parts mostly about coding, interruptions, management, workload, values, or the product? Are there parts of the work you would want to keep if the conditions changed?
This is not a diagnostic exercise. It is a way to make the problem more specific before you choose a solution.
2. Sort the pattern into role, workplace, or industry
Use these questions as prompts, not a test with a score:
| What seems hardest | Ask yourself | A low-risk way to learn more |
|---|---|---|
| The tasks in my role | Would I still want this work if the workload and team were better? | Talk with someone in an adjacent role; try a small project that resembles its day-to-day work. |
| The conditions around the job | Do I like the work when I have time, support, and reasonable boundaries? | If safe and realistic, test one change: a clearer boundary, a team transfer conversation, or time away. |
| The industry itself | If I changed teams and tasks, would I still want to work in tech? | Explore a non-tech path through an informational conversation, a short course, or a small reversible project. |
A “yes” or “no” is not proof. One conversation or project can be misleading; use it to decide what to investigate next.
3. Test the smallest useful change
Choose an experiment that gives you information without forcing a major commitment. If the question is whether you still enjoy technical work, volunteer for a contained task that uses it. If it is people management, ask to observe or support a planning process. If you are curious about work outside tech, interview two people who do it and ask about the ordinary week, not just the appealing parts.
Set a limit before you start: how much time, money, or energy you are willing to spend, and what you want to learn. The goal is not to prove that a path will work. It is to find out whether the next question deserves more attention.
4. Keep the financial decision separate
Wanting a different career and being ready to resign are different decisions. Before making an exit plan, list essential monthly costs, debt and family obligations, benefits you would lose, income that might continue, and transition costs. Model a slower-than-expected search as well as the optimistic case. If taxes, benefits, debt, or investments are involved, get advice suited to your location and situation.
You can explore a change while employed. You can also decide that staying, with different boundaries or a different role, is the best next move. Neither outcome makes the questions you asked a waste.
A useful next step
Write one sentence for each of these prompts:
- “The part I most want to change is…”
- “A change I could test without resigning is…”
- “Before I make a financial commitment, I need to know…”
Then pick one small action for this week. You do not need a five-year plan; you need the next piece of information that would make your options clearer.
For a fuller stage-by-stage set of questions, see How to leave tech: a practical plan for what comes next.
