Career Verdict

A written call on your route, point-in-time.

The same seven things every time, applied to your inputs. Plateau zone, reality vs fantasy, what to sit and what to skip, the tradeoffs, the decisive factors, and what would change the call. It's allowed to come back as unrealistic. That's the product working, not failing.

Request a Career Verdict, £39 Or run the free Guided Route first

£39, one-off. Built for your inputs, yours to keep. Cheaper than a cert you didn't need.

Built on POST's practitioner-authored assessment framework, calibrated by James from twenty years across helpdesk, infrastructure and security. The framework is human-authored; the verdict applies it to your inputs.

The call · verbatim from a real verdict

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.

Request a Career Verdict, £39 Read the full sample first£39 · one-off · 48-hour turnaround

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.

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.

A real verdict

Read the full sample

Extract from a real verdictAnonymised. Partial. Identical to what £39 buys.

Career VerdictRef PA-2026-0418-SC18 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 your next five years hold up under scrutiny. Each cert ruled. Each year named. No hedging.

Inside this verdict

01The callRealistic / stretch / unrealistic, named.
02Where you standStrengths and gaps, weighed honestly.
03Route topologyFive years, plateau marked, salary plotted.
04Where the route breaksWhere the route quietly breaks, and the hidden years.
05What to sit and what to skipThree certs, three calls, in this order.

Prepared for

Sarah Chen

London · 3rd-line Infrastructure Engineer

Target window

2026 to 2031

Five-year route to Cloud Security

Verdict

Realistic, stretched

~60% on time

Compiled

18 April 2026

Inputs

CV · two role briefs

Length

Eight pages · ~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

Page 02 · 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

~60% on time

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.”

Page 03 · Starting position

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

Page 04 · The Misread

The frame the route turns on

Section 03 · The frame-shift

The misread

What's commonly believed

What matters more

Why this matters for you

Page 04 · Route topology

Route visible · reasoning withheld

Section 03 · The iconic page

Withheld in sample

The five-year 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

Salary trajectory · London, base only · reality vs fantasy

Withheld in sample

Reality

Fantasy

The gap

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.

Page 05 · Where this route breaks

One mode visible · two withheld

Section 04 · Operational realism

Withheld in sample

Where this route breaks

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.

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.
02
The cert-without-workload spiral.
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.

Page 06 · What would change this verdict

Shape visible · conditions withheld

Section 05 · Falsifiability

Withheld in sample

What would change this verdict

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.

01
Strengthens
02
Invalidates
03
Invalidates
04
Strengthens

Every verdict names the specific changes in ownership, scope, or context that would revise the call. The shapes are visible. The conditions themselves are in the paid copy.

Page 07 · What to sit and what to skip

One cert visible · rest withheld

Section 06

Withheld in sample

What to sit and what to skip

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.

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.

AWS Security Specialty

USEFUL, LATER

Read on a hiring panel

When in the route

What it replaces or pairs with

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.

Page 08 · What to do next

Instructions visible · the how withheld

Section 07

Withheld in sample

Decisive factors

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

01
Own one production workload, end to end.
The exact sequence
Line to put on your CV
Evidence it worked by day 30
02
Break things in Terraform, on purpose.
The exact sequence
Line to put on your CV
Evidence it worked by day 30
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 real anonymised dossier. Structure intact. Judgement-heavy parts written against the reader's route are withheld on the full sample page.

What you get

One dossier. Six answers.

The call
One diagnosis, named, falsifiable.
Where the route breaks
Named failure modes for this specific move.
Certs to ignore
Not just the ones to sit. The ones that look load-bearing and aren't.
Decisive moves
What to do in the next 30 and 90 days.
Alternative routes
The adjacent paths if this one comes back as unrealistic.
What would change the call
Specific changes in scope or context that flip the verdict.

Same six every verdict. Same framework, different inputs, different call.

What's in a verdict

Plateau zone

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

Reality vs fantasy

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

What to sit

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

What to skip

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

Tradeoffs

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

Decisive factors

The two or three things the call actually rests on.

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.

Why not just ask a general AI

Fair question. A general model will give you a tidy roadmap. Three certs, a plausible timeline, encouragement. It's averaging every article ever written about IT careers, which is mostly people selling something. So the output reads sensible and is hard to fault in the abstract.

The thing it won't do is tell you your specific route is one of the ones that stalls at year three because the hiring market for that title quietly stopped existing. It won't flag the cert you're planning that looks load-bearing and isn't. It won't say "this is fantasy" when it is. Hedging is the safe move for a general assistant, and it isn't for you. A verdict is allowed to be wrong, and it's allowed to be unwelcome. Those are the two things that make it useful.

How a Career Verdict is produced

The framework was created by James from twenty years across infrastructure, cloud and cybersecurity careers.
Your inputs are analysed against that framework.
The dossier is generated within the framework and reviewed before release.
POST will not promise shortcuts, guaranteed salaries or cert-driven career jumps.

If a verdict can't be honestly written for your situation, you get a full refund.

Avoid if

A Career Verdict isn't right for everyone.

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.

Price

£39One verdict. Yours to keep.

No subscription, no renewal, no "tier". One Guided Route run, one verdict, one price. If your situation changes meaningfully, run the route again and request a fresh one.

Request a Career Verdict, £39 Or run the free Guided Route first Read the sample first

£39, one-time. Delivered to your dossier shelf within 48 hours. No subscription, no renewal.

Common questions

Why isn't this a subscription?

A verdict is point-in-time. It's the call on your route as you've described it today. If your situation changes (new job, a move, a different constraint), you run the Guided Route again and request a fresh one. Recurring access to a static judgment would be dishonest.

Is this AI-generated?

Partly, and worth being honest about. The judgment layer is a rules-based framework: whether each cert is useful, where the plateau sits, whether the call is realistic, what the decisive factors are. That part is human-authored and calibrated against twenty years of doing the job. The narrative around those calls is assembled by a language model inside strict style rules. The model never decides the call. It writes the sentence that explains one. If a verdict reads like generic AI content, that's a bug.

What if I disagree with the verdict?

Good. The verdict is meant to be argued with, not obeyed. It names the tradeoffs and the decisive factors so you can push back from a sharper position than you started with. That's the point.

What if the inputs were wrong?

If the verdict was generated from clearly wrong inputs you couldn't correct at the time, email and we'll sort it. Disagreeing with the call isn't the same thing. The verdict is meant to be argued with.