What HR Advisor Interviews Actually Test

Who's in the room

For most HR advisor roles you're not meeting one person. It's usually the HR Manager or Head of HR you'd report to, often paired with a line manager from a department you'd support — someone who has actually rung HR at 4pm on a Friday needing advice on a disciplinary invite. Some organisations, particularly larger ones with a shared service centre, add a second HR advisor or an ER specialist to the panel specifically to probe case-handling detail the manager wouldn't know to ask about. If the employer has an in-house HRIS team (iTrent, SAP SuccessFactors, Workday, BreatheHR, Cezanne), don't be surprised if someone from that side sits in too, particularly if the role includes system administration or reporting.

What this means practically: the manager on the panel is often listening for whether you'd be someone they can ring without a script, and whether your advice would hold up if challenged. The HR panellist is listening for whether you know the process, not just the outcome.

The practical exercise

A pure conversation-only interview for this role is increasingly rare. What you're likely to meet is one of these:

• A written case study: you're given a scenario — an employee with six absences in a rolling twelve months, or a manager wanting to dismiss someone in their probation without a hearing — and asked to draft the advice you'd give, or the letter you'd send. This tests whether you actually know the ACAS Code of Practice on disciplinary and grievance procedures, not whether you can recite its existence.
• A role play: you play the HR advisor, someone plays a manager who wants to skip a step (often: dismiss for gross misconduct without an investigation, or refuse a flexible working request without giving proper reasons). The test is whether you push back appropriately and can explain why, not whether you're polite.
• An in-tray exercise: several queries land at once — a right-to-work document that looks wrong, a maternity leave query with an odd start date, a grievance letter that's actually about performance — and you have to triage and show your reasoning on prioritisation.

None of these are trick formats. They're simulating an ordinary Tuesday. If you've done the job, they're recognisable. If you haven't, they can feel like an exam because the scenario forces specifics you can't wing.

The questions that are actually testing you

Some questions in an HR advisor interview are conversational warm-up. Others are doing real work, and the difference is usually in how specific the follow-up gets.

"Talk me through a disciplinary case from the moment it landed on your desk." This is checking sequencing and legal literacy at the same time: did you establish whether it was a conduct or capability issue before deciding the process; did you know the employee has the right to be accompanied by a colleague or trade union rep at any formal hearing; did you keep the investigation separate from the person hearing the case; did you follow reasonable timescales. A candidate who has actually run cases will mention these without being asked. A candidate who hasn't will describe the meeting and the outcome and skip the part in between.

"How do you manage a manager who wants a quicker route than the policy allows?" This isn't a personality question about assertiveness. It's checking whether you understand that you're the one who carries the legal risk when advice goes wrong, and whether you know when to say "we can't do that" versus when there's genuine flexibility in the policy.

"Someone's absence has hit their Bradford Factor trigger point — walk me through what happens next." This only makes sense as a question if the interviewer expects you to know what the Bradford Factor is and how a trigger point relates to a formal absence review, not a dismissal. It also opens the door to a harder follow-up: what if the absences are disability-related? That's testing whether you know when the Equality Act 2010 requires you to consider reasonable adjustments before treating absence as a standard case, and whether you'd recognise the difference between a general absence policy and a case that needs a different, careful path.

"What's the difference between how you'd handle a conduct issue and a capability issue?" Straightforward on the surface, but it's checking whether you conflate the two, because the process, the letters, and the potential outcomes genuinely differ. Advisors who blur this distinction tend to blur it in practice too, and panels know that.

"A grievance comes in that's actually a complaint about someone's manager. How do you handle the fact you support that manager day to day?" This is about impartiality, and it's one of the harder ones to answer honestly, because the real answer often involves admitting the tension exists rather than pretending it doesn't.

What a shallow answer sounds like

To someone who does this job, a shallow answer has a particular shape: it's fluent on outcome and vague on mechanism. "I'd invite them to a meeting, explain the situation, and we'd go from there" is the kind of sentence that sounds fine to a generalist and sounds like a gap to an HR manager, because it never names the Code, never mentions the right to be accompanied, never distinguishes suspension from investigation, and never says who else needs to be involved.

Similarly, on absence: "I'd have a supportive conversation with them" without mentioning trigger points, without asking whether there's an underlying health condition, without mentioning Occupational Health referral, reads as someone who has watched HR work rather than done it.

On family leave: if you're asked about calculating a qualifying week for maternity or shared parental leave and the answer is "I'd check the policy," that's not wrong, but it's thin. Advisors who handle this daily usually know the qualifying week rule (15 weeks before the expected week of childbirth) without needing to look it up, because they've done it enough times that it's routine, not research.

The common thread: shallow answers describe what a reasonable person would do. Strong answers describe what the process requires and why, because for this role the process is the job — line managers come to you precisely because they don't know it, and "it felt right" isn't advice they can act on if challenged later.

What to do before you go in

Re-read the ACAS Code of Practice on disciplinary and grievance procedures — it's short, it's free, and interviewers assume you've read it recently even if you know it well. Have two or three real case examples ready, each with a clear before-during-after structure, ideally one disciplinary, one grievance, one absence case, and be ready to name the policy trigger point, not just the human outcome. If the advert names a specific HRIS (Workday, iTrent, SuccessFactors), be honest about your level with it rather than implying familiarity you don't have — a practical test will expose the gap faster than an interview question will.

If you're sending out a lot of applications for HR advisor roles and hearing nothing back, it's worth checking whether your CV is actually naming the specifics — CIPD level, systems used, ER caseload, absence management experience — that this interview format is built to test, because a generic HR CV tends to produce a generic interview invite rate. jobmarket.pro reads the full advert for each role, matches your experience against what it specifically asks for, and prepares the application from your actual profile rather than a template.