Free download. Use it offline or customize it for your company.
Welcoming questions
Can you tell us about yourself and the HR areas you have worked across?
What to look for: A strong answer demonstrates genuine breadth with concrete examples from several HR areas, since candidates who have only done recruiting or only admin are not yet generalists.
Sample answer: My HR career started in recruiting coordination at a 300-person manufacturer, and over five years I deliberately collected the rest of the function: I took over onboarding, then benefits administration when a colleague left, then employee relations casework under our HR manager's supervision. In my current role at a 120-person software company, I am the only HR person besides my manager, so a normal week includes screening candidates, running two onboardings, answering payroll questions, and preparing the quarterly attrition report. The variety is exactly why I have stayed a generalist.
What drew you to a generalist path rather than specializing?
What to look for: Look for a deliberate choice backed by self-awareness about the tradeoffs, rather than a generalist by accident who plans to specialize at the first opportunity.
Sample answer: I tried specializing, actually. I spent a year doing pure recruiting and found that I missed seeing what happened after the offer letter. What I enjoy is following the whole employee arc: hiring someone, onboarding them, watching their first review cycle, sometimes handling their hard moments too. There is also a practical satisfaction in being the person who can answer whatever walks through the door. The tradeoff is that I will never know compensation design as deeply as a specialist, and I am at peace with that; when a question exceeds my depth, I know exactly when to pull in outside counsel or a consultant.
Role-specific and technical questions
Which HRIS and ATS platforms have you administered, and what did you use them for?
What to look for: Strong candidates describe administering systems, meaning configuration, data integrity, and reporting, not just logging in as an end user.
Sample answer: At my current company I administer our cloud HRIS end to end: I set up the onboarding workflows, maintain the org structure and approval chains, own data integrity for 120 employee records, and build the monthly headcount and leave reports our leadership reviews. On the recruiting side I configured our ATS pipelines, the scoring forms interviewers fill in, and the offer approval flow. I also ran the data migration when we moved off spreadsheets two years ago, which taught me more about record hygiene than any course could. Payroll runs through an external provider, and I prepare and check the monthly change file that feeds it.
Walk us through how you run onboarding for a new hire, start to finish.
What to look for: You want a structured process that starts before day one and includes checkpoints after the first week, since onboarding that ends at the equipment handover predicts early attrition.
Sample answer: Onboarding starts the day the contract is signed, not the first morning. Between signing and start date I send a welcome email with practical details, trigger the equipment and accounts checklist with IT, and assign a buddy from the new hire's team. Day one is deliberately light: workspace ready, accounts working, a welcome lunch, and only the essential paperwork. The first week has a schedule I prepare with the manager, mixing role training with short intros to the teams they will work with. Then the part most companies skip: I check in personally at day 7, day 30, and day 90 with a few standard questions, and those conversations have caught two struggling hires early enough for us to fix the problem instead of losing the person.
How do you stay current on employment law changes that affect your work?
What to look for: Look for named, regular sources and a process for turning legal changes into policy updates, and treat vague answers about googling when needed as a compliance risk.
Sample answer: I treat it as a standing routine rather than a reaction. I subscribe to two employment law newsletters, one from our external counsel's firm and one from the national HR association I belong to, and I block an hour every other week to read them properly. Our payroll provider also flags statutory changes to contributions and leave entitlements. When something relevant lands, like last year's changes to parental leave in our jurisdiction, I write a short impact note: which policies need updating, which employees are affected, what payroll needs to change, and I review it with my manager before we touch anything. For genuinely ambiguous questions, we have a retainer with an employment lawyer, and I would rather spend an hour of counsel's time than guess.
Which HR metrics have you tracked, and how were they used?
What to look for: Strong answers connect each metric to a decision it influenced, since tracking numbers nobody acts on is administration rather than insight.
Sample answer: The dashboard I maintain covers time to fill, offer acceptance rate, attrition split by voluntary and involuntary, absence rates, and onboarding survey scores. The value is in what they trigger. When our time to fill for engineering roles crept from 35 to 60 days, the data pushed us to rework the interview process, cutting one redundant round, and it came back under 40. Attrition analysis showed one team losing people at twice the company rate, which started a management coaching conversation that would never have happened on anecdotes alone. I keep the set small on purpose; five numbers leadership actually reads beat twenty they ignore.
How do you handle benefits questions when the answer is complicated or unpopular?
What to look for: The candidate should show they explain unpopular answers plainly with the reasoning behind them, rather than hiding behind policy language or making exceptions to avoid discomfort.
Sample answer: People can accept an answer they dislike far more easily than an answer they suspect is evasive. When someone asks why their bonus was prorated or why a dependent does not qualify for our health plan, I walk through the actual mechanics: here is the rule, here is how it applies to your specific case, here are the numbers. If the answer is unpopular, I say so directly instead of wrapping it in HR language, and I never invent flexibility I do not have, because one quiet exception becomes ten loud precedents. I also log recurring pain points; when enough people stumbled over our confusing leave carryover rule, I brought the pattern to my manager and we simplified the policy at renewal.
Behavioral and culture fit questions
Tell us about a sensitive employee relations issue you handled. What was your approach?
What to look for: Look for strict confidentiality, a fair documented process, and appropriate escalation, while any leakage of identifying details in the telling is itself a red flag.
Sample answer: Without identifying anyone: an employee came to me about a manager whose feedback style had crossed into public humiliation, and they were afraid raising it would cost them their job. My first step was listening fully and being honest about what I could and could not keep confidential. I documented the account, gathered context carefully without signaling who had complained, and found two colleagues had similar experiences. I briefed my HR manager, and we addressed it with the manager as a documented performance conversation with clear expectations and a follow-up date. The behavior improved, and just as importantly, the employee saw that speaking up was survivable. Cases like this run on trust, and trust runs on process.
Describe a time you had to enforce a policy you personally disagreed with.
What to look for: You want loyalty to a fair process alongside willingness to challenge the policy through proper channels, and a red flag is either quiet sabotage or pure rule-following with no judgment.
Sample answer: Our company had a strict policy against remote work during notice periods, and I had to apply it to a departing employee with a long commute and a fully remote job lined up. I thought the policy was pointlessly rigid, and enforcing it felt petty. But applying rules based on my personal taste would make me the policy, so I enforced it consistently and explained the reasoning as fairly as I could. Then I did the part that matters: I collected three cases where the rule had created friction without benefit, presented them at our quarterly policy review, and the rule was relaxed to manager discretion. Enforce consistently, challenge formally. Doing only one of those makes you either a bureaucrat or a loose cannon.
How do you prioritize when recruiting support, payroll questions, and an employee complaint land on the same day?
What to look for: Strong answers triage by real deadline and human impact, recognizing that a serious complaint outranks routine work while payroll cutoffs are immovable.
Sample answer: First I check what each one actually is, because the labels hide the urgency. A payroll question can be a curiosity about a payslip line or someone who was underpaid rent money, and those are different planets. A complaint gets fifteen minutes of listening immediately even on the busiest day, because the person needs to know it landed with someone, and if there is any hint of harassment or safety, everything else waits. Payroll has hard cutoff dates, so anything touching this month's run gets resolved before the deadline. Recruiting usually has the most give, and a candidate scheduling email can slide a few hours without damage, though I protect anything offer-related. The honest answer is that the triage takes ten minutes and the discipline is in communicating the new timeline to whoever is now waiting.
Problem-solving and case questions
A manager wants to terminate someone without documentation. What do you do?
What to look for: The candidate must hold the line on due process and legal risk while helping the manager address the real performance problem properly, and simply processing the termination is disqualifying.
Sample answer: The answer is no, but the conversation is not just no. First I ask what actually happened, because managers who arrive demanding termination often have a legitimate problem they have been avoiding for months. Then I lay out the risk plainly: a dismissal with no documented history exposes the company legally and tells every employee that process is theater. What I offer instead is a fast, honest path: a documented performance conversation this week, clear expectations with dates, and a structured improvement plan. If the situation involves genuine misconduct, that is a different track with an investigation, and I would start it immediately. If the manager pushes to skip process anyway, I escalate to my HR manager rather than executing it, because my signature on that file means I endorsed it.
You discover a payroll error that has underpaid several employees for months. Walk us through your steps.
What to look for: Look for prompt verification, transparent communication with affected employees, full back payment, and a root-cause fix, with any instinct to quietly correct it going forward treated as a serious red flag.
Sample answer: Verify first, before anything else: I would pull the affected records, reconstruct the correct amounts per person per pay period, and have someone check my math, because the correction announcement has to be right the first time. Same day, I inform my manager and finance with the scope: who, how much, how long. Then the part that defines how this lands, telling the affected employees proactively with an apology, the exact figures, and a firm date for the back payment, ideally an off-cycle run rather than making people wait for month end. Interest or tax implications go to payroll counsel if the amounts warrant it. Finally, root cause: in the case I actually handled, a mis-set overtime multiplier for weekend shifts, we added a reconciliation check to every pay run so the same class of error cannot recur silently. Hiding an error like this is how companies end up in court; owning it fast is how they keep trust.
Two employees file complaints about each other on the same day. How do you proceed?
What to look for: Strong candidates treat both complaints as independent cases with impartial process, resisting the urge to judge who started it or to force a quick mediation before understanding the facts.
Sample answer: The tempting shortcut is treating it as one squabble to referee, and that is the mistake to avoid. Each complaint gets logged and assessed on its own merits, because they may differ wildly in severity; one could be a communication grievance and the other a harassment allegation, and cross-filing does not neutralize either. I would meet each person separately, listen without signaling conclusions, and document both accounts, then identify witnesses or evidence like the email threads usually involved. If either allegation is serious, formal investigation procedure applies, possibly with interim measures like adjusting who reports to whom on a project. If both turn out to be interpersonal friction, then mediation becomes the tool, but only after the facts are established. Throughout, both people hear the same message: the matter is being taken seriously, retaliation is prohibited, and here is the timeline. Symmetry of process is everything, because whichever way it resolves, both sides must believe it was fair.
Generate custom HR Generalist interview questions
Need questions tuned to your industry, seniority level, or interview stage? Describe the role and our AI interview questions generator will draft a set in seconds.
