Skip to main content
POST ATLAS

The final stage · Verdict

Get a practitioner's judgement on your route.

A clear, written verdict based on your route, POST's maintained career framework and practitioner experience in UK tech.

POST ATLASVerdict no. PA-2026-0512
Career analysis report

Career Verdict

Helpdesk → Security Architect

“Realistic, but not by adding another certification.”
  1. 01
    The callA clear judgement on whether your route is realistic, and under what conditions.
  2. 02
    Where the route breaksThe most likely point to stall, and why it happens in practice.
  3. 03
    What to do nextSpecific priorities for the next 6–24 months, and what to drop.
Generated within POST’s practitioner-authored assessment frameworkPOST ATLAS

Get a judgement on your route

Your current position → your target role

£39

One-off payment. No subscription.

  • A direct call on whether it is realisticBased on your route, POST's maintained framework and practitioner experience.
  • The point most likely to stallA clear analysis of where it breaks down, and why.
  • What to prioritise and what to dropFocused, practical next steps for the biggest impact.
Request my Career Verdict Read the full sample
Private Delivered by email Kept 24 months, then deleted. Deletion on request at any time.

The call · Composite built from several reports

PA-2026-0512
“No, not in four years. The title you're aiming at isn't the job you think it is.”

Helpdesk to Security Architect in four years. The verdict came back “Unrealistic in this window.” That is the product working, not failing.

Avoid if

  • You want a course, a roadmap, or step-by-step instructions. This is judgment, not information.
  • You want reassurance. The verdict can come back as 'unrealistic' and explain why.
  • You haven't done the Guided Route yet. The verdict is generated from those answers, so without them there's nothing specific to write.

Why a Verdict exists when the route is free

A route shows what's possible. A Verdict judges whether it's realistic for you.

The Guided Route is free and stays free. It shows how people typically get from where you are to where you're aiming. The Verdict is the next question: does that route actually work, given your experience, constraints and timeline.

Free Guided Route

Career Verdict, £39

  • Shows a path
    Judges a path
  • Generic to the role
    Personal to your inputs
  • What people usually do
    Whether it's realistic for you
  • A route map
    A call, with the tradeoffs named
  • Doesn't know your timeline or constraints
    Names the bottleneck most likely to stop you
  • Another list of options
    Tells you what to ignore as well as what to do

Neither is better. They answer different questions. Most people only need the route. Some need the call.

A composite verdict, annotated

Read the full sample
Extract from a composite verdictAnonymised. Partial. Identical to what £39 buys.

Five-year route to Cloud Security · Realistic, stretched · 2026 to 2031

Career Verdict18 April 2026
POST ATLAS
postatlas.co.uk
Practitioner-authored · Prepared for a single reader

Verdict report · Five-year

Career Verdict

A written call on whether the route you have written holds up under scrutiny. Each cert ruled. Each year named. A clear call with its assumptions exposed.

Inside this verdict

  1. 01The callThe call on your route as written.
  2. 02Where you standWhere you actually stand, strengths and gaps weighed.
  3. 03The routeThe five-year route, with the plateau marked.
  4. 04Certification rulingsCertification rulings: what to sit and what to skip.
  5. 05Failure modesThe failure modes that quietly end this route.
  6. 06Salary realitySalary reality: what the data shows vs the fantasy.
  7. 07Progression conditions: months 4 to 36Progression conditions: what must become true between months 4 and 36.

Prepared for

Composite reader (illustrative)

London · 3rd-line Infrastructure Engineer

Target window

2026 to 2031

Five-year route to Cloud Security

Verdict

Realistic, stretched

Realistic, stretched on the stated timeline

Compiled

18 April 2026

Inputs

CV · two role briefs

Length

Seven sections · ~2,900 words

Re-issue

Free, within 30 days

Input confidence

How solid the things this verdict rests on actually are
  • Current roleHighCV + role brief
  • Target roleHighTwo role briefs
  • TimeframeMediumSelf-reported
  • Salary expectationsMediumRange, not band
  • Route assumptionsLowInferred from plan
01 · The call
Verdict on the plan as written

Section 01

The call

Realistic, stretched

Yes, but only if you clear the year-three plateau properly.

The shape of the move is fine. Infrastructure into cloud security is one of the better-trodden routes right now, and your eight years on Windows and network gear gives you something most candidates haven't got. Where the plan wobbles is the middle. You've written it as a steady climb. It isn't. There's a flat eighteen months between cert two and cert three where most people quietly stall, and your current employer hasn't the cloud workload to push you through.

Verdict

Realistic, stretched

Realistic, stretched on the stated timeline

Time window

Five years, just

Likely six in practice

Single risk

The plateau

Months 18 to 36 are the test

Assumptions under test

The conditions this call rests on, named so you can disagree

This verdict holds if

  • You stay in environments with hands-on cloud exposure, not adjacent to it.
  • You can argue your way into owning one production AWS account inside year one.
  • You're willing to change employer at year two if the cloud work doesn't materialise.
  • You treat months 18 to 36 as the actual test, not the certs either side of it.

