Pick your target role and experience. Get the rounds you will face, the skills to show, the notice-period timing and the mistakes that cost offers.
Moving to a different field, not only a different company? Use the career change roadmap: what carries over from your job and a plan for the rest.
Nothing you choose here leaves your browser.
This is a template for the role and level you picked, not a plan built from your history. Companies differ; change what does not fit. For a plan built from your own resume and skills, for any job, use the skill gap analyzer.
At one to three years the loop is coding heavy. Low-level design shows up; high-level design is rare. The hiring manager wants to hear one thing you owned end to end, even if it was small.
Service work teaches delivery under a ticket. Product interviews test decisions. Every item below should come with one story of a decision you made.
Tell recruiters on day one, ask whether the company reimburses a buyout, and ask your current HR what a buyout costscovers pay in lieu of unserved notice, and ask your current HR what your contract says it costs before you need the answer.
Never resign on a verbal offer; wait for the letter. Give the notice period on the first recruiter call.
Below, add your resume and get a learning plan for the backend developer job: what you already have, what to learn first, free courses and dates at the hours you have.
The roadmap above is the same for everyone who picks your role and level. This planner is yours: add your resume, or type what you do now, and it shows which skills the job needs that you already have, which ones to learn first, free courses for each, and dates that fit the hours you have each week.
It fills in the work skills you already use. Leave it empty if you are a student or new to work.
Pick from 910 jobs, or type your own title and add a job post below.
Your plan is saved in this browser. The text of your resume, and what you send to the AI, are saved to ClapAssist so our tools can fill them in for you next time. See or delete.
Two minutes for the guide, then the plan.
Your choices stay in this browser, so the same roadmap is there when you come back.
Real output of the roadmap above, on a fixed date.
Say today is Mon, 2 Nov 2026. An analyst with four years at a service company picks “Data analyst or analytics engineer”, “3 to 6 years” and 90 days of notice. The roadmap lists five rounds: SQL test, case study or take-home, analytics round, modeling round, hiring manager round. Resign today, and the last day at the current company is Sun, 31 Jan 2027.
The timing card says resign by Tue, 1 Dec 2026, 29 days from today. That is the whole window for applying, the five rounds and a signed letter. It is tight, so the analyst starts the SQL and case-study practice this week and tells every recruiter the notice period on the first call.
Now the card says too late: the notice runs 16 days past that date. The only ways to make it are an offer in hand already, or a notice buyout ofyour employer agreeing to pay in lieu for about 16 days. So the analyst asks the new company two things before agreeing to the date: is that date firm, and will they reimburse the buyoutcover the unserved days?
The lesson is the order. Work out the resign-by date first, then plan the preparation backward from it, not forward from today.
The job and the interview both change.
At a service company you deliver what a client asked for, often on a system someone else designed. At a product company your team owns the product for years. You are asked what to build, how to measure it, and what to do when it breaks at night.
So the rounds test judgement more than recall. You solve a problem out loud while someone watches, you design something and defend it under questions, and you tell the story of one thing you owned from start to finish. Knowing the answer is not enough; they want to hear how you got there.
A product-company reader skims for decisions and results. A line that names a client and a stack tells them where you sat, not what you did. That is the most common reason a strong engineer from a service company is not called back.
Say what you changed and what happened next.
Take each project on your resume and answer three questions: what was broken or missing, what did you yourself do, and what was different afterward. Put a number in only if you really have it.
Before: Worked on a Java and Spring Boot application for a banking client.
After: Built the retry step for failed payments in a bank’s app, so failed payments went into a queue and retried by themselves instead of waiting for a manual fix.
Before: Developed UI screens in Angular as per requirements.
After: Owned the sign-up screens of a retail client’s website; rewrote the form checks so people saw what was wrong on the field itself, not after pressing submit.
Before: Prepared reports using SQL and Power BI.
After: Replaced three spreadsheets with one sales dashboard that the regional managers now open every Monday; wrote the SQL that feeds it.
If the contract keeps the client’s name private, name the industry and the kind of system instead. Then check your resume against the job post to see whether the words the posting asks for are now on the page.
Say it first, with a plan attached.
Recruiters fill roles against a date. A long notice is easier to accept when you raise it yourself and show you have thought about it. A short script:
“My notice period is 90 days. I can ask my manager about an early release once I have an offer, and I would like to know your longest joining window so we can plan around it.”
Then ask the questions that decide your dates: how many rounds there are and how long the loop usually takes, the latest joining date the team can wait for, and whether the company reimburses a notice buyoutcovers pay in lieu of notice. Write the answers down; they go straight into the timing card above.
When the offer comes, read the letter before you resign: the offer letter reader pulls out the joining date, pay and notice terms. Then the resignation letter generator writes a short, polite letter that states your last day.
Three clocks run one after another.
Preparation. How long depends on how far your skills are from the role, and on your hours. The week-by-week planner on this page measures that: it compares your resume with the job data for the role, adds the hours each missing skill needs, and spreads them over the hours a week you set. The full rules are printed on the skills gap analysis page.
The interview loop. Several rounds with days between them, sometimes more than one company at a time. Apply before you feel fully ready: the first loops are practice too.
The notice period. Fixed by your contract. The timing card above turns it into dates.
Add the three and you have an honest date. If it is later than you hoped, more hours a week shorten the first clock; asking early shortens the third. Nothing shortens the second except being ready for each round.
It is a different test more than a harder one. Service hiring often checks what you know; product hiring checks how you think: problems solved out loud, a design you defend, one piece of work you owned. People who fail usually prepared for the wrong rounds. Pick your role and level in the roadmap above to see the rounds you will face, then practice those.
Yes. The rounds judge what you can do in the room, not the name on your last payslip. What hurts is a resume that only lists client projects and tools. Rewrite each line to say what you built or changed and what happened after, and be ready to explain your own part in every project three questions deep.
Yes, on the first call. Your real last day shows on the papers from your current employer, so a shorter number told early comes out later and can cost the offer. Say the real period, say what you can do about it (early release, a joining date you are sure of), and ask what their longest joining window is.
Yes, if the plan fits the hours you really have. Put those hours in the week-by-week planner on this page and it spreads the skills over the weeks, most important first. Practice the way the rounds run: timed problems, design out loud, and your ownership stories told to a friend who asks follow-up questions.
Usually fewer of the algorithm puzzles that engineering rounds use, and more SQL. The data roadmap above lists a timed SQL test, a case study or take-home, an analytics round on metrics and experiments, and from about three years a modeling round. Practice writing SQL live without a search, and explain your numbers to someone who is not an analyst.
After the signed offer letter, never on a verbal yes. Then count back from the joining date: your notice period decides the latest day you can resign and still join on time. The timing card in the roadmap above does that count when you add a join date, and says so when the date is already too close.
The file is read in your browser, and your plans are saved in this browser, with a delete button and a backup file you can download. The text of your resume, and what you send to the AI, are saved to ClapAssist so our tools can fill them in for you next time; see or delete them at clapassist.com/my-data/. Only the AI buttons send text, and each one says what it sends.
The roadmap adds up hours per step: levels to climb times 15 hours for a tool, 20 for a work skill and 25 for a knowledge area. That is our starting guess, not a promise; change the hours on any step and the dates move. At 6 hours a week, 120 hours is about 20 weeks.
From the O*NET 31.0 Database of the U.S. Department of Labor (August 2026 release), used under the CC BY 4.0 license. It rates how important each work skill and knowledge area is for 910 jobs, based on surveys of people doing the work, and lists the tools the job uses. The jobs and skills are the same in most countries; add a job post from your own country to see what employers there ask for.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your live interview audio and screen are never stored. Your resume and notes are saved to your account so the app fills them in on any computer. It is hidden from screen share on every plan, including Free; only you can see it.
This page includes information from the O*NET 31.0 Database by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA). Used under the CC BY 4.0 license. ClapAssist has modified all or some of this information. USDOL/ETA has not approved, endorsed, or tested these modifications. Learning links go to each site’s own search; we have no deal with any of them.