← All hiring guides
Security Guard

How to Write a Security Guard Job Description

A security guard job posting needs to screen for vigilance and documentation that actually holds up — not just list duties. Here's what to include and what actually filters for the right candidates.

What this role actually needs to prove out

Before writing requirements, get clear on the one thing a strong security guard candidate has to demonstrate: vigilance and documentation that actually holds up. Every requirement you list should trace back to that, not to a generic template for the job title. A posting that just restates the job title in bullet-point form filters for nothing — it neither attracts strong candidates nor repels weak ones.

Must-have requirements to include

Keep this list short and real — these are the skills that actually predict success in the role, not a wish list:

  • Patrol procedures
  • Incident reporting
  • Access control
  • Emergency response
  • Surveillance monitoring

Nice-to-have — list separately, don't gate on these

Worth calling out as a plus, but requiring them as "must-haves" needlessly shrinks your pool:

  • State security license
  • CPR/First Aid certification
  • Armed guard certification

What a strong candidate's resume bullet looks like

Useful as a benchmark when screening — this is roughly what real, specific evidence of the role's core skill looks like on paper:

  • Conducted hourly patrols across a 12-building corporate campus, identifying and reporting 20+ safety hazards over one year
  • Managed access control for 500+ daily visitors and employees with zero unauthorized-entry incidents
  • Documented and escalated 30+ incident reports annually with 100% same-shift reporting compliance

Mistakes that scare off good candidates

  • Requiring years of experience as a proxy for skill (e.g. gating on "5+ years" when the real bar is demonstrated competence) — filters out strong candidates with less conventional paths.
  • Listing every tool/skill your team has ever touched as a "must-have," rather than the handful that actually predict success.
  • Burying the actual role and responsibilities under generic company boilerplate that could apply to any posting.

Frequently asked questions

What should I put at the top of a security guard job posting?

A short intro (1-2 sentences) on the role and team, then straight into responsibilities and requirements. Candidates skim the first few lines to decide whether to keep reading — don't bury the actual role behind company boilerplate.

How many requirements should a security guard job description list?

Split them into must-have (5 or fewer — every extra must-have measurably shrinks your applicant pool) and nice-to-have. A JD that lists 15 "requirements" with no distinction screens out strong candidates who'd have been a genuinely good fit.

Should I list a salary range?

Where legally required or common in your market, yes — it's increasingly expected, and its absence is one of the top reasons strong candidates skip an otherwise good posting without applying.