Sample report. Every candidate and score below is fictional, shown to illustrate what employers receive. Real reports are private, per-assessment secret links. Want to feel where these scores come from? Try the assessment yourself.
Assessment report
Cloud Security Analyst — Azure Storage Hardening
At a glance
Priya S. leads with 4 of 4 checks passed, in 38 of 60 min.
4 of 6 invited completed the assessment. Verified scores ranged 25% to 100% (avg 63%), and 1 candidate passed every check across all four competencies.
How this is scored. Every check below is verified against the live cloud environment each candidate worked in. Scoring reflects objective, measured outcomes only — we don’t infer soft skills or apply a hire / no-hire verdict.
Swipe the table sideways for correctness, time and reflection.
| Rank | Candidate & competencies | Checks | Correctness | Time used | Status | Reflection | Report |
|---|---|---|---|---|---|---|---|
| Rank 1 | Priya S. Cloud Security Analyst Objective correctness1/1Security rigor2/2Operational safety1/1 | 4 / 4 | 100% | 38 min / 60 | Submitted | Reflection submitted | View → |
| Rank 2 | Ananya K. Cloud Security Analyst Objective correctness1/1Security rigor1/2Operational safety1/1 | 3 / 4 | 75% | 51 min / 60 | Submitted | Reflection submitted | Private link |
| Rank 3 | Rahul M. Cloud Security Analyst Objective correctness1/1Security rigor0/2Operational safety1/1 | 2 / 4 | 50% | 57 min / 60 | Submitted | Reflection submitted | Private link |
| Rank 4 | Vikram T. Cloud Security Analyst Objective correctness1/1Security rigor0/2Operational safety0/1 | 1 / 4 | 25% | 60 min / 60 | Submitted | — | Private link |
Candidates are ranked by verified performance on a real, isolated Azure environment — not a quiz. On a live report, every row links to that candidate's full private breakdown — the first one is expanded below.
Candidate report
Priya S.
Verified checks passed
Competency profile
4/4 checks passedObjective correctness
Reached the required secure end-state — the core task.
- The storage account blocks anonymous/public blob accessPassed
Security rigor
Hardened properly: least privilege and defence in depth, not just the minimum.
- Secure transfer (HTTPS-only) is required on the accountPassed
- Shared Key (account-key) access is disabled; data access requires Microsoft Entra IDPassed
Operational safety
Secured the workload in place — didn't delete or break it to clear the alert.
- The storage account still exists (secured, not deleted)Passed
Written reflection
The candidate's own 3–5 sentence account of what they found and how they fixed it — proof they understood the problem, not just clicked through it.
The storage account had anonymous blob access enabled and Shared Key authentication active — meaning anyone with a storage URL could read files, and any leaked account key granted full data-plane access with no Entra audit trail. I disabled allowBlobPublicAccess and allowSharedKeyAccess on the account, and enforced HTTPS-only transfer. I verified the fix by attempting an unauthenticated GET on the seed blob — which returned 403 — before submitting.
This is what you get for every candidate.
Send a link, the candidate solves a real cloud security task in an isolated cloud environment, and you get a verified, side-by-side report. No résumé guesswork.