How to Evaluate a Controller Candidate Beyond Their CPA Credentials

A CPA is a useful signal for many controller searches, especially in public companies, regulated industries, and audit-heavy environments. It is not evidence by itself that someone can own a close, fix a broken process without breaking reporting, lead a team through turnover, or tell a CFO that the forecast is wrong before it reaches the board.

If you’re interviewing for a controller role, expect the real evaluation to focus on operating judgment: what you personally owned, how you found and prioritized risk, how you handled messy facts, and whether people across the business trusted finance after you made changes. The credential may get you into the process; your examples determine whether you are viewed as a controller or as a very qualified technical accountant.

Start with the job the company actually needs done

“Controller” is not one job. At a 75-person venture-backed software company, it may mean building the close calendar, cleaning up revenue and payroll processes, managing an outsourced tax provider, and being the CFO’s only reliable accounting operator. At a multi-site manufacturer, it may mean inventory discipline, standard-cost integrity, plant relationships, fixed assets, and margin analysis. At a public company, the center of gravity may be SEC reporting, SOX, audit coordination, technical accounting, and controls documentation.

Before judging a candidate, the hiring manager should write down the three problems this person must solve in the next year. Candidates should get those problems out of the interviewer early. Ask: “What would have to be visibly better after six months for this hire to be a success?” Then listen for specifics: fewer late reconciliations, a faster close, cleaner inventory, a credible audit readiness plan, a rebuilt accounting team, or reporting that department heads can use.

That answer tells you which background matters. A candidate who has led a successful public-company SOX remediation may be excellent but still not be the right first controller for a founder-led business with unreliable billing data. Likewise, someone who built order-to-cash controls at a startup may not be ready to lead a complex consolidation, manage foreign entities, and work directly with an audit committee. Neither is a credentials problem. It is a scope match problem.

Use a scorecard that tests controller work, not résumé labels

The cleanest way to avoid overvaluing a CPA, Big Four name, or recognizable employer is to assess a small set of observable controller capabilities. The scorecard should be agreed before interviews begin, not reconstructed after the CEO decides they “liked” one person.

• Close ownership and reporting reliability: Can they explain how they set deadlines, assign ownership, deal with late inputs, review reconciliations, and distinguish a recurring issue from a one-off miss? Ask for the before-and-after operating rhythm, not just the number of days in the close.
• Control judgment: Can they identify the risk in a process, design a practical response, and decide when a manual control is sufficient versus when a system change is worth the cost? COSO frames internal control more broadly than compliance—as support for operations, reporting, and compliance—which is the right lens for a working controller.
• Systems and data fluency: Have they led an ERP implementation, stabilization, integration, chart-of-accounts redesign, or reporting cleanup? Probe what they decided, what failed, who owned the data, and how they validated cutover results. “I was involved” is not an answer.
• Business partnership: Can they challenge sales, operations, HR, or a plant leader without becoming the department of no? Look for an example where they translated an accounting or control issue into cash, margin, timing, service, or decision risk.
• People leadership: Have they hired, developed, reassigned, or exited people? A controller who personally saves every close may be strong technically but may not be able to scale a function. Ask what work they moved off themselves and how they knew the new owner was ready.
• Escalation and communication: Can they deliver bad news early, with a recommendation? The best controllers do not hide behind a technically correct memo when the CFO needs a decision, a timeline, and a clear statement of exposure.

For public-company roles, controls need special weight. Management is responsible for establishing and assessing internal control over financial reporting, and an integrated audit considers the design and operating effectiveness of relevant controls. That does not mean every candidate needs a public-company background. It does mean a candidate claiming control ownership should be able to describe the risk, the control objective, the evidence, the failure mode, remediation, and how effectiveness was monitored.

Run interviews around decisions, not definitions

Weak controller interviews are full of prompts such as “Tell me about your accounting background” and “How do you manage a close?” Those questions invite polished generalities. Use a recent, specific operating event instead. Ask the candidate to pick a close that went badly, an audit adjustment they disagreed with, a material process breakdown, or an ERP change that created reporting risk.

Then keep drilling. What was the fact pattern? What did you know on day one? Who had to be involved? What was your recommendation? What did you decide not to fix immediately? How did you keep the books moving? What evidence told you the fix worked? What would your direct reports say you handled poorly? You are looking for an accountable first-person narrative. A controller should say “I decided,” “I escalated,” and “I changed the review,” while accurately naming where the CFO, auditor, IT lead, or business owner made the final call.

A practical case can help, but make it resemble the job. Give the candidate a short close package with aged reconciliations, a late revenue input, an unexplained inventory variance, and a team capacity constraint. Ask for a 30-minute plan: what they would verify first, what they would book or defer, what they would escalate, how they would protect the close timetable, and what they would communicate to the CFO. Do not turn this into a GAAP trivia contest. You already have their résumé and CPA status; the case should reveal prioritization under incomplete information.

Treat references as operating diligence

Reference checks are where a controller candidate’s management range becomes clearer. Do not ask only whether the person was competent or whether they would be rehired. Ask a former CFO or audit partner: “What did you stop worrying about after they joined?” “Where did they need more structure?” “How did they respond when a control or deadline failed?” “Were they equally strong with detail, people, and executive communication?”

For candidates, this is a reminder to prepare references with context, not scripts. Tell them which version of the controller role you are pursuing and remind them of the specific work they saw: the acquisition integration, audit turnaround, team rebuild, inventory cleanup, or close redesign. A reference who can describe your operating judgment is far more useful than one who can merely confirm that you are diligent.

The final decision should come down to evidence against the role’s immediate problems. A CPA remains a meaningful qualification in many searches, and some organizations will require one because of their reporting environment, lender expectations, board preferences, or internal policy. But a good hiring process asks the more valuable question: when the numbers, systems, people, and deadlines all get difficult at once, has this person shown they can run the function?