HR Generalist Interview Questions

"I started as an HR coordinator at a mid-sized manufacturer, mostly handling joining paperwork and attendance records. Within a few months I was sitting in on grievance meetings and helping with the appraisal cycle, and I realised I liked seeing how the pieces connect. A payroll error becomes an employee relations issue, and a weak onboarding shows up later as early attrition. That's why I want to stay a generalist for now. I like being the person who knows the whole employee journey and can spot where one part is causing trouble in another. Later I might specialise, probably in employee relations, but I'd rather do that with a full picture of how HR works end to end."

"A generalist covers the whole employee journey rather than one slice of it. That means supporting hiring and onboarding, handling employee relations like grievances and disciplinaries, running the performance cycle with managers, sending accurate attendance and pay changes to payroll, keeping policies and the handbook current, and managing exits, engagement and the HR data that sits under all of it. In my current role I've done most of that hands-on. I run onboarding and the monthly payroll inputs for about 300 people, and I've handled around a dozen grievance and disciplinary cases from start to finish. The area I've done least is writing policy, because our handbook was owned by head office, so I've been reviewing drafts with my HR manager to build that up."

"The part I enjoy most is onboarding, honestly. It's the one moment everyone is hopeful, and small things like a working laptop and a buddy on day one make a big difference to whether someone stays. The hardest part for me is delivering a disciplinary outcome to someone I've come to like. I care about people, so I used to soften the message too much and the employee left unsure what had actually been decided. What I do now is write down the one sentence that must be said clearly before the meeting, say it early, and then give space for their reaction. Being kind and being clear aren't opposites, but it took me a while to learn that."

"I'd be honest: HR is paid by the company, and part of the job is protecting it from risk. But I don't think that puts me against employees, because most of the time the interests line up. A company that treats people fairly, deals with harassment properly and fixes bad managers is also a company that avoids legal trouble and keeps good staff. Where I earn trust is in how I behave. I apply rules the same way to a junior employee and a senior leader, I keep things confidential, I tell people honestly what I can and can't do, and I follow up when I say I will. People don't need HR to take their side. They need HR to be fair."

"At my last company, an employee complained that her team lead regularly gave her the worst shifts and mocked her in team chats. I met her the same week, took notes, and explained what would happen next and who would need to know. I collected the shift rosters and the chat messages, then interviewed the lead and two colleagues separately with the same open questions. The rosters showed a clear pattern and the messages backed her account. The lead got a formal written warning and had to complete training, and rostering moved to a rotation reviewed by the manager. I gave the lead the full outcome, told her the complaint was upheld and action had been taken without sharing his sanction, and I checked in with her after a month and again after three to make sure nothing had turned into quiet retaliation."

"A developer came to me saying his manager micromanaged him and he wanted to move teams. When I spoke to the manager, she said she checked in often because two deadlines had slipped and she had no visibility. So both were right, and the real issue was that they had no agreed way of sharing progress. I met them together with a simple aim: agree how updates would work. They settled on a short written update twice a week, and she agreed not to message him outside that unless something was urgent. I booked a check-in with each of them a month later. He said it felt much better, and the transfer request was dropped."

"First I'd listen properly, thank her for telling me, and take careful notes in her words. Then I'd be honest: I can keep this as confidential as possible and share it only with the people who need to know, but I can't promise to do nothing, because once the company knows about possible harassment it is expected to act, under our own policy and in most places under the law too, and others may be at risk. I'd explain what the process looks like, what her options are, and that retaliation against her is not allowed and would be treated seriously. I'd ask what would make her feel safe right now, such as making sure she no longer has to work alone with him, without moving her against her wishes. Then I'd follow our policy and any legal requirements where we operate, and keep her updated at each step."

