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.
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.
A real verdict
Read the sampleA real verdict looks like this
Worked example · SOC Analyst → Cloud Security EngineerStretch · 12–18 months
Credible move, but not a one-jump shift.
You're two roles away on the Atlas, not one. Most people make this jump via a cloud-aware SOC role or a junior cloud engineering seat first. Going direct is possible if you've already shipped IaC in anger and own a production AWS or Azure tenant outside work. Otherwise expect a sideways step.
What to sit and what to skip
AWS Security Specialty, Useful
Directly maps to the target role. Hiring panels read this as intent, not just exam-passing.
CCSP, Optional
Vendor-neutral and respected, but slow. Worth it once you're in the role, not as the thing that gets you there.
CISSP, Skip for now
Wrong cert for this move. CISSP is a seniority signal; you need an engineering signal. Park it for two years.
Cloud security at the engineering end means writing Terraform and reviewing pull requests, not just reading alerts. If you've not been shipping code in the SOC seat, that's the gap to close first. The certs won't.
Yours will look like this. Fill the form below to generate it.
A worked excerpt. The sample page shows the cover, the call, one failure mode and one cert ruling in full, and withholds the parts written against your route.
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.
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
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.
£25, 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.
Refunds?
If the verdict is unusable (for example, generated from clearly wrong inputs you couldn't correct), email and it'll be refunded. If you just disagree with the call, that's not a refund case. It's the product working.