Skip to main content

Sample · anonymised · partial

A real dossier, with the judgement-heavy parts withheld.

This is a Career Verdict written for an anonymised reader, rendered exactly as it arrives. The structure is intact. The cover, the call, the assumptions the call rests on, one failure mode and one cert ruling are shown in full. The parts that demonstrate the most personal judgement, the salary read, the tradeoff position, the remaining failure modes, the cert sequencing, the decisive factors, the revisability conditions, are deliberately withheld.

Why partial: a complete sample would let you read the report once and feel done with it. Withholding the personal parts is the honest move, because those are the parts written against your route, not someone else's.
POST ATLAS
postatlas.co.uk
Practitioner-authored · Prepared for a single reader
REF PA-2026-0418-SC

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

  1. 01The callRealistic / stretch / unrealistic, named.
  2. 02Where you standStrengths and gaps, weighed honestly.
  3. 03Route topologyFive years, plateau marked, salary plotted.
  4. 04Where the route breaksWhere the route quietly breaks, and the hidden years.
  5. 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 — 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 — 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 — 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 · 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.

  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.

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.

  1. 01
    Strengthens
  2. 02
    Invalidates
  3. 03
    Invalidates
  4. 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.

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.

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.

  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

Yours, against your route

Same frame. Written against the plan you actually have.

The withheld sections, the salary read, the tradeoff call, the remaining failure modes, the cert sequencing, the decisive factors, the revisability conditions, all written against your route. Arrives within 48 hours. £25, one-time, with a free re-issue inside 30 days if your situation shifts.