Free sample
CV Evidence Review: worked example
Synthetic test case
Your own review is £19, including a PDF, revision worksheet and one recheck within 30 days.
Review my CV · £19Read the invented input CV
PROFILE IT support analyst investigating a move into cloud security. Experience supporting users and documenting access issues; seeking supervised cloud security responsibilities. EXPERIENCE IT Support Analyst, Example Services, January 2023 to present Resolved user access and application support requests through the team ticket queue. Recorded symptoms, checks and escalation notes for the engineers responsible for the service. Investigated repeated access failures by comparing affected and unaffected users with an identity engineer. Documented the observed difference and asked the engineer to review the proposed next check. The engineer owned the permissions change. Wrote a handover guide for recurring account queries. Asked a colleague to follow the instructions, recorded where they needed clarification and revised the guide. No measured time saving is claimed. Supported an approved device replacement exercise by checking the user checklist and recording unresolved application issues. Escalated policy exceptions to the endpoint administrator. Helped gather records requested for a service review, keeping the original ticket references and separating completed work from outstanding actions. The service manager owned the review and improvement decisions. Attended change discussions to understand expected impact and the escalation route. I did not approve production changes or independently administer cloud security controls. PRACTICE PROJECTS Azure access investigation, isolated personal lab Used synthetic identities to compare a permitted and a denied action. Recorded the resource, identity and assigned role, then repeated the checks after changing the lab permission. Kept a short explanation of the result and removed the test resources afterwards. This was a learning exercise, not production cloud ownership. I have not yet implemented infrastructure as code or operated a cloud monitoring service for an employer. SKILLS Ticket investigation, user communication, technical handovers, basic Azure identity concepts and supervised troubleshooting. CERTIFICATIONS Microsoft Certified: Security, Compliance, and Identity Fundamentals EDUCATION BSc Business Information Systems
The sample review
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.
Target: Cloud security engineer at mid level. Review version cv-review-2026-09-b, rules cv-2026-09-b.
Your first three improvements
This review assesses the document, not your ability. Missing evidence may be work you have not described or experience you still need.
Keep the lab scope explicit: cloud platform work in a paid environment
Keep this example labelled as project or lab work. A requirement for paid production work needs a separate employment example; do not relabel the lab as commercial experience.
Connect the listed skills to concrete examples
4 skill phrases need a wording check. Point to an example of your contribution, retaining any lab or supervised scope. Remove a skill only if you cannot support it; a missed text match alone does not establish that.
Not evidenced in this CV: named responsibility for something in production
This CV does not evidence it. That does not establish whether you have done it. Add a claim only if you can describe your own contribution and support it with a real example; otherwise leave the gap visible.
Illustrative recruiter read
The eye lands on IT Support Analyst and the dates. That decides whether the rest is read as a Cloud security engineer application or as something else.
Two or three bullets under the first role get skimmed. 2 of the things this target is judged on show up there.
The skills block gets a glance, then the certifications, then the decision is made.
Twenty seconds in, a recruiter sees something adjacent to Cloud security engineer and cannot tell how close it is. 2 requirements are proven outright, and the rest is claimed, so the CV goes to the maybe pile.
Section by section
The profile states a position. A reader will test it against the employment lines immediately.
- 21 words.
- No stock character claims found.
2 of 9 target requirements are proven inside the employment lines, which is where a reader looks first.
- IT Support Analyst at Example Services: 6 lines.
4 skill phrases were not matched to the employment text. Check the relevant work or project example; the wording check can miss paraphrases.
- 4 skills listed.
- Check the evidence for: Ticket investigation, user communication, technical handovers, basic Azure identity concepts and supervised troubleshooting..
The listed certifications are current as far as TechWaymark's registry records.
- Microsoft Certified: Security, Compliance, and Identity Fundamentals: current.
Education is present and should sit below the work history for this target.
- BSc Business Information Systems
Line by line
Ticket investigation
Check evidence
The wording check did not connect this skill to employment text. Check for a valid paraphrase or a labelled project example before changing or removing it.
user communication
Check evidence
The wording check did not connect this skill to employment text. Check for a valid paraphrase or a labelled project example before changing or removing it.
technical handovers
Check evidence
The wording check did not connect this skill to employment text. Check for a valid paraphrase or a labelled project example before changing or removing it.
basic Azure identity concepts and supervised troubleshooting.
Check evidence
The wording check did not connect this skill to employment text. Check for a valid paraphrase or a labelled project example before changing or removing it.
Requirement matrix
| Requirement | Evidence | What a reader sees |
|---|---|---|
| Cloud platform work in a paid environment (critical) | Partial | This is project or lab evidence. It does not establish paid production responsibility; keep the context explicit.Azure access investigation, isolated personal lab |
| Security controls configured, not just named | Partial | A reader can see something close to this and cannot tell how close.Escalated policy exceptions to the endpoint administrator. |
| Cloud identity and permissions work | Missing | Nothing in the document speaks to this. |
| Infrastructure defined as code | Missing | Nothing in the document speaks to this. |
| Cloud logging or monitoring owned | Missing | Nothing in the document speaks to this. |
| Work carried out under a ticketing or change process | Proven | A reader can point at the line that shows you did this.Resolved user access and application support requests through the team ticket queue. |
| Named responsibility for something in production (critical) | Missing | Nothing in the document speaks to this. |
| Scale and environment stated in numbers | Missing | Nothing in the document speaks to this. |
| An outcome, not just an activity (critical) | Proven | A reader can point at the line that shows you did this.Resolved user access and application support requests through the team ticket queue. |
Recovering the evidence you may already have
For Cloud security engineer, a reader expects to see cloud identity and permissions work carried out in a named job, with the system or the environment stated.
Check work you did outside your job title: cover during absence, a project you were lent to, a migration weekend, an audit response, or a lab you built and actually ran.
- Have you personally done work involving cloud identity and permissions work? If not, leave this as a gap rather than adapting someone else’s example.
- Which identity and operation did you investigate, what permission changed, and how did you test both permitted and denied access?
- What changed after you finished, and how would someone else know?
Use only details you can support. If you have an example, state your contribution, context and observed result. Label a lab clearly; omit any size or outcome you cannot substantiate.
For Cloud security engineer, a reader expects to see infrastructure defined as code carried out in a named job, with the system or the environment stated.
Check work you did outside your job title: cover during absence, a project you were lent to, a migration weekend, an audit response, or a lab you built and actually ran.
- Have you personally done work involving infrastructure defined as code? If not, leave this as a gap rather than adapting someone else’s example.
- Which versioned change did you make, how did you test it, and what would you roll back or rerun after a failure?
- What changed after you finished, and how would someone else know?
Use only details you can support. If you have an example, state your contribution, context and observed result. Label a lab clearly; omit any size or outcome you cannot substantiate.
For Cloud security engineer, a reader expects to see cloud logging or monitoring owned carried out in a named job, with the system or the environment stated.
Check work you did outside your job title: cover during absence, a project you were lent to, a migration weekend, an audit response, or a lab you built and actually ran.
- Have you personally done work involving cloud logging or monitoring owned? If not, leave this as a gap rather than adapting someone else’s example.
- Which signal did you inspect, how did you distinguish a fault from noise, and who acted on the result?
- What changed after you finished, and how would someone else know?
Use only details you can support. If you have an example, state your contribution, context and observed result. Label a lab clearly; omit any size or outcome you cannot substantiate.
For Cloud security engineer, a reader expects to see named responsibility for something in production carried out in a named job, with the system or the environment stated.
Check work you did outside your job title: cover during absence, a project you were lent to, a migration weekend, an audit response, or a lab you built and actually ran.
- Have you personally done work involving named responsibility for something in production? If not, leave this as a gap rather than adapting someone else’s example.
- What was your responsibility, who approved or supervised it, and what record distinguishes your contribution from the team's?
- What changed after you finished, and how would someone else know?
Use only details you can support. If you have an example, state your contribution, context and observed result. Label a lab clearly; omit any size or outcome you cannot substantiate.
For Cloud security engineer, a reader expects to see scale and environment stated in numbers carried out in a named job, with the system or the environment stated.
Check work you did outside your job title: cover during absence, a project you were lent to, a migration weekend, an audit response, or a lab you built and actually ran.
- Have you personally done work involving scale and environment stated in numbers? If not, leave this as a gap rather than adapting someone else’s example.
- What scope can you substantiate from records? Use a range if necessary and do not invent a count or percentage.
- What changed after you finished, and how would someone else know?
Use only details you can support. If you have an example, state your contribution, context and observed result. Label a lab clearly; omit any size or outcome you cannot substantiate.
Suggested rewrites
Built only from words already in your document. No employer, number, date, tool or outcome is added.
No line could be rewritten without adding a fact you did not supply.
What to fix, in order
Keep the lab scope explicit: cloud platform work in a paid environment
Keep this example labelled as project or lab work. A requirement for paid production work needs a separate employment example; do not relabel the lab as commercial experience.
Connect the listed skills to concrete examples
4 skill phrases need a wording check. Point to an example of your contribution, retaining any lab or supervised scope. Remove a skill only if you cannot support it; a missed text match alone does not establish that.
Not evidenced in this CV: named responsibility for something in production
This CV does not evidence it. That does not establish whether you have done it. Add a claim only if you can describe your own contribution and support it with a real example; otherwise leave the gap visible.
Presentation and parsing
- Parsing: Every block in the document could be read as text.
- Headings: 7 standard headings found: header, profile, experience, projects, skills, certifications, education.
- Chronology: Dates run in order with no unexplained gap.
- Duplication: No repeated employment lines.
- Length: 297 words, roughly 1 pages.
- Readability: Bullets are short enough to survive a skim.
TechWaymark publishes no applicant tracking score. Nobody outside a given employer can see how their system ranks a document, so a number here would be invented. These checks cover what can be observed: whether the text parses, whether the headings are standard, whether the dates hold, whether lines repeat, how long it is and how it reads.
Revision worksheet
Keep the lab scope explicit: cloud platform work in a paid environment
Keep this example labelled as project or lab work. A requirement for paid production work needs a separate employment example; do not relabel the lab as commercial experience.
Connect the listed skills to concrete examples
4 skill phrases need a wording check. Point to an example of your contribution, retaining any lab or supervised scope. Remove a skill only if you cannot support it; a missed text match alone does not establish that.
Recover evidence for cloud identity and permissions work
Have you personally done work involving cloud identity and permissions work? If not, leave this as a gap rather than adapting someone else’s example. Which identity and operation did you investigate, what permission changed, and how did you test both permitted and denied access? What changed after you finished, and how would someone else know?
Recover evidence for infrastructure defined as code
Have you personally done work involving infrastructure defined as code? If not, leave this as a gap rather than adapting someone else’s example. Which versioned change did you make, how did you test it, and what would you roll back or rerun after a failure? What changed after you finished, and how would someone else know?
Recover evidence for cloud logging or monitoring owned
Have you personally done work involving cloud logging or monitoring owned? If not, leave this as a gap rather than adapting someone else’s example. Which signal did you inspect, how did you distinguish a fault from noise, and who acted on the result? What changed after you finished, and how would someone else know?
Recover evidence for named responsibility for something in production
Have you personally done work involving named responsibility for something in production? If not, leave this as a gap rather than adapting someone else’s example. What was your responsibility, who approved or supervised it, and what record distinguishes your contribution from the team's? What changed after you finished, and how would someone else know?