Notes from an interview, written from the other side of the table. Anonymised, shared with consent.
A content and marketing company went from ten people to more than two hundred and fifty in under fifteen months. They were hiring for a senior people leadership role, and I sat the conversation.
What follows is less about how the interview went and more about what the company was actually shopping for, versus what they had written down.
What they got right
The speed was deliberate. Nobody in the room pretended the growth had happened to them; there was a window, they went at it, and they were clear-eyed that the window would close. That's rarer than it sounds. Plenty of companies scale that fast by accident and then narrate it backwards as strategy.
They also knew something was wrong before it had broken loudly. Hiring a people leader at two hundred and fifty, rather than at four hundred after a bad quarter of attrition, is the correct instinct and most companies don't have it.
And they were willing to spend the interview on hard questions rather than culture-deck questions. The conversation moved to failure modes within minutes, and they let it.
What they were thinking
They believed they were hiring for HR. The role as described covered headcount planning, attrition, hiring velocity, policy, and the usual vocabulary of a people function at scale.
Underneath, the questions they kept returning to were nothing like that. What happens when teams get split across locations temporarily. How informal leaders shape behaviour in a dense in-office environment. Why culture breaks faster in young teams than experienced ones. How to spot the person quietly damaging a team without turning it into a witch-hunt. Whether someone can tell a founder an uncomfortable thing early enough for it to matter.
None of that is HR. Those are second-order effects, and they only become visible after the scaling has already happened.
What they had not priced
Blitz-hiring hides people risk. It doesn't remove it, it defers it, and it surfaces all at once rather than gradually. A company that adds two hundred and forty people in a year has bought a large amount of unexamined behaviour and has no baseline to compare it against.
The company had accounted for the operational cost of that growth. It had not accounted for the interpretive cost, which is the part nobody can put in a headcount plan: reading weak signals, holding a narrative steady while fifty new people onboard in a quarter, acting as an extension of founder judgment when the founders are stretched thin.
Payroll, compliance and grievance handling were assumed hygiene. Everyone agreed on that. What nobody had named was that the remaining eighty percent of the job has no checklist.
Where the job description and the need diverged
Read literally, the role was a people operations hire. Read from the questions being asked, it was organisational risk management, and risk management runs on judgment rather than process.
That gap matters because it determines who applies. A JD written in HR language attracts people who are excellent at HR, and the company then wonders why the shortlist feels thin. The best candidates for the job they actually had would not have recognised themselves in the posting.
The underlying question they were really testing was about tolerance rather than capability. Can this person operate after scale rather than before it? Can they make an unpopular call without becoming adversarial, and protect culture without freezing speed?
What they were confused about
Not growth. They understood growth better than most companies twice their age.
They were confused about the moment structure has to replace instinct. That's a much harder question, it has no clean answer, and it almost never appears in a job description because writing it down means admitting the founders' instincts have a shelf life.
How it ended
By the end it wasn't framed as fit or no-fit. It was framed as readiness, which was the more honest framing and, I suspect, the more useful one for them.
We closed on a mutual pause. Nothing was missing on either side. Both of us had simply arrived at the weight of what the role actually demanded, and neither wanted to pretend it was smaller.
If I were advising them on one thing, it would be this: rewrite the role before running the next search. The company knows what it needs. The posting doesn't say it, and the posting is what does the filtering.