Human Resources · Mid-level
HR generalist resumes often describe the whole department instead of the person: onboarding, payroll, policies, employee relations. Every HR team does those things. A hiring manager wants to know how much you handled, for how many people, and what got better because you were there.
The example below states the size of the workforce supported up front, puts a number on each area (time to hire, turnover, case volume, audit results), and names the HRIS and payroll systems exactly, since postings and ATS filters look for them by name.
HR Generalist with 5 years supporting a 450-person manufacturing and office workforce across 2 sites. Owns the full employee lifecycle for 3 departments, from hiring and onboarding to employee relations and exits. Cut average time to hire from 41 to 27 days and led the move to a new HRIS without a payroll error.
"Supported 180 employees across 3 departments" tells a hiring manager your scope immediately. Without it, the same duties could describe a team of 20 or 2,000.
Time to hire, offer acceptance, turnover, case volume, audit findings, training completion. HR outcomes are measurable, and a bullet with a number reads as an achievement instead of a job description.
Write "BambooHR", "Workday" or "UKG" rather than "HRIS", and list certifications such as SHRM-CP or CIPD Level 5 with their full names. Postings filter on these terms literally, so only list the ones you actually hold or use.
A generalist resume shows breadth across the employee lifecycle and how much of it you owned. A specialist resume (recruiting, compensation, HRIS) goes deep on one area. If you are moving towards a specialism, put those bullets first.
Describe volume and outcome, never details: "handled around 35 cases a year, none escalated" shows judgment without revealing anything about the people involved.
Only if you hold it or are actively studying for it; then list it with the expected completion date. Many generalist roles ask for one as a preference rather than a requirement.
Start from this structure in the free editor, then run the ATS check to verify it parses.