Software Engineer (Backend / Full-stack)
Ship product, own services. Portfolio matters more than certs.
Still a strong career, but the entry market in 2026 is harder than the industry admits and the bar for juniors has quietly risen.
You actually like writing code most days, you can put a portfolio together that survives a code review, and you're prepared for the first eighteen months to be uncomfortable.
You picked it because the salary numbers looked good on LinkedIn. The job-market mismatch is real, and the people who succeed are the ones who'd write code anyway.
Phased progression
Foundations → first role → specialisation → advanced. The realistic order, not a script.
Salary figures are POST practitioner estimates, not survey data.
- 010–6 monthsFoundations
Literacy, lab habits, the cert that opens first conversations.
- 026–18 monthsFirst paid role
Land a Junior Software Engineer. Operational time, not more certs, earns the next move.
Junior Software Engineer£40–60k junior - 031.5–3 yearsSpecialisation
Add a specialist credential aligned to the work you're already doing.
AWS Cloud Practitioner£70–95k mid - 043+ yearsAdvanced
Move into adjacent roles. Long-term credentials become worth their cost.
DevOps Engineer£160k+ staff (UK; London fintech / scale-ups higher)
- 01Foundations0–6 months
Literacy, lab habits, the cert that opens first conversations.
- 02First paid role6–18 months
Land a Junior Software Engineer. Operational time, not more certs, earns the next move.
Junior Software Engineer£40–60k junior - 03Specialisation1.5–3 years
Add a specialist credential aligned to the work you're already doing.
AWS Cloud Practitioner£70–95k mid - 04Advanced3+ years
Move into adjacent roles. Long-term credentials become worth their cost.
DevOps Engineer£160k+ staff (UK; London fintech / scale-ups higher)
Certification sequence
Ordered by realistic relevance, not vendor marketing.
- AWS Cloud Practitioner
- AWS Developer Associate
- Terraform Associate
Practical projects
What to actually build, the portfolio that opens interviews.
- Ship one real product to public users (web, CLI or mobile)
- Contribute three non-trivial PRs to an open-source repo
- Build a small service with auth, persistence and CI from scratch
- ·AppSec via security curiosity
- ·Data engineering via SQL-heavy work
Realistic expectations
What no recruiter will tell you.
That a bootcamp is enough. It opens the door for some people. Most successful juniors right now have a bootcamp plus a year of public projects, contributions or contracting on top.
Twelve to twenty-four months from zero to first developer role is the honest range, and the upper end is more common than the lower. Don't believe the three-month bootcamp marketing.
What this is based on
Practitioner judgement. External evidence review pending.
Last reviewed: not yet reviewed · UK market
Where this fits
A pathway is a sequence, not a destination. Here are the roles and certs along it.
- Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
- Cloud Engineer → Cloud Architect
Highest-paid generalist track. Stack: networking + Linux + cloud + IaC.
- IT Support → Sysadmin (the honest on-ramp)
The realistic first paid technology job. No shortcuts, but the cleanest gateway into every other world.
- Bootcamp vs self-taught. The question is wrong
In progress. Neither route is the actual differentiator. What matters is the thing both routes leave out.
- DevOps vs platform engineering. What actually changed
In progress. It isn't a rename. The hiring bar, day-to-day, and career ceiling are all different. Most candidates pick the wrong one.
The next step
The pathway is plausible. Whether it holds for five years is a different question.
A Career Verdict applies the framework to your actual stage and stack: what holds, what breaks, what would change the call.
A route shows what is possible. A Career Verdict makes the call.
Career Verdict
Helpdesk → Security Architect
- 01The callA clear judgement on whether your route is realistic, and under what conditions.
- 02Where the route breaksThe most likely point to stall, and why it happens in practice.
- 03What to do nextSpecific priorities for the next 6–24 months, and what to drop.
Career Verdict
- The callA single written judgement on whether the route is realistic for you.
- Plateaus and failure modesThe flat years and the specific ways this route tends to stall.
- Where you standThe strongest and weakest parts of your current position, named.
- Salary realityWhat this route actually pays, set against what you've been told it pays.
Usually within minutes of payment. Kept 24 months, then deleted. Deletion on request at any time.
Built on POST's practitioner-authored assessment framework, informed by two decades across helpdesk, infrastructure and security. The verdict applies that framework to your inputs.