Sefism Job Search Roadmap

What this roadmap is

The Sefism Job search roadmap is a plan for looking for a software job on purpose rather than by volume. It is written for the moment you decide you are ready to look, whether you are a final-year student, a recent graduate or a working engineer changing company, and it walks the whole search in order: choosing a target, building a resume and proof of work, applying through the channels that actually get replies, getting ready for each round of a hiring process, and handling the offer and your first weeks.

It has 7 stages and 54 topics, adding up to about 146 hours. On the public page that works out to about 31 weeks at a few hours a week. Each topic has a short explanation, one check question to answer without notes, and a prompt you can paste into an AI assistant that makes it question you rather than do the work for you.

What you have at the end

The roadmap names four outcomes, and every stage feeds one of them:

• A one-page resume with results-first bullets, which you can tailor to a real job description in under 30 minutes.
• A tracked weekly search that mixes applications, referrals and short messages to hiring managers.
• The ability to solve medium coding problems out loud in 45 minutes, and real stories ready for the hard behavioural questions.
• A way to compare offers by total compensation and negotiate politely with a researched counter.

Who it suits, and who should start elsewhere

It suits anyone who can already build things and now needs the search itself to work: students in their final year, graduates who have been applying and hearing nothing, and experienced engineers who have not looked for a job in years and find the process has changed.

If you are not yet ready to apply, start with University to job-ready, which builds the skills and projects this roadmap assumes. If your profile is the weak point, pair it with LinkedIn and personal branding, which this roadmap points to for your LinkedIn profile. If you want work from abroad paid in dollars, Remote jobs covers that market, and once you have signed an offer, Your first tech job picks up where this one ends.

Time and a realistic weekly plan

The total is about 146 hours. The stages are not equal: Know your target is 6 hours, Your resume 12, Proof of work 25, Where and how to apply 20, Coding and system design rounds 60, Behavioural rounds 15 and Offers, pay and a strong start 8. The technical rounds stage is the big one, and two of its topics (take-home assignments, and system design basics for mid level and above) are marked optional, so a new graduate spends less there than a mid-level engineer.

• A student or graduate with about 8 hours a week finishes in roughly 21 weeks. In practice the stages overlap: once your resume and two projects are ready, keep a weekly application rhythm going while you work through the technical stage, rather than waiting until you feel ready.
• Someone working full time with about 5 hours a week should plan for about 31 weeks. A workable week is two evenings of focused study (one or two coding problems, a story or a resume edit) and one weekend block for applications, outreach and your tracker review.
• With 12 or more hours a week the roadmap takes about 15 weeks.

Stage 1 is marked as a foundation stage: if you already have a clear target role, level and company list, you can skim it.

Stage by stage

1. Know your target (6 hours)

Decide which roles, level and companies you are going after, and what the market pays. Topics: role titles and your honest level, writing your constraints down first (location, visa, notice period, lowest acceptable pay), reading about 20 real job descriptions as data, marking skill gaps honestly as have, weak or missing, a tiered company list of 30 to 50 companies (stretch, realistic and safe), how each top company hires, and market pay for your level and city. The milestone is a one-page target sheet with one or two titles, your level, 30 or more companies in three tiers, the 10 skills that appear most in real postings and a pay range with its sources.

2. Your resume (12 hours)

A one-page, single-column PDF that survives a few seconds of scanning and an automated keyword filter. Topics cover how resumes are screened, bullets that show results with numbers (and how to find numbers when you think you have none), projects with stack, scale and links, education and gaps, mirroring keywords and tailoring, and rounds of feedback. The milestone: every bullet starts with an action verb, at least half include a number, feedback from two people is applied, and one copy is tailored to a real posting. It points to Jake's Resume Template and the Tech Interview Handbook resume guide, and treats a Jobscan score as a hint about missing keywords, never the goal.

3. Proof of work (25 hours)

Your resume makes claims; GitHub and a small portfolio prove them. Topics: what proof of work means, choosing and pinning the right projects, READMEs a reviewer can skim, a live demo, commit history, a GitHub profile README and an optional one-page portfolio on GitHub Pages. The milestone is two pinned repositories with complete READMEs, at least one live demo, a profile README and a portfolio linked from your resume. As the stage puts it, two finished projects with clear READMEs beat ten tutorial clones.

4. Where and how to apply (20 hours)

Apply where your target companies hire, lean on referrals and short messages to hiring managers, and track everything. Topics: job boards for your market (LinkedIn Jobs, Rozee.pk in Pakistan, Wellfound and Work at a Startup for startups), a tracker before your first application, referrals, messages under 80 words, a weekly rhythm, following up once after 7 to 10 days, and reading your reply rate. The milestone is a tracker with at least 30 tailored applications and 15 outreach messages over three weeks, with your reply rate worked out. If it is under 5 percent after 30 applications, the stage tells you to fix your resume or targeting before sending more.

