Graduate roadmap

Software Engineering

Software engineering is an umbrella term that covers the design, development, testing, and maintenance of software applications: both the parts end users see (front end) and the servers and databases working in the background (back end). The steps below start from scratch. If you already have some programming experience, skip ahead to the advanced steps.

The path
10
steps: 7 core, then 3 advanced
Made for
Graduates & new starters
Start at step 1, no experience needed
Core Foundations

Why just one?

In this sector overall, it’s often better to be a specialist than a generalist. Although generalist roles do exist and can be fulfilling, it’s specialist roles that are generally more sought-after and command higher salaries. Job descriptions sometimes list a lot of different programming languages, but often this is employers checking that you can learn fast.

Some languages are more widely used in different parts of the sector than others: Python is more useful in back-end and data work, but JavaScript and TypeScript open the door to building interfaces.

How fluent is ‘fluent’?

In this context, saying you’re ‘fluent’ in a programming language means more than just knowing the syntax. It means knowing the standard library, the tooling ecosystem, how the language handles memory, and how experienced developers in that language actually structure a program. The goal for fluency is being able to read and write idiomatic code before moving on to another language.

The basics you need to know

When you’re navigating to a website on your browser, there are a few things that happen in the background to get you where you want to go. First, a Domain Name System lookup matches the URL you’re looking for with an IP address. An HTTP request is sent to a server, and the server sends back a combination of HTML, CSS and JavaScript codes. In turn, the browser turns that code into something you can look at on the screen. Almost every software engineering job will involve working within this sequence of events, so being super familiar with each step in the process means you’re less likely to be confused by error messages and log output.

Fixing the bugs

Within software development, debugging is the process of locating, isolating and fixing problems or ‘bugs’ in the system, so being able to understand the HTTP status codes that identify bugs (for example, 200, 404, 500), as well as headers and request/response structure is knowledge that will be essential on a daily basis. Almost every debugging conversation in a web-facing role begins with the question: ‘what did the request look like and what came back?’.

What Git is for

Git is a ‘version control system’, which means it tracks every change to your code over time. As well as tracking changes, it’s also extremely helpful when multiple developers are working on the same codebase, keeping it in sync and up to date. If two people make a modification to the same file, Git is often able to merge them automatically, or show how two people’s changes conflict. This ability to undo mistakes, work on new features without breaking existing code and collaborate across the team is why Git is used by every professional engineering team.

What to learn first

Start with four commands: git init, git add, git commit, and git push. After that, learn branching and merging, and then learn how pull requests work on GitHub, which is the process used to review and approve code changes at every software company.

Why is this important?

Although it’s possible to navigate through folders on a computer’s operating system by pointing and clicking in a graphical interface like Finder or Windows Explorer, most development tools are operated through a command line. This is a text-based interface that interacts with the computer’s operating system, where you type specific text commands to navigate, manage files and execute programs. This is a faster and more advanced way of working, and is standard in software development. It’s also a skill that you could learn in a basic way within a weekend or so, and will help you get up to speed with people around you.

What to know

The most important elements are being able to navigate directories, create and edit files, run scripts, and pipe output between commands. On Mac and Linux this is bash or zsh. On Windows, learn PowerShell or set up WSL (Windows Subsystem for Linux). You do not need to master shell scripting at this stage, just be comfortable enough to not freeze when a terminal opens.

Building Things

The basics you need

Applications have to store their data somewhere, and the most common storage layer is a relational database that’s accessed through Structured Query Language (SQL). SQL is the standard programming language that’s used to communicate with, manage, and extract data from relational databases. The important elements are how to create tables, insert data, query with the SELECT command, filter with the WHERE command, join tables together. It’s also important to understand what an index does and why it matters for performance.

Start with PostgreSQL

PostgreSQL, also known as Postgres, is a free and open-source relational database management system. It’s widely used in production, and what many job descriptions mean when they say “SQL experience.” Get familiar with it by installing it locally, creating a database, and building a small project that reads and writes to it. Understanding the difference between a database and a plain text file is the knowledge that will help you unlock a lot of what’s needed in future steps.

Why a project beats a course

Courses have their place, but they give you exercises with known solutions, and solutions that someone else has worked out. Real engineering work involves working through problems where no one is holding the answer back from you: you just have to work it out for yourself. Building a project of your own forces you to make decisions, debug issues that tutorials can’t cover, and end up with something you can show to an employer. Being proactive, resourceful and willing to learn on your own are qualities that will make you even more appealing to a hiring manager.

Picking the perfect project

It’s a fine balance, but the answer lies in building something small enough for you to finish, but interesting enough to keep you engaged. A to-do app is the canonical beginner project for a reason: it covers creating, reading, updating, and deleting data, which forms the basis of most web applications. Once you’ve got your project working and deployed somewhere (Vercel and Railway both have free tiers), you now have proof of your learning and ability.

What is an API?

An API (Application Programming Interface) is a defined way for one piece of software to talk to another, which allows computer programs to use services provided by other computer programs. For example, when the weather app on your phone shows the temperature and conditions today, it is communicating with a weather API, or when your shop’s website processes a payment, it is communicating with a payment API. Most applications we use today are not one single large program but a collection of different services communicating through APIs.

What you need to learn

REST (Representational State Transfer) conventions are a set of best practices and architectural constraints that developers use to create the most optimal web APIs. This means it’s important to learn REST conventions: GET to read data, POST to create, PUT or PATCH to update, DELETE to remove. As well as REST conventions, you should learn what JSON (JavaScript Object Notation) is and how to parse it. Use a tool like Postman or curl to call a public API manually before you write code that does it. Seeing the raw request and response helps you to get your head around the process.

Working Professionally

Why testing is essential

In a professional team, code that cannot be tested reliably becomes a liability. Every change risks breaking something unexpectedly. Tests let you change code with confidence and catch regressions before users do. Most engineering teams will not merge code without tests. It is not a bonus skill; it is part of the job.

Where to start

Write unit tests first. A unit test checks that a single function behaves correctly with a given input. In Python, pytest is the standard library. In JavaScript, Jest or Vitest. Write a test before you write the code (test-driven development), or write tests immediately after. The habit matters more than the order.

The path from code to production

Writing code on your laptop is different from running it for real users: it’s the difference between theory and practice. Teams developing software have a process where code is written before being pushed to a repository, then automated tests are run, and if they pass, the code is deployed to a staging environment for review, then to production. This process is called CI/CD (continuous integration/continuous deployment).

What to know

CI/CD is where GitHub Actions comes in really handy, as it allows you to automate software development tasks throughout the lifecycle of the project. Understand what environment variables are, and why secrets like API keys should never be hardcoded. At this point you should learn the difference between development, staging, and production environments, since these concepts come up in every software engineering job.

The skill that separates junior from mid-level

If we think of the pathway from junior to mid-level engineer, then it can partially be boiled down to the fact that junior engineers write code, while mid-level engineers write code that other people can work with. This difference shows up in variable naming, function length, comments, commit messages, and pull request descriptions. But fundamentally, the skill that is essential for a mid-level engineer is collaborative problem-solving.

How to practise this

Learn to work in the context of other people by contributing to an open source project. Even an action as simple as fixing a typo in documentation teaches you how to navigate an unfamiliar codebase, understand someone else’s decisions, and submit a change for review. The pull request process, handling reviewer feedback, and rewriting based on comments are skills that most bootcamps do not teach but every job requires.

Ready when you are

Put your skills to work.

Browse the latest jobs →

Subscribe to Career Resources

Get the latest career advice, industry insights, and job opportunities delivered to your inbox.