Sefism Your First Tech Job Roadmap

What this roadmap is

The Sefism Your first tech job roadmap is for students and graduates who have accepted, or just started, their first software job and want to do well in it rather than just survive. University teaches you to write code. It rarely teaches you how to read a contract, find your way around a codebase a hundred people wrote, take code review without flinching, keep a manager informed, or walk into your first pay conversation with evidence. That is what this roadmap covers, in the order you meet it.

By the end you can:

• Read your contract, spot fake offers and arrive on day one with accounts secured and questions ready.
• Get a working setup and merge a first small change within your first two weeks, with notes you can reuse.
• Open small, well-described pull requests, take review well and review teammates' code with useful comments.
• Send short weekly updates, raise blockers early and run your own one-on-ones with a list.
• Keep a work log all year and agree written goals, so your probation, first review and raise conversation rest on evidence.

Who it suits, and who should start elsewhere

It suits anyone in the gap between an accepted offer and the end of their first year: fresh graduates, interns converting to full time, and career switchers starting their first engineering role. It is not about any one language or stack, so it works whether you joined as a frontend, backend, mobile or QA engineer.

If you do not have an offer yet, this is the wrong place to start. The Job search roadmap covers targeting, applications and offers, and the Job ready roadmap covers the skills employers check for. Once your first year is behind you, the Mid-level to senior roadmap picks up where this one stops.

Prerequisites and realistic time

You need an offer or a job, and nothing else. The roadmap has 8 stages and 59 topics, with about 74 hours of effort in all. At about 5 hours a week that is roughly 19 weeks, close to four months; at 8 hours a week it is about 11 weeks. Most of those hours happen inside your normal working week, because the stages are about habits you build at work, not material you study at a desk.

If you are still a student or between offer and start date. Do stage 1 in the weeks before you join (about 6 hours), then plan on 6 to 8 hours a week for the first month, when stages 2 to 4 are busiest: setting up, learning the team's rituals and opening your first pull requests.

If you have already started full time. Skip stage 1 (it is marked as a foundation stage for exactly this reason) and give the roadmap about 4 to 5 hours a week, mostly on Friday afternoons: the weekly update, the work log entry, and one stage topic. Stages 7 and 8 fit naturally around your probation review and the first review cycle.

Stage by stage

1. Before day one (about 6 hours)

The weeks between accepting an offer and starting. Topics: reading your contract before you sign; IP, non-compete, side work and bond clauses; spotting fake offers and joining fees; learning about the company; paperwork, accounts and security basics; light preparation rather than cramming; and managing nerves and impostor feelings.

Milestone: a signed contract you have read with its key terms noted on one page, two-factor authentication on every account, a one-page note on the company's product and customers, and five questions for your first meeting with your manager. Tauseef's note: most problems he sees later, a bond nobody mentioned, a three-month notice period, a side work ban, were on paper from the start. And if anyone asks you to pay to start a job, that is not a job.

2. The first two weeks (about 14 hours)

Get your environment working, agree what success looks like and learn to ask for help in a way people are glad to answer. Topics: agreeing your onboarding plan, getting your development environment working, reading an unfamiliar codebase, following one feature end to end, asking good questions at the right time, finding a buddy and meeting the team, taking notes you will actually reuse, and shipping your starter task.

Milestone: a working local environment with the setup document improved, a written 30, 60 and 90-day plan agreed with your manager, a working notes document with a glossary, and your first small change merged. Fixing the setup guide as you go is a real contribution in week one.

3. Working with your team (about 10 hours)

The rhythm of a software team. Topics: standups that help the team, tickets and acceptance criteria, giving honest estimates, sprint planning, reviews and retrospectives, written low-context updates, getting value from meetings, working with product and design, and plain English at work, whether it is your first or second language.

Milestone: a one-page note on how your team works: its rituals and cycle length, how tickets and estimates are handled, which channels to use for what, and one retrospective point you raised.

4. Your first pull requests (about 16 hours)

The largest stage. Topics: keeping pull requests small, descriptions and self-review, testing your change and passing CI, receiving code review without taking it personally, reviewing other people's code, not breaking production, incidents and on-call at a junior level, and owning your mistakes.

Milestone: three merged pull requests with clear descriptions and tests, at least three reviews you gave with labelled comments, and a one-page note on how your team releases, rolls back and handles incidents. Tauseef's note: small pull requests are the easiest habit that makes a junior look senior, and when you break something, say so in the channel within minutes.

5. Communication and visibility (about 8 hours)

