The evidence statuses and application decision come from POST's fixed rules for the target role. Generated prose may explain those decisions, but cannot change them.
Explanation used: fixed rules wording.
CV Reality Check
Your report
- Reviewed for
- Cloud security engineer
- Mid · United Kingdom
- Role evidence reviewed September 2026
Overall verdict
Plausible target. Your CV does not prove it yet.
The document points towards this target, but key areas need stronger evidence before it convinces.
Based only on the CV and the answers you supplied. This judges the document, not you, and it does not predict whether an employer will hire you.
What to do next: Revise before applying
What your CV proves today
Only requirements supported by paid work are shown here. Home-lab evidence stays separate.
No target-role requirement is proven through paid work in the document yet.
Evidence matrix
What the document proves for this role, what it merely claims, and what is missing. Paid work and home-lab activity are counted separately.
Cloud platform work in a paid environment
Partial
"Exposure to Azure administration tasks"
Security controls configured, not just named
Missing
Nothing in the document supports this yet.
Cloud identity and permissions work
Missing
Nothing in the document supports this yet.
Infrastructure defined as code
Missing
Nothing in the document supports this yet.
Cloud logging or monitoring owned
Missing
Nothing in the document supports this yet.
Work carried out under a ticketing or change process
Missing
Nothing in the document supports this yet.
Named responsibility for something in production
Missing
Nothing in the document supports this yet.
Scale and environment stated in numbers
Missing
Nothing in the document supports this yet.
An outcome, not just an activity
Missing
Nothing in the document supports this yet.
Recruiter scan
What a technical recruiter takes from the first twenty to thirty seconds.
Twenty seconds in, a recruiter reads an IT support analyst at a media company who mentions Azure once. The target on the covering note says cloud security, and nothing in the employment block backs that turn yet, so the CV gets filed as support rather than security.
Hiring-manager scan
What the manager looks for, and where they stop finding it.
A cloud security manager looks for a control you configured, an identity task you owned, and a log source you were responsible for. None of the three appear. The Azure line is the only foothold, and it describes exposure rather than work carried out.
Credibility risks
Places where the document invites a question you would rather not be asked.
Several lines describe proximity to work rather than work carried out.
Exposure to Azure administration tasks · Involved in security awareness campaigns
Priority corrections
Ranked by what changes a reader's judgement most. Rewrites use only facts already in your CV.
- 1
Name what you did with Azure, not that you were near it
The line states exposure. A reader cannot tell whether you administered anything, so the strongest claim in the document is also the vaguest.
Your line: "Exposure to Azure administration tasks"
Rewritten from that line: "Carried out Azure administration tasks alongside the support queue at Northgate Media."
- 2
Say what your part in the security campaigns was
Involvement describes proximity. The role you are targeting is judged on ownership, and the document currently claims neither.
Your line: "Involved in security awareness campaigns"
Rewritten from that line: "Took part in security awareness campaigns at Northgate Media, in support of the wider programme."
- 3
Give the support work a number
Scale is the fastest way a reader calibrates a support role. Your CV has none, so it reads smaller than it may be.
- 4
Replace the generic skills with tools you have actually used at work
Communication and teamwork cost you a line each and prove nothing about a cloud security seat.
- 5
Show what SC-900 changed about the work you do
A foundation certification alone does not move this target. Tied to something you then did, it starts to.
Your document
- Your uploaded file is deleted on 17 September 2026.
- This report and the structured record are removed on 15 December 2026.
- The link to this report expires on 15 December 2026 and is yours alone.
- Nothing you uploaded is used to train a model.
Rules version cv-2026-09-a
Basis and limitations
How the judgement is made
Basis: the uploaded CV, your confirmed corrections and your five answers.
Limits: no employer records, references, interview evidence or private hiring data were checked.
Extraction confidence: high.