Career
Should I switch to a career in IT?
Should I retrain and move into tech from my current field, or keep building on what I already have?
Tech promises a higher pay ceiling, remote work and global demand — but the path runs through months of studying after work, a crowded junior market and starting over in seniority. Weigh the real costs against the real upside before you commit.
Short answer
Switch if you have tested the work itself with a free course or a small project and enjoyed it, can protect a few study hours every week for months, and can pick an entry path where your current industry knowledge gives you an edge. Stay or wait if you are drawn mainly by the salary halo: the junior market is crowded, the first search can take months, and early pay may sit below what you earn now for a year or two.
Template balance
Leaning yes
The pros have the edge, but it's not a landslide.
Higher long-term pay ceiling than most non-tech fields
Months of studying on evenings and weekends while holding my current job
How the verdict works
Each item counts with the weight you gave it. Sub-points can strengthen or weaken their parent by up to 50% — your own rating always stays primary.
Tap any argument below to switch it off and watch the balance move — sub-arguments shift their parent's weight.
Pros
Cons
Adjust the arguments and weights to your situation — the verdict recalculates live.
Check before you decide
- Finish a free intro course in two or three directions — testing, data, frontend — before investing months in one
- Build one small real project; the junior market rewards a portfolio far more than certificates alone
- Check whether your savings or current job can cover the stretch when junior pay starts below your present salary
- Map which IT employers value your current domain — an accountant applying to fintech competes in a smaller pool
- Block your study hours in the calendar for a trial month and see if the pace survives family duties and work fatigue
- Read 20 junior vacancies in your target role to see real requirements, not what course ads promise
Frequently asked questions
- Do I need a technical degree to get into IT?
- For most entry roles, no. Employers in tech tend to care about demonstrated skills — a portfolio, projects, certifications — more than the diploma on the wall. Some areas are friendlier to self-taught newcomers than others: testing, support, data analysis and frontend development are common entry points, while research-heavy roles may still expect formal education. Pick a path where your existing background gives you an edge.
- Which IT role should I aim for first?
- Start from your strengths, not from whichever role is loudest online. If you like structure and detail, look at testing or data work; if you enjoy people and explaining things, consider support, project coordination or product roles; if building things excites you, try development. Spend a weekend on a free intro course in two or three directions before investing months in one — the cheapest mistake is the one you catch in week one.
- How long does it take to land the first job in IT?
- It varies widely — be skeptical of anyone promising a fixed timeline. Plan in seasons, not weeks: several months of consistent study, then a job search that can itself take months in a crowded junior market. Two things shorten it more than anything else: a small portfolio of real work, and leaning on your previous industry — a former accountant applying to fintech companies competes in a much smaller pool.
Should I retrain and move into tech from my current field, or keep building on what I already have?
Make it yours