Security Automation Engineer
SOAR playbooks, glue scripts, ticket enrichment, replacing your own toil.
A small but quietly excellent niche. Take it if you can code properly and security tooling actually interests you, skip if either is missing.
- Domain
- Cybersecurity
- Entry
- £32–52k
- Senior
- £95–135k
- You can write maintainable Python and read someone else's without complaining
- You enjoy turning manual workflows into reproducible ones
- You're patient with vendor APIs that lie
- You like being measured on time saved, not tickets closed
- You see SOAR as a checkbox rather than a software project
- You don't enjoy maintaining what you build long after it's interesting
- You haven't done security ops work yourself, you'll automate the wrong things
What "doing well" looks like in the seat
- Your playbooks survive personnel changes in the SOC
- Analysts ask for changes rather than working around your automation
- You can quantify hours returned to the team each quarter
- Your code passes review from the platform team, not just the security team
The market is shallow and the title varies wildly. At one org you'll be a senior engineer reporting into security with real autonomy, at another you'll be the SOAR person who tweaks playbooks the vendor shipped. Interview for who owns the code, what languages they actually write in, and how much of the automation is real software versus drag-and-drop. If it's mostly drag-and-drop, your skills won't travel.
Tradeoffs at a glance
Hover any chip for the calibrated meaning. Ratings are directional, not absolute.
Promotion ceiling
Moderate to high. Often a stepping stone to detection or platform sec.
Who actually gets in
- +Senior SOC who codes
- +Detection Engineer
- +DevSecOps
Common misconceptions
- −That it's a junior role. Needs real Python and security domain knowledge.
Where this leads
- Detection Engineering
- DevSecOps
- Platform Security
Tech you'll see
- Python
- Logic Apps
Pathways that pass through here
What this is based on
Practitioner judgement. External evidence review pending.
Last reviewed: not yet reviewed · UK market
The next step
You've read about the role. The harder question is whether it's the right one for you.
A Career Verdict is the written, practitioner-authored call on your specific route into and out of this role. Six primitives, same format every time.
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.