"I'd take them somewhere private, let them talk, and not rush to the paperwork. Once they're ready, I'd explain what's available under our policy, which might be paid leave, compassionate or emergency leave, unpaid leave, or flexible hours for a while, plus any employee assistance service we offer. I'd ask what they'd like the manager to know, and then tell the manager only that they'll be away and for roughly how long, not the details. I'd handle the leave entry in the system myself so they don't have to think about it. And I'd agree a simple way to stay in touch, so they know they can come back when they're ready without worrying about their job."

"I try to make sure people see HR for more than bad news. I walk the floor, join team meetings now and then, help with onboarding, and I'm the person who sorts out a leave problem quickly. So when something serious comes up, they already know me. What makes people trust you with problems is being predictable: I'm polite and fair to everyone, including the person I'm investigating, and I don't gossip. I do keep a line, though. I'm friendly with everyone, but I'm careful about close friendships at work and I don't join in on complaints about colleagues. It can feel a bit lonely sometimes, but it means people know I'll treat them fairly when it matters."

"In my last role, new joiners kept telling us in their 30-day check-ins that day one was mostly waiting: no laptop, no system access, and a manager in back-to-back meetings. I built a simple pre-joining checklist that went out automatically when an offer was accepted, with tasks for IT, the manager and facilities, each with a deadline before the start date. I also added a named buddy and a first-week plan the manager had to fill in. I tracked two things: how many joiners had working access on day one, and what they said in their 30-day survey. Both improved within a couple of hiring cycles, and fewer people left in their first three months."

"I'd greet them myself, apologise honestly, and tell them what I'm doing about it, rather than leaving them in reception. Then I'd call IT to get a loaner laptop and basic access that day, and ask a senior person on the team to act as their host until the manager is back. While that's being sorted, I'd use the time well: joining forms, a walkthrough of key policies, a tour, lunch with the team. I'd message the manager so they can send a short welcome note. Afterwards I'd trace what went wrong, whether the IT request was never raised or the manager's leave wasn't flagged, and fix that step, because one bad first day can make someone doubt their decision."

"One month, an employee who'd taken approved leave was marked as unpaid absence because the leave approval came in after our attendance cutoff. She was short in her pay, and she was upset because she had rent due. I apologised, confirmed the approval with her manager the same morning, and worked with payroll to process an off-cycle correction within a couple of days instead of waiting for the next run. I kept her updated each day so she wasn't chasing us. Then I looked at why it happened. Late approvals were common, so we added a reminder to managers before the cutoff and a rule that any unpaid absence got a quick HR check before it went to payroll."

"Each month HR sends payroll the changes that affect pay: new joiners with their start dates and pay details, leavers with their last working day for final settlement, any salary changes or promotions, unpaid leave and absence, overtime or shift allowances, and changes like new bank details. Before the cutoff I reconcile headcount against last month, so every joiner and leaver explains the difference. I check that each change has an approval behind it, and I look at anyone whose pay moves a lot compared with last month. Bank detail changes get extra care, because they're a common fraud route, so I confirm them with the employee directly. Then a second person reviews the file before it goes, and every change is logged."

"Day to day I use the HRIS for employee records, joiners and leavers, job and reporting changes, leave and attendance, storing signed documents, and pulling reports like headcount or leave balances. To keep it accurate, I treat it as the single source of truth, so changes go in when they happen, not in a spreadsheet that gets updated later. I run a monthly check on things like missing managers, people with no department, or leavers still marked active, and I reconcile headcount with payroll. I also ask employees to confirm their personal details once a year. And I'm careful about access: managers see their team's basics, while things like medical notes or salary are limited to the people who really need them."

"A department head wanted to let go of an employee the week after she told us she was pregnant, saying her performance had dropped. There was nothing on file about performance, so the timing alone would have looked like pregnancy discrimination, which is unlawful in most places. I asked for a private meeting and explained that without documented concerns, the company would struggle to defend the decision, and that the real risk was bigger than one role. Then I offered a route: if there were genuine performance issues, we'd set clear expectations, document them and give her proper support like anyone else. He wasn't happy, but he agreed. Once expectations were clear, her performance was fine, and the matter was dropped."

