UK Career Change · 2026
IT Support to Software Engineer
Difficulty
Moderate
Typical timeline
12-24 months
From → To
Tech → Tech
IT support to software engineer is one of the cleanest internal-tech transitions in UK 2026. The candidates already understand systems, troubleshooting, and customer-facing technical work — they just need to add programming depth. The 12-24 month timeline reflects the time needed to build a credible portfolio while still working IT support. Most successful transitions happen within the same company first via internal moves, then external moves to junior or mid-level engineering roles.
Salary impact
Initial entry £30-40k similar to senior IT support; reaches £55-80k at mid-level engineer in 2-3 years
Why this transition works
- ✓IT support staff already understand systems, networking, troubleshooting — half of what engineers need
- ✓Customer-facing technical communication is a rare engineer skill, well-developed in support
- ✓Internal transitions at the same company are common and have high success rate
- ✓The progression IT support → DevOps → SRE → infrastructure engineer is well-trodden
The hard parts (don't skip these)
- !Programming fluency from scratch is genuinely hard alongside full-time support work
- !Some IT support roles aren't recognised as proper engineering experience by external hiring managers
- !First-role pay drop possible if moving from senior IT support (£40-50k) to junior engineer (£32-38k)
- !Imposter syndrome — many transitioners feel they're not 'real engineers' for 12-18 months after the move
Step-by-step plan
- 1
Pick a stack tied to support work
Python (automation), JavaScript (web), or DevOps stack (Bash, Terraform, Kubernetes). Match the stack to your support work — Python for scripting-heavy roles, DevOps for infrastructure roles. Don't learn three at once.
- 2
Automate things at your current job
Find 3-5 repetitive support tasks and automate them. The automation becomes your portfolio. Document each: problem, code, time saved. This is rare credible engineering experience that bootcamp grads can't fake.
- 3
Build 2-3 personal projects
Beyond automation: a personal CLI tool, a small web app, or contributions to open-source projects relevant to your stack. Each with GitHub repo, README, and clear documentation.
- 4
Internal transition first
Talk to your engineering or DevOps team about helping with infrastructure projects. Most companies welcome support staff doing engineering-shaped work and the internal transition has 80%+ success rate.
- 5
External transition to junior or mid-level
Target junior software engineer, junior DevOps, or platform engineer roles at companies that hire from non-traditional backgrounds — Capgemini, Multiverse partners, growth-stage SaaS with apprenticeship programmes.
- 6
Frame support experience as engineering credibility
"3 years of production troubleshooting" reads as on-call experience, which is rare engineering signal. "Automated 4 manual processes saving 12 hours/week" reads as engineering work. Translate but don't hide.
CV adaptations for this transition
- →Lead with portfolio + automation projects, not support tickets count
- →Translate support work to engineering vocabulary
- →Surface specific tools and systems used (Linux, Bash, Active Directory, networking)
- →List relevant certifications (CompTIA, AWS, Linux, Kubernetes)
Red flags that derail this transition
- ✗Pure support CV with no automation or personal projects
- ✗Aiming for senior engineer roles directly — flags wrong-level applicant
- ✗Multi-stack scattergun without commitment
- ✗Hiding support background — comes across as dishonest in interview