5. Coding and system design rounds (60 hours)

Get ready for the technical rounds in the hiring processes you are actually in. Topics: what each company's rounds score, coding problems by pattern, a repeatable approach (restate, clarify, brute force, improve), thinking out loud, edge cases and testing your own code, stating time and space complexity, mock rounds, and two optional topics: take-home assignments and system design basics for mid level and above. The milestone is solving 3 unseen medium problems in 45 minutes each while talking out loud, plus one full system design walkthrough in 45 minutes for mid-level roles. Picks include Grokking the Coding Interview and the company interview guides in the library. The advice is blunt: do not let AI solve your practice problems; take a hint only after a real attempt.

6. Behavioural rounds and your questions (15 hours)

Real stories from your own work, calm answers to hard questions, and good questions of your own. Topics: the STAR structure, a story bank, "tell me about yourself", strengths and weakness, stress and gaps, answering the salary expectations question, questions to ask and red flags, and rehearsing out loud. The milestone is at least 6 written stories, a 90-second introduction and 8 questions to ask, all said out loud at least once. The stage suggests writing these before technical practice eats your time, because this is the cheapest round to improve.

7. Offers, pay and a strong start (8 hours)

Topics: what is in an offer, vesting and total compensation, comparing offers against the market, negotiation principles and leverage, making a counter-offer, what is negotiable beyond base pay, deadlines and withdrawing politely, and your first 90 days. The milestone is a side-by-side comparison of offers by total compensation, a polite counter drafted before you reply, and 30, 60 and 90-day goals agreed with your manager once you start. It links Ten Rules for Negotiating a Job Offer, levels.fyi and the brag document habit to start on day one.

Projects

Three FYP ideas from the library are attached, each useful in your own search:

• A job application tracker with a keyword gap view: a pipeline, follow-up reminders and resume keyword gaps.
• A developer portfolio and blog generator from GitHub: turns your repositories into a portfolio and is itself proof of work.
• Explainable resume and job description matching: shows you understand screening by building a matcher that explains which requirements are missing.

How it works on Sefism

Everything on Sefism is free to learn from. The public roadmap page shows the full list of stages, with the first two stages open to read. Adding the roadmap to your dashboard opens every stage, lets you tick topics off and track progress at your own pace, and also gives you the companion cheat sheet. Adding a roadmap uses credits: new members get starting credits and the first roadmap you add is free. If you are stuck on any stage, you can send Tauseef a question about your search, your target list or your profile, or book a 1:1 session for honest feedback on your positioning.

The companion cheat sheet

The Job search cheat sheet follows the same order in 8 chapters and 55 concepts, from target role and job level to vesting, exploding offers and a first 90 days plan. Use it to revise after each stage and as a quick reference while you are in a live process.

Related on Sefism

• Career questions: Why is my resume not getting shortlisted?, How many jobs should I apply to per day?, How to cold message recruiters and ask for referrals on LinkedIn, Should I take the first job offer or wait for the right role? and How to recover after failing a technical interview.
• Blog: A job search is a pipeline, not a performance and How to apply for software engineering jobs.
• Library: Grokking Tech Salary Negotiations for the offer stage.

What you can do afterwards

You leave with a search that runs like a pipeline: a clear target, a resume and portfolio that agree with each other, a tracker that tells you which channel is working, stories and technical habits ready for each round, and a researched number when the offer arrives. The same system works for every search after this one; keep your story bank and brag document current and the next search starts warm.

FAQ

How long does a job search take with this roadmap? The material is about 146 hours, which is around 31 weeks at 5 hours a week or 21 weeks at 8. You should start applying from Stage 4 onward rather than finishing everything first; the roadmap says waiting to feel ready is how months disappear.

How many jobs should I apply to? The roadmap suggests a tracked weekly rhythm, for example 10 tailored applications and 5 outreach messages a week, with about half your search time on referrals and messages, and a review of your reply rate after every 30 applications.

Do I need system design for a junior role? No. System design basics are an optional topic aimed at mid level and above; juniors focus on coding problems by pattern, thinking out loud and testing their own code.

Should I use AI to write my resume or solve practice problems? Each topic has a prompt, but the prompts are written to make the assistant question you and point out gaps, not to write your resume or solve your problems. The coding stage says plainly to do the logic yourself.

Is negotiating risky for a first offer? The roadmap's advice is that a reasonable, well-argued counter made politely very rarely gets an offer withdrawn, and that you should compare total compensation at the level offered, not the title.