"I'd start by asking a few managers and employees what's working today and where the friction is, and I'd have the draft checked for legal points like working time or data protection where we operate. I'd write it in plain words, with examples, because a policy people can't understand won't be followed. Before launch, I'd brief managers first so they can answer questions and aren't caught off guard. The announcement would explain why, not just what, and link to a short set of common questions. After that, the key is consistency. If one manager ignores it, everyone notices. So I'd track how it's being applied and requests for exceptions, and review it after a few months with real feedback."

"The areas I'd say a generalist must know well are equal treatment and anti-discrimination in hiring and at work, pay rules like minimum wage and overtime, working hours, leave entitlements, health and safety, harassment prevention, how notice and termination work, and how employee data must be handled and stored. The details change a lot between countries and even regions, so my job isn't to be a lawyer. It's to spot when something carries legal risk and check before acting. To stay current, I follow updates from the official labour authorities where we operate, use our legal advisers or an employment law service for anything unclear, and keep a compliance calendar for filings and policy reviews, so changes don't slip through."

"A manager I got on well with asked me over lunch why a colleague from another team had been off for three weeks, saying the team was worried about him. It was a medical absence and I knew the details. I said, I get that you're worried, but anything about someone's health stays between them and HR, the same way yours would if it were you. Then I offered what I could: I told her the absence was being managed, and that if the team wanted to send a message, I'd pass it on. She was fine with it. I think people actually trust HR more when they see you won't share, even with someone you're friendly with."

"I'd tell my manager straight away that I'm friends with the person, and ask for the case to go to someone else. Even if I believe I could be fair, the complainant wouldn't see it that way, and if the outcome was challenged, my friendship would undermine the whole investigation. If there's no one else on the team, the company can bring in another HR person or an outside investigator. Then I'd keep a clear line: I wouldn't discuss the complaint with my friend, even casually, and if they raised it, I'd tell them kindly that I'm not involved and can't talk about it. It's awkward, but it protects everyone, including them."

"I wouldn't deny it, because if I say there's nothing planned and cuts are announced next week, nobody will trust HR again. I also can't share plans that haven't been announced. So I'd say something like: I know there's a lot of talk and I understand why you're worried. I can't comment on rumours, but when there's news that affects you, you'll hear it directly and clearly, not through the grapevine. Then I'd go to leadership the same day, tell them the rumours are spreading and that silence is making it worse, and push for an announcement sooner, with a clear plan for how affected people will be told and supported."

"Over about two quarters, I noticed that most leavers from our customer support team mentioned the same thing: no clear path to move up, so they left for a small title bump elsewhere. On their own, each exit looked like a normal resignation. I grouped the comments, took out anything that could identify someone, and showed the support head the pattern alongside how long the average leaver had stayed. We worked with him to create a senior agent level with clear criteria and a review twice a year. It didn't stop every exit, but in the following year fewer people left in that team, and in the stay interviews people mentioned the new level as a reason they were staying."

"First, it shouldn't be the person's own manager asking, because the manager is often part of the reason. I usually do it in the last week or two of notice, when they have less to lose, and I tell them how the feedback will be used and that it won't be passed on with their name attached. I ask open questions like when did you first start thinking about leaving, and what would have made you stay. Then I mostly listen and ask follow-ups, and I never argue or defend the company, because the moment you do, people go quiet. Afterwards I remove anything identifying and look for patterns across leavers, by team and manager, and share those themes with leadership every quarter."

"The basic calculation is the number of people who left during a period divided by the average headcount over that same period, and you usually annualise it so you can compare across months. But the headline hides most of the story. I'd split voluntary from involuntary, because dismissals and resignations mean very different things. I'd look at regretted leavers, the people we really didn't want to lose, and at early attrition, meaning people leaving in their first few months, which usually points to hiring or onboarding problems. Then I'd break it down by team, manager, role and tenure, because one team with a problem can make the whole company look fine or terrible. Finally, I'd pair the numbers with exit interview themes, so we know why, not just how many."

