The most common mis-hire at Financial Controller level is appointing a strong technical accountant when what your function actually needs is a strong operator. The two look almost identical on paper, and the gap only shows once the person is in the seat and the month end is still landing on your desk.
I see this play out often enough that it is worth spelling out. A Financial Controller who can produce flawless accounts but cannot run a team, hold a deadline, or take work off you is not solving your problem. They are just doing a job you could already do yourself.
Why does this mis-hire happen so often?
Because the CV rewards the wrong thing.
Technical depth is easy to evidence. Qualifications, audit background, complex reconciliations, a clean set of statutory accounts. All of it is visible and comfortable to assess.
Operational strength is quieter. It shows up as a team that hits close dates without drama, as errors caught before they reach you, as a person who owns a problem end to end. None of that photographs well on a CV.
So interviews drift towards the technical. You test what is easy to test, and you end up hiring the person who interviews best on accounting standards rather than the person who would actually run your reporting cycle.
What is the real job of a Financial Controller?
The Financial Controller sits in the layer directly below you, and the point of that layer is to protect your week.
A good one owns the close, owns the controls, owns the accuracy of the numbers, and owns the people producing them. They give you a set of figures you trust without re-checking. That trust is the entire value of the role.
When you hire for technical brilliance alone, you often get someone who wants to do the detailed work themselves rather than lead others to do it well. The close stays slow because it depends on one heroic person. Nothing scales. Your week does not get freer.
The job is control and leadership. Technical competence is the entry ticket, not the differentiator.
What does the mis-hire look like three months in?
Here is a realistic pattern, anonymised from a business I know.
A Finance Director in a growing services firm hired a Financial Controller with an excellent practice background and a razor-sharp technical interview. On paper, perfect.
By month three the FD was still reviewing every reconciliation. The two junior accountants were disengaged because the new Controller reworked their output instead of coaching it. Month end had actually got longer, because the Controller trusted no one and funnelled everything through themselves.
The accounts were immaculate. The function was worse. The FD had hired a brilliant preparer and needed a leader, and the difference cost them two quarters and one resignation before they addressed it.
How do you screen for the operator, not just the accountant?
Change what you ask.
Stop asking how they would treat a technical item. Ask how they run a close. Ask them to walk you through their timetable, day by day, and listen for whether they think in dependencies and people or only in journals.
Ask what they changed in their last close process and what it saved. A real operator has a specific answer with a number attached. A technician often has none, because they never owned the process, they just fed it.
Ask about their team. How many, what did each person own, who did they develop, who did they let go and why. The way someone talks about their juniors tells you whether they lead or hoard.
Then give them a live scenario. A messy close, a missed deadline, a junior making repeated errors. You are watching for whether they instinctively fix it themselves or build a way for the team to fix it.
What should change in how you hire this role?
Weight the specification honestly. Decide before you interview how much of this role is technical delivery and how much is running a team and a process. For most Financial Controller seats it is heavily the latter.
Brief whoever supports your search on that split so the shortlist reflects it rather than the tidiest CVs. If you are recruiting for this layer, Harper May works with finance leaders on exactly this distinction, and you can see current finance vacancies for a sense of the market.
Most of all, protect one truth. The measure of a good Financial Controller is not how good the accounts are. It is how little of your week the accounts now take.
Common questions
Should a Financial Controller still be strongly technical?
Yes. Technical competence is non-negotiable as a baseline. The mistake is treating it as the deciding factor when leadership and process ownership are what actually free up your time.
How do I tell an operator from a preparer in interview?
Ask process and people questions, not standards questions. Operators describe timetables, dependencies, and how they developed their team. Preparers describe the work they personally did.
What if I genuinely need deep technical firepower?
Then name that in the brief and hire accordingly, but be honest that you may still need someone else to run the team. One person rarely does both brilliantly at this level.
