People who change careers in their mid-thirties become beginners twice. The first time, at twenty-two, the world is set up for it. The second time, at thirty-five, almost nothing is. That isn't a motivation problem and it isn't a skills problem. It's a context problem that nobody warns you about, and the people who manage it well plan for it on day one.
Who this is for
- You're somewhere between 30 and 45, you've done ten or fifteen years in another industry, and you're seriously considering a move into technology.
- You've read the career-change blogs and noticed they all assume you're 24, single, living with parents, and able to do a 16-week bootcamp on savings. That isn't your life.
- You're not asking whether it's possible. You know it is. You're asking what you're actually signing up for.
What being a beginner the second time is actually like
The first time you were a beginner, the structure did most of the work. You were at university or in a graduate scheme or on an apprenticeship. Your peers were also beginners. Your manager expected you to be slow. The salary was low because everyone's salary was low. There was no comparison to draw against.
The second time, none of that is true. You're on a junior salary in a team where the 23-year-old next to you, who we'll call Sam, has three years of cloud experience already and treats Terraform the way you used to treat Excel. Your mortgage is the same size it was last month. Your old colleagues from the industry you left are getting promoted to senior manager and posting about it. You have to ask permission to take a Wednesday afternoon off for a Microsoft exam.
That gap, between the life you have and the role you've taken to get out of the life you had, is the second beginner problem. It's almost never in the planning deck. It shows up around month four of the new job, usually on a Sunday evening, and it's the thing that actually makes people quit.
The three things people miscalculate
Salary floor, not salary ceiling. The career-change content always quotes ceilings. £80k for a senior cloud engineer. £100k for a security architect. The number that actually matters is the floor for the next two years. A career-change entrant into IT support or junior cloud ops in the UK is typically looking at £24k to £32k for the first role and £32k to £45k for the second. If your current household relies on £55k and you're the sole earner, that gap is the project, not the cert stack.
Time, not effort. People overestimate how much evening study they can sustain alongside a full-time job and a family, and they underestimate how long a single role lasts before the next one is realistic. Eighteen months in role one is normal. Two to three years to reach the salary you left behind is common. Anyone telling you twelve months is selling something.
Identity, not learning curve. The technical content is hard but it's finite. The harder thing is being the most junior person in the room after fifteen years of being the experienced person. Some people find that liberating. Most find it grinding, especially in months three through nine, and the ones who don't plan for it tend to bail.
What actually transfers from the old career
The career-change blogs will tell you that “soft skills” transfer. That's true in the abstract and useless in practice. Here's the operational version.
- Running a meeting without losing it. Genuinely rare in a junior technologist. Worth real money on day one.
- Writing a clear email to a non-technical stakeholder. Worth more than most certs in your second year.
- Reading a room. The reason career changers often out-promote graduates by year three. Not at year one, where the technical gap dominates. By year three, when the gap closes and the political work begins.
- Being unflappable when something is on fire. If you've managed a hospitality service through a Saturday night rush, or run a logistics shift through a depot outage, you already have the temperament that senior engineers spend ten years learning.
What doesn't transfer, despite the marketing
- Industry domain knowledge transfers less than you think, unless you stay in that industry's technology function. A logistics career into a logistics-company IT team is genuinely valuable. A logistics career into a general consultancy is not.
- Seniority does not transfer. Not at all. The fact that you used to manage 40 people in retail will not get you out of being a T1 analyst for your first 12 months. The people who insist otherwise interview badly.
- Salary does not transfer. The hiring manager benchmarks you against the technical bar of the role, not against what you used to earn doing something else.
What the realistic plan looks like
Two years of runway, not twelve months. Plan to be on a reduced household income for the back half of year one and most of year two. If you can't survive that, the plan needs to change before it starts, not eight months in when the money runs out.
One entry route, picked early. IT support into sysadmin, networking into infrastructure, project coordination into GRC, ops management into cloud ops. Pick the one that aligns with what you already do well, not the one with the highest salary headline. The headline is three roles away.
Six hours a week of focused project work, every week, for the year before you make the jump. Same shape as the helpdesk plan, but the stakes are higher because you have more to lose if you stop. If you can't hold six hours a week for a year, the next role can't hold you either.
One conversation with your partner, not several. The thing that actually kills these plans isn't the certs or the job market. It's running out of household patience around month nine when you're tired, the salary's lower, and nothing has obviously changed yet. Have the honest conversation about that on day one.
When the career change is the wrong call
Some honest disqualifiers. The kind nobody else will say to you.
- You're unhappy in your current career and you're hoping technology will fix that. It won't. The first 18 months will be harder, not easier, and the things that make you unhappy now will probably travel with you.
- You can't take a real salary cut without serious household stress. The plan only works if year one and year two can absorb the dip. If they can't, you'll quit at month seven and the whole project will read as a failure that wasn't.
- You don't actually like the technical content. You think you might tolerate it because the money looks better. You won't. The people who make this work find some part of the work genuinely interesting. If nothing about the job appeals to you on a Wednesday afternoon when nobody's watching, the move is wrong.
The honest framing
Career changers who get this right tend to outperform their graduate peers by year three. Not because they're smarter, and not because of some mystical “life experience” advantage. Because they already know how to behave in a workplace, how to communicate with people who aren't engineers, and how to manage themselves through a bad week. That gap closes at year three or four and the career changer comes out ahead.
The cost of getting there is real, and the people who plan for it on day one almost always make it. The people who plan only for the certs almost never do.
Where this connects on POST
For the realistic entry routes, the pathways page lays out the four beginner-safe lanes that career changers tend to take. The guided route narrows them down for your situation. If you want a written call on whether the specific move you're planning holds up, the Career Verdict is the closest thing POST does to a one-to-one assessment.