It weakens if

  • You move into governance or audit-only work before year three.
  • You stack a third cert in place of owning a real workload.
  • You optimise for the next title rather than the next stretch of responsibility.
  • You stay at an employer with no cloud roadmap past year two.
“The plan holds up. The cert order doesn't, and the year-three plateau will eat anyone who treats it as a study problem.”

What would change this call

Named conditions, not personal development

The call above isn't a permanent reading. It rests on what you currently own, where you currently sit, and what your next role actually puts you near. Here are the specific changes in your situation that would make me revise it, in either direction.

  • If you move into a role with your name on one production AWS account, end to end, inside year one.

    The plateau the verdict centers on is months 18 to 36 with no owned workload. Owning one shrinks that plateau to the cert order and nothing else.

  • If your current employer's cloud roadmap stays a slide deck and you sit through a second year of Windows-and-AD tickets.

    Two years adjacent to cloud reads on a CV the same as two years away from it. The internal-mover ceiling becomes the binding constraint and the call moves from Stretch to Unrealistic.

  • If the next move is into governance, audit, or cloud-policy work before year three instead of platform ownership.

    Cloud security hires from people who've operated the systems they're now defending. A governance pivot is a different route, not a faster one, and the verdict for that route is a separate call.

  • If you end up in a post-incident review for a cloud workload you helped design, even partially.

    Operational credibility in cloud security is built in post-incident reviews, not exams. One named incident with your fingerprints on it changes how the next hiring manager reads the rest of the CV.

02 · Where you actually stand
Titles visible · reasoning withheld

Section 02

Withheld in sample

Where you actually stand

Working for you

  • Real infra time

  • On-call instinct

  • PowerShell at depth

Working against you

  • No cloud ownership

  • Zero IaC in anger

  • Compliance blind spot

An honest aside

03 · The route
Route visible · reasoning withheld

Section 03

Withheld in sample

The route

Where the plateau sits, and what clears it.

Plateau zone

3rd-line Infra

Now

AWS-aware

Yr 1

Cloud engineer

Yr 2

Stall risk

Yr 3

Cloud sec analyst

Yr 4

Cloud security

Yr 5

milestone you control
where most people stall
What's commonly believed

What matters more

Why this matters for you

Tradeoff spectrum · this route, not in general

breadth · audit · GRCdepth · ops · ownership

Where this specific plan sits on the breadth/depth axis is in the paid copy. One sentence, but the one most readers screenshot.

04 · Certification rulings
One cert visible · rest withheld

Section 04

Withheld in sample

Certification rulings

Each one is judged against the move you've actually written, not against the industry in general. A cert can be brilliant and still be the wrong call here.

01

AWS Solutions Architect Associate

USEFUL

Do it first. Inside three months. Not because it's hard, but because it gives you the vocabulary to ask for cloud work at your current job. Without that conversation, you don't get the workload, and without the workload, every cert after this one is theatre.

02

AWS Security Specialty

USEFUL, LATER
Read on a hiring panel
When in the route
What it replaces or pairs with
03

CISSP

SKIP, FOR NOW
Read on a hiring panel
When in the route
What it replaces or pairs with

One cert shown in full so you can read the voice. The rest are ruled the same way, against your stage and the order they should be sat in.

05 · Failure modes
One mode visible · two withheld

Section 05

Withheld in sample

Failure modes

Most cloud-security plans don't fail at the exam. They fail at three quieter points, every time. Naming them is the difference between getting through year three and quietly drifting out of the route.

  1. 01

    The reading trap.

    You read AWS docs for a year, sit the exam, and still can't be trusted with a production account. Hiring managers ask one scenario question and the gap shows in under a minute.

  2. 02

    The cert-without-workload spiral.

  3. 03

    The internal-mover ceiling.

The first failure mode is shown in full so you can hear the voice. The remaining two are the ones most readers don't see coming, which is why they're in the paid copy.

06 · Salary reality
Shape visible · numbers withheld

Section 06

Withheld in sample

Salary reality

London market, base only. The gap between what the data shows and what the plan assumes.

Withheld in sample

Reality

Fantasy

The gap

07 · Progression conditions
Conditions visible · the how withheld

Section 07

Withheld in sample

Progression conditions: months 4 to 36

If the plateau is the test, these are the three things that determine whether you clear it. Treat anything else as optional.

  1. 01

    Own one production workload, end to end.

    The exact sequence
    Line to put on your CV
    Evidence it worked by day 30
  2. 02

    Break things in Terraform, on purpose.

    The exact sequence
    Line to put on your CV
    Evidence it worked by day 30
  3. 03

    Find one person already in the role.

    The exact sequence
    Line to put on your CV
    Evidence it worked by day 30

Last word

Read the full sample verdictStructure intact. Judgement-heavy parts withheld.

The actual Career Verdict format, rendered from a composite built from several real dossiers with identifying details fictionalised. Structure intact. Judgement-heavy parts written against the reader's route are withheld on the full sample page.

01

Plateau zone

Where this specific route tends to stall, and at which year.

02

Reality vs fantasy

Whether the call is realistic, stretch, or unrealistic. Stated, not hedged.

03

What to sit

The certs and steps that are doing real work on this route.

04

What to skip

