On this page
This tech career roadmap covers the five to six months between finishing a course and accepting an offer. It turns knowledge into public evidence, evidence into conversations and conversations into interviews, at about ten to twelve hours a week, then covers your first ninety days in the job.
Almost everyone who switches into tech hits the same moment. The course is finished, the certificate is downloaded, and then nothing happens, because nobody knows you exist. Capable people spend a year applying from here and get nowhere, usually because they improvise the conversion from learning to offer instead of planning it.
This roadmap is for career switchers and new graduates who have the skills and not yet the job. It does not cover what to learn; the roadmaps hub does that. It covers the six stages after learning, with overlapping timings, a checklist for portfolio evidence, and a table that diagnoses which part of your job search is failing.
- Total duration
- 5-6 months
- Weekly commitment
- 10-12 hours
- Typical entry salary
- Varies by track
- 1Weeks 1-6
Stage 1
Close the evidence gap
You have finished the course. Nobody can verify what you learned. This stage produces the artefacts that make your skill legible to a stranger reading for eight seconds.
Skills you build
Project scopingTechnical writingDocumentationPublic deploymentPortfolio projects
- One substantial project, deployed publicly, with a README explaining the trade-offs you chose
- A written case study of that project — the problem, the approach, what broke, what you would change
Outcome: A stranger can look at one link and understand what you can do without you being in the room.
- 2Weeks 7-9
Stage 2
Position, then package
Decide what you are applying for before you write anything. A CV aimed at everyone reaches no one. Pick one role title and one industry, and build the entire package around it.
Skills you build
Role targetingCV structureLinkedIn positioningPortfolio narrativePortfolio projects
- A one-page CV in reverse-chronological order, quantified, with no skills-bar graphics
- A LinkedIn headline that names the role you want, not the one you are leaving
Outcome: Your CV, LinkedIn and portfolio all tell the same story, and that story names a specific job.
- 3Weeks 8-16, overlapping
Stage 3
Build the surface area
Referred applicants are more likely to be hired than cold applicants. This stage runs in parallel with applications and is the one career switchers most consistently skip.
Skills you build
Community participationWriting in publicInformational interviewsOpen source contributionPortfolio projects
- Two merged pull requests in a project you actually use
- Four published posts about what you are building
- Ten genuine conversations with people doing the job you want
Outcome: People in your target field know your name before your application arrives.
- 4Weeks 10-20
Stage 4
Apply like it is a system
Volume without targeting is wasted. Targeting without volume is slow. Run both: a tracked pipeline, tailored applications, and a weekly review of what is converting.
Skills you build
Application trackingCover letter writingCompany researchFollow-up disciplinePortfolio projects
- A tracked pipeline of 25-40 targeted applications with response rates logged
- One tailored paragraph per application referencing something specific about the company
Outcome: You know your conversion rate at each stage, and you can see which stage is actually broken.
- 5Weeks 12-22, overlapping
Stage 5
Interview as a separate skill
Building and interviewing are different competencies. People who are good at the job routinely fail interviews for want of practice explaining themselves out loud.
Skills you build
Technical interview practiceBehavioural stories (STAR)System design basicsLive coding under observationNegotiationPortfolio projects
- Six mock interviews with someone who will be honest with you
- Five prepared stories covering conflict, failure, ownership, ambiguity and impact
Outcome: You can think out loud under pressure and explain a decision you made six months ago clearly.
- 6Post-offer
Stage 6
The first ninety days
The offer is the start of the compounding, not the end of the process. What you do in the first quarter sets your reputation and your trajectory for years.
Skills you build
Onboarding fastAsking good questionsShipping earlyDocumenting as you learnPortfolio projects
- One small but visible improvement shipped in the first month
- Written onboarding notes that help the next person
Outcome: You are seen as someone who ships and improves things, which is what promotion cases are built from.
How does the tech career roadmap fit into five to six months?
The stages overlap on purpose, because networking and applying take time to produce results. Here is what a typical week focuses on across the plan:
| Weeks | Main focus | Running in parallel |
|---|---|---|
| 1–6 | One deployed project and its case study | — |
| 7–9 | Choose one role; rewrite CV and LinkedIn | Start community participation (week 8) |
| 10–11 | First targeted applications | Networking, writing in public |
| 12–16 | Applications and tracking | Networking; mock interviews begin |
| 17–22 | Interviews and follow-ups | Applications continue to week 20 |
| Post-offer | First ninety days | Onboarding notes, first shipped improvement |
At ten to twelve hours a week, the 22 weeks before an offer add up to roughly 220–264 hours, which is less than most courses take, yet it is the part that decides whether the course pays off.
Why does finishing a course not get you hired?
Because nobody reading your application can see what you learned. That is the uncomfortable asymmetry at the heart of a career switch.
You know exactly how much you learned: the concepts that clicked at 11pm, the bug that taught you more than the whole module, the moment the architecture finally made sense.
A hiring manager scanning your CV for a few seconds knows none of that. They see a course name and a title, and they have seen hundreds of both this month.
Everything in stage one exists to solve that asymmetry. A deployed project with a written explanation of your trade-offs converts private learning into public evidence. It is the single highest-leverage six weeks in this entire roadmap, yet it is the one people skip because it feels like it is not learning.
What makes a portfolio project count as evidence?
A portfolio project counts when a stranger can verify it without talking to you. Before you call stage one done, check that yours has all of these:
- A live link that works on a phone, not only a repository.
- A README that opens with the problem, then the approach and the trade-offs you chose.
- Something that went wrong, and what you changed because of it.
- A realistic constraint, such as real users, messy data or a hard performance limit.
- Readable history: small commits with clear messages, so a reviewer can see how you work.
Why do referrals matter so much?
Referrals matter because they change who reads your application and how much they trust it. In a study of nine large firms across call centres, trucking and high-tech, Burks, Cowgill, Hoffman and Housman (Quarterly Journal of Economics, 2015) found that referred applicants were more likely to be hired and more likely to accept offers than non-referred applicants, even though the two groups had similar skill characteristics.
This is not because referral is unfair, exactly. A referral is a risk signal. Someone who works there is putting a small amount of their own reputation behind you, and that is worth more to a hiring manager than any certificate.
Stage three is how you earn that, honestly and at scale:
- Contribute to projects people use. GitHub's guide to finding ways to contribute to open source suggests searching for
good first issueandhelp wantedlabels. - Write about what you are building, including what broke.
- Have real conversations with people doing the job. Not "can you refer me" on day one, but genuine participation over two months, after which asking is natural rather than awkward.
How do you tell which part of your job search is broken?
Track the conversion rate at each stage, not the number of applications sent. Once applications are running, most people track the wrong number. Total applications sent tells you nothing, whereas conversion at each stage tells you exactly what is broken.
| What you see | What is usually broken | What to do |
|---|---|---|
| Almost no responses (roughly under one in twenty) | Positioning or CV | Rewrite around one named role; get cold reads |
| Responses, but no technical rounds | Portfolio not carrying weight, or CV over-promising | Strengthen the headline project and its write-up |
| Technical rounds, but no offers | Interview practice | Book mock interviews; rehearse explaining decisions |
| Offers below expectation | Targeting and negotiation | Apply to a different band of company; prepare numbers |
Each of those has a completely different fix, and none of them is "send more applications". Diagnose before you increase volume.
How do employers screen career switchers?
Most processes filter in a predictable order, so each stage of this roadmap maps onto one filter:
- Automated or recruiter CV screen. The role title and relevant keywords must match, which is why stage two picks one role.
- Hiring manager review. They open one link, so make sure it is your best project.
- Technical assessment. A take-home task, live coding or a case, depending on the track.
- Behavioural interview. Prepared STAR stories carry you here, especially about why you switched.
- References and offer. People from stage three often become your most credible references.
What can you earn once you land?
What you can earn depends heavily on the track and the country, which is why the roadmap card says "varies by track". For scale, the latest US Bureau of Labor Statistics wage figures as of September 2026, which refer to May 2025, show how far apart tracks sit:
| US occupation (BLS) | Median annual wage, May 2025 |
|---|---|
| All computer and IT occupations | $109,470 |
| All occupations | $50,980 |
| Software developers | $135,980 |
| Data scientists | $120,230 |
| Web developers | $92,650 |
These are national medians for experienced and new workers combined, so a first role will usually start below them. Also, no equivalent official breakdown by tech role exists for India.
Common mistakes between course and offer
Across the stages, the same errors recur:
- Taking another course instead of starting stage one. A second certificate does not fix an evidence gap.
- Applying to every title at once. "Data analyst, data scientist or web developer" reads as no target at all.
- Networking only when you need something. Relationships built during the job search work better when they started before it.
- Tracking volume instead of conversion. It hides which stage is broken.
- Coasting after the offer. The first ninety days set how your team sees you for years.
The Sunday Growth Brief
One email a week: the best new comparisons, a fresh roadmap and the tech news worth your attention.
No spam. Unsubscribe in one click.
Where to go next
If you already have a finished project, start stage one by writing its case study this week. If you have not chosen a track yet, start with Data Science vs Machine Learning vs AI. For a technical path with stage gates, see the full stack developer roadmap. And if you are switching later in your career, How to switch to tech at 30 covers the specific constraints that come with that.
Frequently asked questions
How long does it take to get hired after finishing a course?
For career switchers I have worked with, three to six months with a genuine portfolio was common, and longer without one. There is no reliable official statistic for this. The main variable is not skill level — it is whether you started building a network and public evidence during the course or waited until after it.
How many applications should I send?
Fewer than you think, better targeted than you think. Twenty-five to forty tailored applications with a tracked pipeline tend to outperform hundreds of generic ones. As a rule of thumb, if fewer than one in twenty applications gets any response, the problem is positioning, not volume, so fix the CV before sending more.
Do cover letters still matter?
A generic one does nothing. Two specific sentences about why this company and this role, linked to a relevant piece of your portfolio, can help at smaller companies where a person reads every application. At large employers with automated screening, the cover letter is rarely read, so spend the effort on the CV instead.
Should I take a lower salary to break in?
Sometimes, and it is a legitimate strategy — but cap it at one role and eighteen months, and negotiate the learning explicitly: the stack, the mentoring and the scope you will own. A first role that teaches you nothing is expensive at any salary, because your next offer is judged on what you did there.
What if I get no responses at all?
That is a positioning failure, not a skill failure, and it is fixable. Have three people in your target field read your CV cold and tell you what job they think you are applying for. If they cannot say, that is your problem. Rewrite the headline, summary and top project around one named role.
Written by
Nishant Kiran
B2B SaaS & EdTech Content Strategist
Content writer and copy editor with seven years across EdTech, FinTech and B2B technology. Formerly led content marketing at 1stepGrow Academy.