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 document
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
Evidence gap for this target
The document does not yet show essential experience for this target. Recover a real example if you have one; otherwise build the missing experience before claiming it. Wording alone cannot close this gap.
Target: Cloud security engineer at mid level.
Review reference
Review version cv-review-2026-10-workplace-context; rules cv-2026-10-workplace-context-20261016. Keep these details if you ask us about this review.
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.
Not evidenced in this CV: cloud platform work in a paid environment
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.
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.
State plainly what you did on an outcome, not just an activity
The line suggests relevant exposure, but your responsibility and result remain unclear. Confirm what you personally did before strengthening the wording.
Illustrative recruiter read
A reader may start with IT Support Analyst and the dates, then look for how that experience connects to Cloud security engineer.
Across the employment record, 1 target requirements have supporting evidence. Put the most relevant examples where a reader can find them quickly.
A reader may compare the skills and certifications with the work described. Keep those connections explicit; this walkthrough does not predict a hiring decision.
For Cloud security engineer, the requirement matrix records 1 directly evidenced; 2 partially supported; 0 claimed without supporting detail; 6 not found in the supplied document. Read the supporting lines and their context before revising. Lab evidence remains lab evidence; this is a document assessment, not a prediction of shortlisting.
How each part of your CV reads
Each heading on your CV judged as a whole: what a reader takes from it, and the facts behind that judgement.
The profile states a position. A reader will test it against the employment lines immediately.
- 21 words.
- No stock character claims found.
1 of 9 target requirements have supporting evidence in the employment lines, which is where a reader looks first.
- IT Support Analyst at Example Services: 6 lines.
Relevant wording was found in work or project examples for each listed skill. Check your contribution and retain any lab or supervised scope.
- 5 skills listed.
- No unmatched skill phrases.
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
Your sentences that need work
Individual lines quoted from your CV, each with the problem a reader would notice. Lines that read well are left out.
No sentence in your CV stood out as vague, repeated or unsupported.
Requirement matrix
| Requirement | Evidence | What a reader sees |
|---|---|---|
| Cloud platform work in a paid environment (critical) | Missing | The workplace requirement is not evidenced. The quoted project or lab shows related practice, which should stay labelled separately.Azure access investigation, isolated personal lab |
| Security controls configured, not just named | Missing | No matching evidence was identified. Check whether a relevant example uses different wording before treating this as an experience gap. |
| Cloud identity and permissions work | Partial | This is project or lab evidence. It does not establish paid production responsibility; keep the context explicit.Azure access investigation, isolated personal lab: Used synthetic identities to compare a permitted and a denied action. |
| Infrastructure defined as code | Missing | No matching evidence was identified. Check whether a relevant example uses different wording before treating this as an experience gap. |
| Cloud logging or monitoring owned | Missing | No matching evidence was identified. Check whether a relevant example uses different wording before treating this as an experience gap. |
| Work carried out under a ticketing or change process | Evidenced in CV | 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 | No matching evidence was identified. Check whether a relevant example uses different wording before treating this as an experience gap. |
| Scale and environment stated in numbers | Missing | No matching evidence was identified. Check whether a relevant example uses different wording before treating this as an experience gap. |
| An outcome, not just an activity (critical) | Partial | A reader can see something close to this and cannot tell how close.Resolved user access and application support requests through the team ticket queue. |
Recovering the evidence you may already have
For Cloud security engineer, explain the evidence behind this requirement: Cloud platform work in a paid environment. Name your contribution and distinguish paid work, supervised work and practice.
The related practice is already recorded. Look for a supervised workplace example with the required context; if you have none, retain this as an experience gap.
- Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience.
- 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, explain the evidence behind this requirement: Security controls configured, not just named. Name your contribution and distinguish paid work, supervised work and practice.
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.
- Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience.
- Which risk did the control address, what did you configure yourself, and what observation showed that it worked?
- 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, explain the evidence behind this requirement: Infrastructure defined as code. Name your contribution and distinguish paid work, supervised work and practice.
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.
- Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience.
- 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, explain the evidence behind this requirement: Cloud logging or monitoring owned. Name your contribution and distinguish paid work, supervised work and practice.
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.
- Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience.
- 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, explain the evidence behind this requirement: Named responsibility for something in production. Name your contribution and distinguish paid work, supervised work and practice.
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.
- Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience.
- 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, explain the evidence behind this requirement: Scale and environment stated in numbers. Name your contribution and distinguish paid work, supervised work and practice.
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.
- Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience.
- 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.
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 page.
- 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
Not evidenced in this CV: cloud platform work in a paid environment
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.
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.
State plainly what you did on an outcome, not just an activity
The line suggests relevant exposure, but your responsibility and result remain unclear. Confirm what you personally did before strengthening the wording.
Recover evidence for cloud platform work in a paid environment
Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience. 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?
Recover evidence for security controls configured, not just named
Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience. Which risk did the control address, what did you configure yourself, and what observation showed that it worked? What changed after you finished, and how would someone else know?
Recover evidence for infrastructure defined as code
Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience. 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
Do you have your own example that addresses this requirement? If not, leave it as a gap rather than adapting someone else’s experience. 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?