Composite built from several reports · partial
A composite dossier, built from the real format with identifying details fictionalised, and the judgement-heavy parts withheld.
This is a composite, assembled from several real dossiers with identifying details fictionalised, rendered exactly as a verdict arrives. The structure is intact: seven sections from The call through Progression conditions. The cover, the call (including what would change it), where the reader actually stands, and the route stops are shown. The judgement-heavy prose, the misread, the salary numbers, the failure-mode reasoning, the cert sequencing, the decisive factors and the revisability details are deliberately withheld.
Five-year route to Cloud Security · Realistic, stretched · 2026 to 2031
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
- 01The callThe call on your route as written.
- 02Where you standWhere you actually stand, strengths and gaps weighed.
- 03The routeThe five-year route, with the plateau marked.
- 04Certification rulingsCertification rulings: what to sit and what to skip.
- 05Failure modesThe failure modes that quietly end this route.
- 06Salary realitySalary reality: what the data shows vs the fantasy.
- 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
Section 01
The call
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 disagreeThis 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 developmentThe 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.
Section 02
Withheld in sampleWhere you actually stand
Real infra time
On-call instinct
PowerShell at depth
No cloud ownership
Zero IaC in anger
Compliance blind spot
An honest aside
Section 03
Withheld in sampleThe 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
Why this matters for you
Tradeoff spectrum · this route, not in general
Where this specific plan sits on the breadth/depth axis is in the paid copy. One sentence, but the one most readers screenshot.
Section 04
Withheld in sampleCertification 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.
AWS Solutions Architect Associate
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
CISSP
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.
Section 05
Withheld in sampleFailure 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.
- 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.
Section 06
Withheld in sampleSalary reality
London market, base only. The gap between what the data shows and what the plan assumes.
Reality
Fantasy
The gap
Section 07
Withheld in sampleProgression 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.
- 01
Own one production workload, end to end.
The exact sequenceLine to put on your CVEvidence it worked by day 30 - 02
Break things in Terraform, on purpose.
The exact sequenceLine to put on your CVEvidence it worked by day 30 - 03
Find one person already in the role.
The exact sequenceLine to put on your CVEvidence it worked by day 30
Last word
Yours, against your route
Same frame. Written against the plan you actually have.
The withheld sections, the misread, the salary read, the tradeoff call, the remaining failure modes, the cert sequencing, the decisive factors, the revisability conditions, all written against your route. Usually within minutes of payment, always within 24 hours. £39, one-time, with a free re-issue inside 30 days if your situation shifts.