Security Guard CV Example
A security guard CV is read by a security manager, a contract security firm, or an in-house facilities lead, and they are screening for one thing above all: can this person be trusted to protect people, property, and information - stay alert through a quiet shift, stay calm in a crisis, and follow procedure to the letter. Security hiring rewards proof of trust, licensing, and judgement, not a list of patrol duties. Whether you hold a valid licence is often checked first: a security licence (an SIA licence in the UK, a guard card or state licence in the US, or your country's equivalent), its number, and its expiry, because an unlicensed guard is a non-starter for most regulated roles. The setting you have actually worked is checked next: the type of site (retail, corporate, event, residential, construction), the hours and risk level, and whether you ran a post alone or in a team. Systems matter too: the CCTV, access-control, and alarm tools you have used, plus your incident reporting, because familiarity means you are productive from your first shift. And the bullets that win quantify in incidents, loss, and sites covered: 'patrolled the premises' loses to 'secured a 12-acre site with 40+ CCTV cameras across 12-hour night shifts, cut theft incidents 30%, and logged every incident with zero disputes'. This example covers the structure that surfaces those signals in the order a security manager looks for them, the summary and skills sections that prove you can do the job, the experience bullets that win interviews, and the common mistakes that drop strong candidates - including how to write a great security CV even with no formal experience. Everything is editable in the Cvida builder - use it as a starting point and tailor it to your licence, your settings, and the role you are targeting.
Why a security guard CV is different from a generic CV
Security hiring runs on signals generic CV advice tends to skip. Start with what makes it different:
- Trust is the product: a security manager is handing you keys, codes, and responsibility for people and property, so every line should signal that you are dependable, honest, and steady - not just that you held the post.
- Licensing is often a hard gate: many roles legally require a valid licence (an SIA licence in the UK, a guard card or state licence in the US), so whether you hold one - plus its number and expiry - is checked before anything else.
- Alertness and judgement are checked: 'worked security' could mean a quiet residential lobby or a high-risk night-time retail site. State the setting, the hours, and the risk level, because that frames everything else.
- Systems and procedure matter: the CCTV, access-control, and alarm systems you have used, plus your record-writing and incident reporting, signal you can run a post correctly from day one.
- Calm under pressure is the job: de-escalation, first aid, and clear communication in an emergency are what separate a good guard from a liability - so show them in action, not as a list of adjectives.
Treat your CV as proof that nothing went wrong on your watch because you were paying attention. A security manager should be able to confirm your licence, your settings, and a reason to trust you alone overnight inside two minutes - and if they cannot, you do not make the shortlist no matter how reliable you actually are.
The CV structure that works for security guard roles
Security reviewers scan in a fixed order and an ATS parses top to bottom, so use a clean, predictable structure rather than a creative one:
- Header: name, target title ('Security Guard', 'Security Officer', or 'Door Supervisor'), phone, a professional email, city, and your licence number if you hold one. Skip the photo and date of birth - they add ATS risk and no value.
- Professional summary: two or three lines stating your years in security, the settings you have guarded, the licence you hold, and one quantified win. It is the first thing read, so make it earn the rest of the page.
- Licences and certifications: put these high - a valid security licence, first aid, or fire-marshal certificate is often a legal requirement, so do not bury it at the bottom.
- Key skills: a compact block of the surveillance, access-control, and people skills the job posting names, so both the ATS and a human can match you in seconds.
- Experience: reverse-chronological, most recent first, each role with three to five quantified bullets - not a copy of the job description.
- Optional extras: a clean driving licence, languages, or physical-fitness notes - only if they support the target role.
- Length and format: one page is ideal for most security CVs, saved as a PDF with a standard font and no tables, text boxes, or columns that an ATS can misread.
The order matters as much as the content: a security manager reading top to bottom should reach your licence, settings, and reliability before anything else. A clean structure is not a missed chance to stand out - for security roles it signals exactly the discipline the job is screening for.
The fundamentals of CV structure and length this example builds onThe professional summary: setting, licence, and a measurable win
Your summary is the one paragraph guaranteed to be read. For a security guard it should prove setting, licence, and impact in the first lines, not announce that you are reliable:
- Open with experience and setting: 'Licensed security officer with 4 years guarding high-volume retail and corporate sites', not 'hard-working and trustworthy team player'.
- Name the licence immediately: the SIA licence, guard card, or state licence you hold belongs in the first lines, because that is the first thing a manager and the ATS are matching against.
- Include one quantified win: incidents you defused, loss you prevented, or sites you covered, so the summary carries proof and not just claims.
- Match the target title and setting: echo the exact role and environment from the posting (event, residential, construction, door supervision) so the reader sees an immediate fit.
- Keep it to two or three lines: a summary that runs longer stops being a summary and pushes your experience below the fold.
A strong security summary reads like a one-sentence reference: this person is licensed, guarded these settings, and prevented this much loss. Lead with adjectives like 'reliable' instead and you sound like every other applicant in the stack.
How to write a CV summary that opens with proof, not adjectivesLicences, certifications, and the ATS: the section that gets you past the filter
For security roles, your licence, certifications, and the systems you know are often the biggest filter - make them explicit rather than burying them in prose:
- Licence first: list your security licence by name, number, and expiry (SIA, guard card, or your country's equivalent) - many postings auto-reject CVs that do not show one.
- Safety certifications: first aid, CPR, fire marshal, or manual handling - often required, so list them clearly with dates.
- Systems: CCTV and surveillance, access control, alarm monitoring, and any patrol or incident-logging software you have used, listed by name.
- Mirror the posting's wording: an ATS scores you on matching the exact licence and system names the job lists, so use the posting's own terms rather than synonyms.
- Keep it scannable: a labelled licences-and-certifications block beats the same facts hidden inside a paragraph, for both the software and the human after it.
An applicant-tracking system cannot infer that 'looked after the cameras' means the access-control suite the role requires - it matches words. Name the licence, the certificate, and the system exactly, and you clear the filter that silently drops most security CVs before a person ever reads them.
How applicant-tracking systems read a CV - and how to get past themThe skills block: vigilance, procedure, and people skills
Security blends hard procedural skills with the soft skills that defuse a situation before it escalates. Show both, but anchor each in something concrete:
- Hard skills: CCTV monitoring, access control, patrol routines, alarm response, and accurate incident and shift reporting.
- Procedure and compliance: following post orders, health-and-safety rules, emergency evacuation, and chain-of-custody or key control.
- Observation and judgement: spotting the unusual, assessing risk fast, and deciding when to watch, when to act, and when to call for backup.
- People skills: calm de-escalation, clear communication with the public and emergency services, and the firm-but-polite presence that prevents trouble.
- Avoid empty adjectives: 'vigilant' and 'trustworthy' are unprovable filler; replace them with skills a reader can picture you doing on a night shift.
Pick the skills the specific posting emphasizes rather than listing everything you can do. A focused block that mirrors the site's language reads as a candidate who fits the role, not one applying to every contract in town.
How to choose and present the skills that actually move a CVExperience bullets: from 'patrolled the site' to measurable impact
This is where most security CVs fall flat - listing duties instead of impact. Every bullet should show scope, action, and a result a reader can measure:
- Quantify the scope: 'patrolled a 12-acre site with 40+ CCTV cameras across a 12-hour night shift' beats 'patrolled the premises', because numbers turn a duty into a measure of responsibility.
- Show the outcome: 'reduced theft incidents 30% in six months' or 'detained 5 shoplifters with zero injuries and full reports' proves you protect the asset, not just stand near it.
- Lead with strong verbs: monitored, patrolled, de-escalated, detained, reported, coordinated - not 'responsible for' or 'duties included', which read as passive.
- Show trust and a clean record: 'sole overnight officer for a 200-unit residential complex', 'zero security breaches across 18 months', or 'first responder to 30+ incidents' signals you can be left in charge.
- Tie work to the result: connect what you did to an outcome - an incident contained, a loss prevented, a safe evacuation - so the reader sees impact, not tasks.
A reviewer should be able to read any single bullet and know both what you were trusted with and how well it went. 'Patrolled the building and checked doors' describes a job title; 'secured a 200-unit site solo overnight with zero breaches in 18 months' describes a person worth interviewing.
How to write CV achievements that quantify in reach, time, or impactEducation, certifications, and entry routes
Security rarely requires a degree, so this section is short - but licensing and the right framing matter a lot, especially if you are starting out:
- Lead with the licence and certifications: a security licence, first aid, or fire-marshal certificate is often legally required, so put it where a manager sees it fast.
- Keep education brief: a high-school diploma or equivalent is enough for most guard roles, so do not over-weight it.
- Use transferable experience: military, police, stewarding, customer service, or any role demanding alertness and procedure demonstrates exactly what security depends on.
- No experience? Lead with the licence, fitness, and attitude: a valid licence, reliability, flexible shifts, and any responsible or people-facing work go further than an empty experience section.
- Show you are screening-ready: a clean record, willingness to work nights and weekends, and any vetting or background-check clearance reassure a manager you can start fast.
First-job applicants should lean on this section, the skills block, and a strong summary to prove capability the experience cannot yet show. Name the licence, the transferable role, the clean record - concrete signals of readiness beat a generic line about being a hard worker.
Common mistakes that sink security guard CVs
Most security CVs are rejected for a handful of avoidable reasons. Check yours against this list before you send it:
- No licence details: leaving off your licence number and expiry - or whether you hold one at all - is the fastest way to be auto-rejected for a regulated role.
- A duties list with no numbers: 'patrolled, monitored cameras, locked up' describes the title, not your impact - quantify the site size, incidents handled, and loss prevented.
- No sense of setting or risk: leaving out the type of site and the hours makes a manager guess whether you can handle their overnight high-risk post - and guessing usually means no callback.
- Unexplained gaps or a vague record: security is a vetted, trust-based field, so address gaps briefly and honestly rather than leaving a reviewer to assume the worst.
- Typos and a sloppy layout: security is about attention to detail, so a careless CV signals a careless guard - proofread it and keep it clean.
Security hiring is, at its core, a test of trust, alertness, and procedure - so a CV that is licensed, quantified, setting-specific, and clean is itself the strongest evidence you can do the job. Fix these five and you clear the bar most applicants fail, even with little experience.
How to write a strong CV even with little or no work experienceFinal notes and the hiring-manager test
Before you submit, run your security CV through the test a security manager applies in the first scan:
- The licence check: can a reader see, in the first few lines, that you hold a valid licence and when it expires? If not, move it up.
- The trust check: does the CV signal you show up, stay honest, and can be left alone in charge - the thing a manager fears most about a new hire?
- The setting check: is it instantly clear which environments you have guarded and at what risk level and hours?
- The impact check: does any bullet show an incident contained or loss prevented, not just a post stood?
- The tidiness check: is it a clean, one-page, error-free PDF - the same attention to detail you would bring to a shift report?
If your CV passes all five in a thirty-second skim, it will clear the filter that rejects most of the pile and get you to an interview. Build it in Cvida, tailor it to each site's setting and systems, and you give a security manager every reason to trust you with the post - which is the whole job.