The certs and steps that look load-bearing and aren't.

05

Tradeoffs

What you give up by choosing this route over the adjacent ones.

06

Decisive factors

The two or three things the call actually rests on.

07

What would change the call

The specific changes in ownership, scope or context that would flip the verdict. Falsifiable, not motivational.

Seven sections, every verdict. Same framework, different inputs, different call.

Three verdicts, three different calls

The same seven sections. Different inputs. Different verdict.

Short excerpts from three real anonymised dossiers. The point isn't the writing. It's that the call comes out differently each time, and the reasoning is specific to the reader, not the route.

Realistic

Three years on a UK service provider NOC. CCNA done, CCNP ENCOR in progress. Targeting Network Engineer inside twelve months.

The route holds, but certs are the floor and clean change records are the gate.

Your CCNP looks good on paper. If your CV doesn't also show named ownership of production changes, it gets filtered. The interview question that exposes the gap is 'walk me through the last change you rolled back'. The work that moves you is getting your name on the author line of low-risk changes in your current NOC, not more lab hours.

What would change the call

If the next role gives you a structured ramp on change implementation with direct supervision, the timeline holds. If it lands you back in a watch-only seat, the twelve months disappear.

Unrealistic

Career changer, six months in. No IT role yet. Security+ booked, AWS SAA next. Targeting Cloud Security Engineer in twelve months.

Not from here, not in twelve months. The plan compresses years the role won't compress.

Cloud Security hires people who have already been burned by a production IaC deployment. Operational scar tissue is the currency. TryHackMe rooms and a single EC2 instance don't build it, and stacking AWS SAA on top doesn't substitute for it. The honest version of this route puts you in a Junior Cloud Ops or DevOps support seat first, somewhere that runs Terraform in production, then the move comes from inside that seat.

What would change the call

If you can land an IaC-adjacent ops role inside six months, the call changes by month eighteen. Without that seat the cert stack is collateral on a route you can't walk.

Stretch

Eight years infrastructure. Two ISO 27001 audits as the infra signatory. Targeting GRC Analyst in financial services, Bristol, nine months.

Doable, but not on this timeline and not in this market without an internal move.

Your audit exposure is real, but you've participated in controls, you haven't owned one end to end. The Bristol GRC market is thinner than London at the entry-to-mid level, and most seats expect prior dedicated GRC time. The thing that closes the gap isn't another cert, it's a control where your name is on the documentation, you brief the auditor, and you sign off the remediation.

What would change the call

An internal transfer to a dedicated GRC team inside six months makes the timeline real. A cold external move into a Bristol-only search at your salary floor does not.

Excerpts from three real generated verdicts. Reader details lightly anonymised. Calls, reasoning and revisability clauses intact.

Before you pay

What you are buying, and what happens if it goes wrong.

What you get

A written dossier of seven sections, on screen as a private link and as a PDF. No account, no renewal.

When you get it

Usually within minutes of payment. Always within 24 hours. A draft that fails the writing checks is held rather than released as if it passed. You get an email either way. If 24 hours passes with nothing, you get a full refund.

How it is produced

The judgement layer is a practitioner-authored, rules-based framework informed by two decades across infrastructure, cloud and cybersecurity. Your inputs are assessed against that framework. A model writes the prose inside strict rules; it does not decide the call.

If it is wrong

Email and say so. Wrong inputs you could not correct at the time get a corrected dossier at no cost. If a verdict cannot be honestly written for your situation, or the dossier does not arrive, you get a full refund, no argument. Disagreeing with the call is not a fault; the verdict is meant to be argued with.

Your data

Your answers and email are held to produce and re-deliver your dossier, and for nothing else. No accounts, no profiling, no selling on. Your report, your inputs and your access link are kept for 24 months from purchase so you can come back to them. After that they are deleted and the link stops working. Ask for deletion sooner and it goes at once.

What it will not do

It will not promise a salary, a timeline or a job. It will not hand you a course or a step-by-step roadmap. It is a point-in-time call on the route you described, and it is allowed to come back unwelcome.

Questions before buying go to contact. Terms and privacy sit on the legal page.

Is this AI-generated?

Partly, and worth being honest about. The judgement layer is human-authored: whether each cert is useful, where the plateau sits, whether the call is realistic, what the decisive factors are. The narrative around those calls is assembled by a language model inside strict style rules. If a verdict reads like generic AI content, that is a bug.

Why is it not a subscription?

A verdict is point-in-time. It is the call on your route as you have described it today. If your situation changes, run the Guided Route again and request a fresh one. Recurring access to a static judgement would be dishonest.

Do I need an account?

No. After payment you get an email with a link that grants access on whichever device you open it on.

How long do you keep my dossier?

Your report, your inputs and your access link are kept for 24 months from purchase so you can come back to them. After that they are deleted and the link stops working. Ask for deletion sooner and it goes at once.

How your information is handled

Your report, your inputs and your access link are kept for 24 months from purchase so you can come back to them. After that they are deleted and the link stops working. Ask for deletion sooner and it goes at once.

Price

£39One-off payment. No subscription.
Request a Career Verdict, £39Or run the free Guided Route first