The tech interview process has a predictable structure — and knowing the structure is half the battle for career changers. Most hiring processes move through four stages: the HR screen, the hiring manager conversation, a technical or skills assessment, and the final round. Each stage is testing something different, and preparing for all four without knowing the difference is how candidates burn out before they get to the offer.
Stage 1 — The HR screen
The HR screen is a ten-to-twenty-minute call with a recruiter. They are checking three things: that you are who your resume says you are, that your compensation expectations are in range, and that you can communicate clearly. Prepare a thirty-second version of your career transition story, know your target salary range going in, and ask one genuine question about the role at the end. This is not the place to dive deep — it is the place to clear the bar and advance.
Stage 2 — The hiring manager conversation
This is where you need to tell your career change story convincingly. The hiring manager wants to understand your motivation, your trajectory, and whether your background is actually relevant. Research the company before this call: know their product, their recent news, and one specific thing about the team or the role that genuinely interests you. Being the candidate who did the homework is rare and memorable.
Stage 3 — Technical or skills assessment
This stage varies by role. For PM candidates: a product sense exercise or a written take-home. For BA candidates: a requirements gathering scenario or a process documentation exercise. For UX candidates: a portfolio walkthrough where you explain your design decisions. For QA candidates: designing test cases for a given feature. For data analyst candidates: a SQL or analytics problem. Know what your target role typically tests and practice the specific format before the interview.
Stage 4 — Final round
Final rounds typically involve multiple interviewers across different functions — a peer interview, a cross-functional partner interview, and often a presentation or case exercise. Prepare five STAR stories (Situation, Task, Action, Result) drawn from your previous experience. Good themes to cover: a time you solved a problem with limited information, a difficult stakeholder situation, a failure and what you learned, a time you had to prioritize under pressure, and your proudest professional achievement. Practice these stories out loud until they are natural, not scripted.
Answering the career change question
Almost every interviewer will ask some version of: "Why are you making this transition?" The script that works is additive, not corrective. You are not running away from your old career — you are combining it with something new. "I spent six years in operations and realized the highest-leverage work I could do was in the software that ran those operations. I want to build that software" is a compelling answer. "I was bored and wanted a change" is not.
What to ask your interviewers
Ask things that reveal how the team actually works: "What does success look like in this role in the first ninety days?" and "What is the biggest challenge the team is facing right now?" signal genuine interest and preparation. Avoid asking about salary or benefits in a technical or manager interview — that conversation belongs with the recruiter.
Follow-up strategy
Send a thank-you email within twenty-four hours of every interview. Reference one specific thing from the conversation to prove you were listening. If you have not heard back within the timeline the recruiter gave you, follow up once, politely. For structured interview practice by role, the NewRoleKit interview prep and interview questions resources walk you through the process role by role.