Software Engineer Roadmap

A step-by-step Software Engineer roadmap: the full stack, the skills to learn in order and the best places to learn each step.

The stack, end to end

  • Fundamentals: Variables and data types, Loops and conditions, Functions, Problem solving, Git, GitHub, Branching and merging, Pull requests, Arrays and hash maps, Trees and graphs, Sorting and searching, Big-O thinking
  • Database: SQL, SELECT and WHERE, JOINs, GROUP BY and aggregates, INSERT, UPDATE, DELETE
  • Testing: Unit testing, Integration testing, Test-driven development
  • Backend: System design, Scalability, Load balancing, Message queues
  • Get hired: Portfolio projects, Technical resume, Interview preparation

  1. Programming and problem-solving basics

    Suggested pace: Start here

    Learn to think in steps: variables, conditions, loops, functions and how to break a big problem into small ones. A structured beginner course gives you the habit of solving problems on your own.

    Skills

    • Variables and data types
    • Loops and conditions
    • Functions
    • Problem solving

    Tips

    • Type the examples yourself instead of copying them, and change them to see what breaks.

    Where to learn

  2. Version control with Git and GitHub

    Suggested pace: Next

    Git records the history of your code and lets teams work on the same project. Learn to commit, branch, merge, resolve conflicts and open a pull request on GitHub. Almost every software job expects it.

    Skills

    • Git
    • GitHub
    • Branching and merging
    • Pull requests

    Tips

    • Put every practice project on GitHub. It doubles as your portfolio.

    Where to learn

  3. Data structures and algorithms

    Suggested pace: Then

    Arrays, lists, hash maps, stacks, queues, trees, sorting and searching, and how to judge how fast code runs. Many technical interviews test this, and it improves how you design solutions.

    Skills

    • Arrays and hash maps
    • Trees and graphs
    • Sorting and searching
    • Big-O thinking

    Tips

    • Solve a few problems regularly rather than many in one weekend.

    Where to learn

  4. SQL basics

    Suggested pace: After that

    SQL is how you ask a relational database questions. Learn SELECT, WHERE, ORDER BY, GROUP BY, aggregate functions, joins and how to create, insert, update and delete data.

    Skills

    • SQL
    • SELECT and WHERE
    • JOINs
    • GROUP BY and aggregates
    • INSERT, UPDATE, DELETE

    Tips

    • Practise on real-looking data. Write the query by hand before using any tool that writes it for you.

    Where to learn

  5. Unit and integration testing

    Suggested pace: Later

    Automated tests catch mistakes early and let you change code with confidence. Learn to write unit tests, use mocks sensibly and test your API and database together.

    Skills

    • Unit testing
    • Integration testing
    • Test-driven development

    Tips

    • Write a test for every bug you fix so it cannot come back unnoticed.

    Where to learn

  6. System design basics

    Suggested pace: Later

    Learn how larger systems are put together: load balancers, caches, queues, databases and how to scale and keep them reliable. It also helps you explain your choices in interviews.

    Skills

    • System design
    • Scalability
    • Load balancing
    • Message queues

    Tips

    • Practise explaining the design of a small system (a URL shortener) out loud.

    Where to learn

  7. Build your portfolio, resume and interview skills

    Suggested pace: When you are ready

    Employers want proof. Finish two or three projects you can show and explain, put them on GitHub, write a clear resume that matches the jobs you apply for, and practise the interview questions for the role.

    Skills

    • Portfolio projects
    • Technical resume
    • Interview preparation

    Tips

    • Describe what you built, why, and what you would improve. That is what interviewers ask about.

    Build your resume · Check your resume (ATS) · Interview questions · Salaries · Browse jobs

Frequently asked questions

Where should I start with Software Engineer?

Start at step 1 and work down in order, because later steps build on earlier ones. If you are signed in, the roadmap compares your resume with each step and marks where you could start.

Do I need a degree to work as a Software Engineer?

It depends on the employer and the country. Many employers accept proven skills and projects, while others ask for a degree. Read the adverts for the roles you want and ask the employer if it is unclear.

How do I know I am ready to apply?

When you can build a small project from start to finish without copying a tutorial, and explain why you made your choices. Apply while you keep learning; you do not need to know everything.