Software Engineer
Builds and changes the software a business runs on, and lives with the consequences once real people use it.
Role at a glance
The shape of the job
Pay bands are TechWaymark practitioner estimates for UK roles, reviewed 2026-09, not survey data. They vary by region, sector and employer.
What the Software Engineer role involves
- You take a feature or bug, work out what needs to change, write the code and the tests, and get it reviewed.
- You read far more code than you write. Most of the job is changing existing systems safely.
- You work with product managers, designers and other engineers to decide what's worth building and how.
- When something breaks in production, you help find out why and make sure it doesn't happen the same way again.
Read TechWaymark's full role verdict and reasoning
Software engineering delivers maintainable behaviour under real requirements and constraints.
- Domain
- Platform / DevOps
- Entry
- £34–45k
- Senior
- £60–80k
- You enjoy the craft, debugging at 11pm should sound bearable
- You're prepared to keep learning languages and paradigms for years
- You can read and review other people's code patiently
- You want to develop deeper expertise or technical leadership
- You're chasing the salary without enjoying the work
- You'd resent code review or pair programming
- You expect AI tools to remove the need to understand what you're shipping
What "doing well" looks like in the seat
- Your PRs are merged with minor feedback, not full rewrites
- You're trusted on cross-team design conversations
- Your incident response is calm and your post-mortems improve things
- Your test coverage and observability are part of how you ship, not afterthoughts
Tool fluency does not replace understanding failure and change. Ask about review quality, ownership and how engineers learn from production outcomes.
Illustrative
A day in the role
- Stand-up. Yesterday's bug fix is in review, today is the new checkout validation
- Read the existing checkout code before touching it. Find two places that need to change
- Review a colleague's pull request. Ask about an edge case with empty baskets
- Write the change and tests. One test fails for a reason that turns out to be a real bug
- Quick call with the designer about an error message wording
- Open the pull request with a clear description of what changed and why
An example day. Roles and organisations vary, and no two days match.
Day to day
What you'll work with
Systems
Tools
Concepts
Hiring reality
What employers actually expect
Must understand
- Write working, readable code in at least one language
- Use Git and work through code review
- Test your own changes
- Ask when you're stuck
Commonly expected
- A degree, bootcamp or equivalent evidence
- Web and database basics
- Some cloud exposure
- Projects on GitHub
Sets you apart
- A project with real users
- Clear written pull requests
- Debugging a production issue
- Understanding the business the code serves
What this role isn't
It isn't sitting alone writing new code all day. Most time goes on reading, reviewing, testing, talking and changing existing systems without breaking them.
How the role changes with seniority
Works on well-defined tickets with support, learns the codebase and the team's habits.
Delivers features alone, reviews others' work, handles on-call and messy bugs.
Shapes design decisions, spots risk early, unblocks others and makes the team better.
Nobody puts this in the advert
The hard parts
A tough junior market
Entry-level roles attract a lot of applicants. Evidence of real, finished work matters.
Legacy code
Much of the job is working on code written years ago by people who've left.
Constant change
Tools and frameworks move quickly. The fundamentals last longer than any one library.
On-call
Many teams share responsibility for live systems, including the odd night call.
More than one way in
How people actually get into it
Degree and graduate scheme
The most common route into larger employers.
Apprenticeship
Software developer apprenticeships combine paid work with training.
Bootcamp plus portfolio
Works best when the portfolio shows finished, tested projects rather than tutorials.
Internal move
Testers, analysts and support staff sometimes move into development within the same firm.
Evidence employers value
"Proficient in React and Node"
Built a booking app for a local club that's used weekly, with tests and a short write-up of what went wrong
"Team player"
A pull request where review feedback changed your approach, and why it was better
"Completed 50 coding challenges"
Fixed a bug in an open-source project and got the change merged
Projects that prove it
Small pieces of work you can do on your own, and what each one shows an employer.
Build something small that someone uses
3-4 weekendsA tool for a club, family or friend. Keep it small, deploy it, and fix the first three problems they report.
What it demonstrates
Contribute to open source
2-3 eveningsFind a small labelled issue in a project you use, fix it, and work through the maintainers' review.
What it demonstrates
Add tests to your own old project
2 eveningsGo back to something you built, write tests for it, and fix whatever they uncover. Write a short note on what you found.
What it demonstrates
Your next hops
Where Software Engineer can take you
Other common branches
There is no single ladder. See the routes on the Atlas.
Interview reality
Questions you may be asked
Loading questions…
Practise with model answers in My WaymarkFor educators
Used in TechWaymark Education
These modules use this page as investigation material in the classroom.
- 1Technology is not one career
An example of work that mainly builds technology, and how it differs from running or protecting it
Could you realistically get here from where you are?
The Guided Route compares your background with this role and shows the honest route, hop by hop.
Last reviewed 2026-09. Photographs are illustrative.