Most career-change advice is written for the Sunday-evening spreadsheet stage, not the Tuesday-morning interview stage. It tells you to list your transferable skills and project confidence. The interview asks you specific technical questions and notices, in the first ninety seconds, whether you actually want the role you applied for or whether you think you should be doing the role three rungs up. The second thing is what loses the offer, and almost no career-change content prepares you for it because the people writing it have never sat on the hiring side of a Teams call.
The advice that's mostly fine on paper
You've probably read it. Identify your transferable skills. Write a narrative-style CV that frames your career change as a deliberate move. Network on LinkedIn. Get a cert or two. Apply widely. Be confident in interviews.
None of that's wrong, exactly. It's just written for the part of the process where you're at the kitchen table on a Sunday with a cup of tea, not the part where you're in a 25-minute Teams call on a Tuesday with a hiring manager who's got seven other candidates this week and a Slack notification going off about a prod incident behind the camera.
What the interview actually tests
For a career changer applying to a junior or first-rung technical role in the UK, the interview almost always has three parts. The career-change advice prepares you well for one of them and badly for the other two.
The technical screen. Usually 15 to 30 minutes of questions on the role's actual subject matter. Networking fundamentals if it's a network role. Cloud concepts if it's a cloud role. Basic security operations if it's SOC. This is the bit you can prepare for. Career changers who've done the project work described in the helpdesk essay tend to pass this fine. The ones who've relied on certs alone tend to come unstuck the moment the question leaves the multiple-choice framing.
The seniority calibration. Rarely named, almost always present. The hiring manager is working out whether you'll accept being managed by someone younger than you, with less life experience, who'll be asking you to do tickets they consider beneath their own level. The signal isn't in any single question. It's in the way you talk about your previous role, the way you describe what you want to do at this company, and whether you ever accidentally refer to yourself as “at my level” when you mean your old salary band.
The motivation read. The hiring manager is also working out whether you'll quit in eight months when the novelty wears off and the salary still hasn't recovered. Career changers have a higher attrition risk in the first year than graduates do, and hiring managers know this. You have to give them a reason to believe you're different, and “passion for technology” is not that reason.
Why the standard advice misses the second and third
The standard advice tells you to project confidence. Useful at a networking event. Actively counter-productive in a junior-role interview, because confidence reads as “this person thinks they're senior” and senior is not what's being hired.
It tells you to frame your career change as a deliberate move into a calling. Useful if the hiring manager is also a career changer. Less useful if they're 31, have been in technology since they were 18, and are politely sceptical of mid-life epiphanies because they've seen three of them quit in the last two years.
It tells you to highlight transferable skills. Useful for the CV screen. Less useful in the interview, where the hiring manager already knows you've managed teams and chaired meetings, and is now trying to find out whether you've actually configured a switch or written a script.
What works in the interview, specifically
Lead with the work, not the narrative. When asked why you're moving into technology, don't reach for the long-standing-interest line. Talk about what you've actually built in the last six months. The home lab that's currently on a Raspberry Pi under the stairs. The little bit of PowerShell you wrote to stop closing the same ticket twice a week at your current job. The lab environment you broke on a Sunday and fixed by Wednesday. Specific, recent, slightly embarrassing. Two minutes.
Name the seniority calibration before they have to. Something like “I know this is a junior role. I'm looking for the first proper technical seat and I'm planning to spend 12 to 18 months learning the stack properly before the next move.” That one sentence resolves roughly half the doubt in the room and usually shortens the interview by about five awkward minutes.
Be specific about salary. If the role pays £30k and the question comes up, the answer is “yes, I've planned for this”. Not a wince. Not a long pause. Not a story about what your old role used to pay. The wince is what costs people the offer. Far more often than the cert stack does, and it's the bit nobody practices because nobody on LinkedIn is filming themselves doing it badly.
Pick one specialism and sound like you mean it. “I want to work across cloud, security and automation” is what graduates say. It tells the company you don't know what you want and they'll be training you for the next person to poach. “I want to spend the next three years getting strong on networking and infrastructure, with a view to architecture work later” is what a hireable career changer sounds like. Even if you're less sure than that. Especially if you're less sure than that.
The CV problem
A separate but related issue. Career-change CV advice usually tells you to write a long narrative-style summary at the top explaining your move. Most hiring managers don't read it. They scan to the most recent role, see “Operations Manager, Tesco, 2014 to 2024”, and either bin the CV or open the projects section to see if there's anything to hire.
The projects section is the thing that decides it. Three or four finished, named, written-up technical projects, with a one-line description and a working link. If that section is empty, the 500-word narrative at the top of the page cannot save the CV. If that section is strong, the narrative is barely needed and most hiring managers won't read it anyway.
Most career-change advice spends 80% of its airtime on the bit nobody reads and 20% on the bit that decides the outcome. Which tells you something about who's writing it.
The honest summary
Career-change advice is mostly written by career coaches, not by people who hire engineers. The two groups answer different questions. The coach is answering “how do I help this person feel ready to apply?” The hiring manager is answering “is this person going to be productive and stick around?”
The candidates who get hired are usually the ones who've quietly bypassed most of the coaching content and spent six months building the project work, planning the salary dip, and rehearsing the seniority-calibration conversation. The narrative-style CV and the confident handshake are decoration on top of that work, and they cannot substitute for it.
Where this connects on POST
For the project-work bar that the interview actually tests, the helpdesk essay describes the same shape from a slightly different angle. For the salary and household economics, The second beginner problem covers the bit that quietly ends most career changes. For a written call on the specific move you're planning, the Career Verdict will give you the same kind of read a hiring manager would, before the interview, not after.