"I'd start from what people are actually saying, through a short survey, pulse checks or exit themes, rather than planning events. If the feedback says people don't know how to grow, a party won't help; a clear promotion path will. Then I'd pick two or three issues, fix them properly and tell people clearly: you told us this, here's what we did. That loop is what builds trust, and without it people stop answering surveys. I'd also involve managers, because most of engagement happens in the team, through recognition, fair workloads and good one-to-ones. Events still have a place for connection, but they're the extra, not the plan."

"I'd start by agreeing that repeated lateness is a real problem, because the manager needs to feel heard. Then I'd explain that with nothing on file, the employee has never been formally told it's an issue, so a sudden dismissal would be hard to defend and would look unfair to the rest of the team. I'd pull the attendance records to see the actual pattern, and suggest the manager has a documented conversation this week to find out if there's a reason, like caregiving or transport, and to set a clear expectation. If it carries on, we move into the formal disciplinary process with warnings. Most of the time the conversation alone fixes it, and if it doesn't, we have a fair record."

"It starts with finding out the facts before anyone decides anything, so I'd gather records and speak to the people involved. If there's a case to answer, the employee gets the concern in writing, with the evidence, and enough notice to prepare for a meeting. Depending on the law where you are and the company policy, they may be able to bring a colleague or representative. At the meeting they get a genuine chance to explain. Then the decision-maker picks an outcome that fits the issue and their record, whether that's no action, a warning or, for serious misconduct, dismissal, and checks it's consistent with how similar cases were handled. The outcome goes in writing with the reasons, and they're told how to appeal to someone who wasn't involved."

"A performance problem is about capability. The person is trying but isn't meeting the standard, maybe because of skills, training or unclear expectations. The route there is to set clear goals, give support and training, and allow a fair amount of time, with regular reviews. A conduct problem is about behaviour the person controls: breaking a rule, being abusive, lying on a timesheet. That goes through the disciplinary process, and serious cases can mean dismissal even for a first offence. The mistake I see is managers treating a skills gap as misconduct, or letting real misconduct slide because someone is a high performer. Sometimes it's both, and then I'd handle each part through its own route."

"I wouldn't assume the manager is wrong. Some teams really do have a great year. So I'd first look at the team's results against their goals. Then I'd sit with the manager and ask them to walk me through each rating with examples tied to the agreed standards. Often they realise a couple of people met expectations rather than exceeding them, or they admit they were trying to protect the team's raises. I'd explain why it matters: if one team rates everyone at the top, people in other teams doing the same work get treated unfairly, and the ratings stop meaning anything. Then I'd bring all the ratings to a calibration session, so managers test each other's ratings against the same bar."

"I'd make the year-end review the least important part. It starts with goal setting, where each person agrees a few clear goals with their manager that link to the team's priorities. Then managers hold regular one-to-ones, at least quarterly, with a quick note of progress and feedback, so nothing at year end is a surprise. At review time, both sides bring evidence, and managers come together to calibrate so a strong rating means the same thing in every team. Then the outcome feeds into development plans, pay and promotions in a way people can understand. HR's job is to give managers simple templates, train them to have honest conversations, and nudge the ones who fall behind on check-ins."

"A PIP is meant to give someone a real, fair chance to get back to standard. It spells out the specific gaps, what good looks like in measurable terms, the support they'll get such as training or closer coaching, a realistic timeline and regular review points. It's the wrong tool in a few cases. If the issue is misconduct, that belongs in the disciplinary process. If the manager has already decided the person is leaving, a PIP is just a paper trail, and employees can tell, which damages trust across the team. And if the real cause is unclear goals, an unworkable workload or a poor manager, a PIP puts the blame on the wrong person. I'd check those before agreeing to one."