Most controller job descriptions I see were written for a job that no longer exists. They ask for a decade of experience, a professional designation, and "strong attention to detail." Then the company hires someone who matches the description and wonders, eight months later, why the close still takes three weeks and the board deck is still wrong.
I have hired controllers, been the CFO they reported to, and, earlier in my career, done the job. Here is what the role actually demands now, and where hiring managers go wrong.
The job has moved from recording to running
Ten years ago a controller's job was to get the numbers right and get them out. That is still the floor. But the systems that do the recording have improved, and the expectations around the controller have risen to match. The controller in a well-run company is now the person who owns the operating rhythm of finance: the close calendar, the control environment, the reporting package, and the team that produces all of it.
That shift changes what you should be screening for. Technical accounting knowledge matters, but it is table stakes. What separates a good controller from an adequate one is judgment about process, people, and priorities.
Five things a controller needs to know in 2026
1. How to design a close, not just execute one
Ask a candidate to describe their close calendar. A strong controller will tell you which tasks happen on which day, where the dependencies are, what usually breaks, and what they changed to fix it. A weak one will describe a list of journal entries. The first person can shorten your close. The second can only survive it.
2. How the systems actually work
Not "proficient in NetSuite." Can they explain how a subsidiary consolidation flows through the ledger? Have they configured a revenue-recognition rule, or only used one someone else built? Have they managed a migration? In 2026, the controller is often the most technical systems person in the finance team, whether or not the org chart says so.
3. Controls that fit the business
A controller from a public company can bring a control mindset that is valuable. They can also bring a control burden that paralyzes a company one-tenth the size. The skill is knowing which controls matter at your stage and which are theater. Ask what controls they would remove, not just add.
4. How to talk to people who are not accountants
The controller presents to the CEO, answers the auditor, explains the numbers to the head of sales, and negotiates with the bank on covenant reporting. If they cannot explain a variance in plain language, they will be a bottleneck no matter how accurate the books are.
5. How to build and keep a team
Accounting talent is scarce and getting scarcer. A controller who cannot develop a senior accountant into an accounting manager will spend their tenure recruiting. Ask who they have promoted. Ask who left, and why.
What hiring managers keep getting wrong
Anchoring on the designation. A professional credential is evidence of technical foundation. It is not evidence of the five skills above. I have seen brilliant controllers without one and mediocre controllers with one. Screen for the work.
Confusing years with scope. Ten years running a single-entity, single-currency close is not the same as three years running twelve entities in two countries. Ask about scope: entities, currencies, revenue size, team size, audit history.
Hiring for where you are, not where you are going. If you are at $20M in revenue and plan to be at $60M with a lender and an audit, hire the controller who has already been through that. The one who has only run the $20M version will need replacing in two years.
Skipping the technical interview. Most controller interviews are conversations about culture and career. Those matter, but somebody in the process must ask hard, specific questions about close, controls, and systems. If nobody on your team can do that credibly, get someone who can.
Writing the job description before defining the problem. Start with what is broken, what is coming, and what a good year looks like. The job description writes itself after that, and it will be shorter and more honest.
What to do instead
Define the scope in numbers. Write a scorecard with five or six outcomes for the first year. Build a technical interview around the actual work: walk me through your close, tell me about a control you removed, describe a migration you ran. Then check references with someone who managed the candidate, not someone they nominated.
Do that, and the designation and the years take care of themselves.