Keep your manager and team informed without being asked. Topics: short weekly status updates, raising blockers and risks early, running useful one-on-ones, starting your work log, asking for and receiving feedback, saying what you will deliver and when, and giving credit to others.

Milestone: four weekly updates sent, a shared one-on-one agenda document, a work log with at least six entries that each have evidence, and one piece of feedback you asked for and acted on.

6. Productivity and learning on the job (about 8 hours)

Topics: knowing what matters most this week, protecting focus time, a routine for getting unstuck, using AI assistants within company policy, owning what an AI assistant writes, learning the business domain, and a small, steady learning plan. The AI topics are practical: find your company's rules on approved tools and data, never paste secrets or customer data into anything, and never submit code you cannot explain line by line.

Milestone: a weekly plan template you have used for a month, two protected focus blocks in your calendar, a written note of your company's AI tool rules, a domain glossary with at least 15 terms and a one-page learning plan.

7. Workplace basics (about 6 hours)

Probation, reviews, pay, leave, notice periods, your rights and how to report harassment, plus burnout, boundaries and remote or office etiquette. Details vary by country and company, so the stage keeps sending you back to your own contract and local law.

Milestone: a one-page personal reference with your probation dates and criteria, review cycle dates, notice period, leave entitlement, the reporting routes in your code of conduct, and two written working boundaries.

8. Your first year plan (about 6 hours)

Topics: setting goals with your manager, reading your career ladder, when and how to ask for more responsibility, your first raise conversation, mentors and your network inside the company, when changing jobs early makes sense, and looking back on year one.

Milestone: three or four written goals agreed with your manager, a marked-up copy of your level and the next one on the career ladder, one request for more responsibility made, and a one-page first-year look back.

Projects

The roadmap suggests four projects from the Sefism FYP library that build the same habits outside work:

• Work log and weekly update builder, which builds the work log and weekly update habit this track depends on.
• Peer code review platform for university courses, to practise small changes and kind, labelled review comments.
• Open source contribution matcher, because finding your way into an unfamiliar codebase is exactly the first-two-weeks skill.
• Dotfiles and one-command machine setup, so a new work laptop takes an hour, not a week.

How it works on Sefism

Everything on Sefism is free to learn from, and this roadmap is currently free to add as well. The public page at Your first tech job shows every stage open, with its topics, milestones and recommended material.

Adding it to your dashboard costs no credits and does not use up your free first roadmap, so that stays available for another one. Once you add it, it stays yours. On your dashboard you can:

• tick stages off and track your progress, at a pace set by the hours you have each week
• keep the companion Your first tech job cheat sheet, which comes with the roadmap
• ask Tauseef a question about any stage, or book a 1:1 session if you want to talk your plan through

If you are new, create a free account first.

Each topic comes with a question to check yourself and a prompt for an AI assistant that quizzes you rather than doing the work.

The companion cheat sheet

The Your first tech job cheat sheet has 8 chapters that mirror these stages, with 64 concepts from the employment contract to the first raise conversation. Use it to revise a stage after you finish it, or keep it open while writing your first pull request description or your first self-review.

Related on Sefism

• First 90 days in a new developer job
• How to ask for help without looking incompetent and How to say you are blocked without looking incompetent
• Made a mistake in production: tell your manager or fix it first?
• How to overcome impostor syndrome in your first developer job
• How to read and understand a large codebase
• On the blog: What actually changes in your first two years as an engineer and What actually happens between your pull request and production
• From the library: The Missing README and Julia Evans's brag document guide

FAQ

What should I do in my first week as a software engineer? Get the code building and the tests passing, agree with your manager what success looks like at 30, 60 and 90 days, trace one feature through the code, and start a notes document. Stage 2 has the full checklist.

How long does it take to settle into a first developer job? The roadmap is paced over about 19 weeks at 5 hours a week, or about 11 weeks at 8 hours a week. Its first milestone, a small change merged, is aimed at your first two weeks.

Can I use AI coding assistants in my first job? Usually, within your company's rules. Stage 6 asks you to find the policy on approved tools and data, and to read, run and test every line an assistant suggests before you commit it.

When should I ask for my first raise? Stage 8 suggests raising pay a month or two before the review cycle, with evidence from your work log and market data, rather than at the review itself.

Should I change jobs in my first year? Not because the work feels boring at month four; the second half of the year is usually where it gets interesting. But if the salary is late or the place is unsafe, leave. Stage 8 asks you to write down what would make you stay or go before any decision.