What Do HR Management Students Often Lack? — A View from 100+ Recruitment Interviews

A few weeks ago, a final-year student sat across from me and recited Kirkpatrick's four levels of evaluation flawlessly. Definitions, sequence, examples — perfect. So I asked a follow-up: "You've just run a training programme for 200 store staff, and three months later turnover hasn't moved. Where do you look first?"

She went quiet. Not because she wasn't bright — she was one of the sharpest candidates that week. She went quiet because, in four years, no one had ever asked her that question.

That silence is the reason I'm writing this. Not as a critique of students, and certainly not of the faculty who teach them. The students who reach our interview rooms are usually diligent, curious, and genuinely well-read. What I want to share are field notes from the other side of the desk — offered in the spirit of comparing observations, because we're trying to solve the same problem from two directions.

Here is what we most often see missing. None of it is about intelligence or effort.

1. The leap from function to business

Most students describe HR as a set of functions — recruitment, C&B, L&D — each in its own tidy box. What they rarely do is connect any of it to a number the business actually cares about.

Ask "why does onboarding matter?" and you'll hear "to help new hires integrate." True — but the operations director across the table wants to hear: "Because our data shows the first 90 days predict two-year retention, and replacing one store supervisor costs us roughly a month of their salary in lost productivity alone." The gap isn't that students don't care. It's that they were never taught the habit of speaking in the language of the business.

2. The leap from framework to operation

They know the models — ADDIE, 70-20-10, competency frameworks, the maturity ladder. Ask them to draw one and they will, cleanly. But ask, "You have 5,000 people, 87 stores, three countries, and 90 days — where do you begin?" and the model stops helping. They learned it as a diagram to admire, never as a tool to reach for when everything is on fire and every choice has a trade-off.

3. Comfort with numbers

Many students chose HR believing it was the "people, not numbers" field. The field moved. Modern HR runs on attrition curves, cost-per-hire, quality-of-hire, span-of-control, ROI. When we hand a candidate a simple turnover table and ask what it's telling them, we often see genuine discomfort — not inability, discomfort. No one told them that being good with people and being good with data are now the same job.

4. The consultant's posture

HR is an influence job. You rarely hold authority over the line managers whose behaviour you're trying to change. Students imagine "doing HR"; the reality is persuading a busy manager to invest in something that won't pay off for a year — building the case, handling the "no," disagreeing with someone senior without losing the room. These are muscles. Muscles need repetitions, and a lecture can describe a repetition but can't be one.

5. Knowing the floor

This is the quietest and most decisive gap. Many candidates have designed a policy, a survey, an onboarding plan — for a workplace they have never physically stood in. They've never watched a shift change, sat in a call centre at hour six, or seen how a factory line actually flows. Good people-work begins with empathy for the reality of the work, and that empathy is very hard to acquire from a case study.

So what actually closes these gaps?

I hesitate to offer suggestions, because faculty know their classrooms far better than any recruiter does — and many programmes already do these things well. But for whatever they're worth, these are the moves we've seen make the biggest difference:

• Bring one real dataset into one class, and make students defend a decision from it — not analyse it, decide with it.

• Swap one essay for one role-play: pitch a training investment to a skeptical operations manager who keeps saying no.

• One site visit teaches more about operations than three lectures ever will.

• Invite practitioners not to lecture, but to bring a live, messy problem with no clean answer — and let students sit in the discomfort.

• After every framework, ask the same four words: "So what does the business get?"

None of this replaces the theory. The frameworks matter — they're the scaffolding. What we're describing is the translation layer between the classroom and the shop floor, and that layer is genuinely hard to build inside a single semester. It may be the one thing the two sides of the desk can only build together.

I'm not writing this to sell anything. We spend our days on the hiring side of the table, and we'd honestly love to compare notes with the people on the teaching side — including where you see it differently, because you may well be right and we may be wrong.

If any of this resonates, or if it doesn't, I'd genuinely like to hear from you.

Tomuz Advisory

A Firm Core, A Far Reach