Security Guard Resume Guide: Guard Card, Post Type, Reports

A practical guide from the team behind PlainResume, the free resume builder.

Security postings are filled fast, often to cover a specific site starting next week. The reader is asking: can this person be licensed on my post, have they stood a post like it, and will their paperwork hold up if something goes wrong? Answer in that order.

The license block: card, status, and armed status

Licensed security work requires a state-issued card in most of the US, armed work requires a separate firearms permit, and the rules — training hours, renewal cycles, even the name of the card — vary by state, so name yours and its status. This is the license-block pattern again: it's a gate, not a credential, so it belongs under your name rather than at the bottom under certifications. Mid-process? Write "guard card in process, expected March 2027" — a stated date reads as a plan; a blank reads as nothing. Never list a lapsed card as active; this is an industry that verifies.

Name the post — "guard" isn't a job description

The first version is on every security resume in the stack; the second tells a manager exactly which post you can hold. Post types are genuinely different jobs — corporate lobby and visitor management, hospital security with de-escalation demands, retail loss prevention, construction-site and equipment protection, gated residential, event and crowd work, mobile patrol across multiple sites. Say which you've worked, alone or on a team, and on which shift. Overnight solo coverage is a specific competence and it should be labelled as one, the same way shift reliability is in operations work.

Reports and systems: the part most candidates skip

Your incident reports are legal documents. Say that you write them and how many — "wrote 40+ incident reports over 18 months, including two that went to police reports" — and name the systems you've used: CCTV and video management platforms, access control, patrol-tour apps and checkpoint scanners, visitor management, alarm response and dispatch protocols. If you've testified, given statements, or handed evidence to responding officers, that belongs on the page. Add training by name where you have it: de-escalation and verbal defusion, use-of-force policy training, active-threat response, fire-panel and evacuation duties, OSHA cards for industrial sites.

Judgment beats vigilance — show the calls you made

What separates officers is decision-making under pressure: when to call, when to observe and report, when to intervene, and how the incident ended. One or two concrete, non-identifying examples — a trespass handled without escalation, a medical call where you started care before EMS arrived, a fire panel activation you cleared — do more than a list of duties. Keep it discreet: no client names or specifics that would embarrass a site, and never invent an incident. The show-the-behavior rule applies with a professional-discretion caveat.

Coming from elsewhere, or heading somewhere

Security draws heavily from military and first-responder backgrounds — translate the same way: post responsibility, people accounted for, procedures followed, without jargon. Coming from customer-facing work? Most guard posts are 90% presence and service, so lobby, de-escalation, and visitor-handling experience translates directly. Heading upward, the bullets that get you to supervisor, site lead, or corporate security are the ones showing you trained others, wrote post orders, covered scheduling, or held keys and alarm codes — trust markers, as always.

Frequently asked questions