Why do some developers choose to change careers?

Being a developer is an exciting job, but it is not necessarily for everyone, or for an entire career. Between deadline pressure, constant technological changes, especially over the past few months, meetings and sometimes a lack of recognition (sniff), some eventually start considering a career change.
Leaving IT to do something else may seem like a good solution, but changing careers does not necessarily mean that the difficulties will disappear.
Why leave a developer job?
The reasons are as varied as the number of developers. Some eventually get tired of spending their days in front of a screen, writing code, or rather, lately for some, reading and validating code generated by an AI assistant. After several years of fixing bugs and responding to sometimes urgent requests, they feel the need to do something more concrete.
This was the case with my wife, who was a developer. She wanted to change careers to do a more "human" job, with physical contact and a positive impact on people. She became a nursing assistant, then a teacher...
There are also developers who no longer feel at home in their profession. Technologies evolve quickly, skills sometimes become obsolete and you have to keep learning. The arrival of AI and code generation tools can also change their relationship with the job.
Finally, some simply want a different lifestyle. Working in a trade, becoming self-employed or doing a manual job can be particularly appealing when you have spent ten or fifteen years behind a computer.
When developers turn to manual jobs
Skilled trades are one possible career path. Plumbing, electrical work, carpentry, heating... These jobs have several apparent advantages: practical work, directly usable skills and potentially strong demand depending on the region.
I actually had two former colleagues who had decided to retrain as heating engineers. Before that, both had bought houses and completely renovated them before selling them. They had therefore already tried the practical side of things, and they enjoyed it. But both eventually returned to IT, for different reasons.
The first had particular difficulty getting clients to pay the right price for his work. Being technically skilled is not necessarily enough when you become a self-employed tradesperson: you also need to know how to sell your work, negotiate with clients and stand by your prices.
The second had plenty of work but had not hired anyone. He therefore found himself managing an increasingly large business on his own, with a workload that was difficult to handle and uncertain income.
These different experiences show that changing careers is not just about learning a new trade. You also have to deal with everything around it, such as business management, customer relations, accounting, organization and sometimes recruitment.
The difficulties of changing careers
Sometimes we imagine that by changing jobs, we leave behind all the problems we encountered in our previous profession. Unfortunately, it is not that simple. A developer who becomes a tradesperson may gain more independence, but may also have to find clients, prepare quotes, deal with unpaid invoices and attract new customers.
Conversely, a developer who retrains for another salaried job may face different constraints: fixed working hours, physical work, sometimes lower pay or the need to undergo training again.
You also have to take into account the possible loss of seniority and salary. After several years in IT, starting from scratch in another field can represent a real financial sacrifice. My wife took a significant pay cut when she went from being a developer to a nursing assistant.
Should you really leave IT?
Not necessarily. Before considering a complete career change, it may be worth changing your professional environment, specialty or way of working.
For example, a developer could move from web development to cybersecurity, system administration, teaching or technical support. They could also become self-employed, work on their own projects or join a company whose working methods suit them better.
Sometimes, it is not the developer job itself that is the problem, but simply the environment in which you work.
Conclusion
Changing careers after several years in software development is a perfectly legitimate decision, but it should not be idealized either.
The experiences of my two former colleagues who became heating engineers illustrate this reality quite well. You may want to leave IT to gain more freedom or do something more concrete, only to discover difficulties you had not expected.
With AI assistants becoming increasingly powerful, this is probably a question that more and more developers will ask themselves (Reading code doesn't exactly excite me...).





