A construction controller needs to produce numbers you can rely on, explain what's happening on the jobs, and help you decide what to do about it. If job costs are incomplete or the WIP is wrong, you can make decisions about bids, staffing, and equipment based on profit that won't hold up.
After fifteen years working in construction finance, including CFO roles, I look for four things in a controller: accounting depth, construction knowledge, comfort with technology, and curiosity.
Before you hire, be clear about what the controller will own. That might include the monthly close, job costing, WIP preparation, financial reporting, cash forecasting, and supervision of the accounting team. Evaluate candidates against the work your business actually needs.
A controller should understand how transactions flow into the financial statements and how to check whether those statements are right. They need to know which accounts require reconciliation, whether costs are recorded in the correct period, and where an estimate or accounting judgment needs closer review.
Experience as an accounting manager, assistant controller, or financial statement auditor can be useful. Ask what the candidate personally handled. Reviewing a monthly close, resolving reconciliation problems, and preparing financial statements are different responsibilities from entering transactions.
For someone coming from tax, ask about their experience with accrual accounting, monthly reporting, job costs, and the close process. Tax experience can be valuable, but you still need evidence that they can manage the accounting function you are hiring them to lead.
A useful interview question is: "Walk me through a monthly close you managed. What did you review yourself, and how did you know the reports were complete and accurate?"
Listen for specific work, checks, and problems they resolved. You want to understand what they can take responsibility for.
General accounting knowledge gives a controller a foundation. Construction adds job costing, progress billing, retainage, change orders, WIP, and revenue recognition for long-term contracts. Your controller needs to understand how those pieces affect the financial statements and the decisions you make.
Someone with construction accounting experience should be able to explain earned revenue, billings, and cash collections in plain language. They should also understand how a change in the estimated cost to finish can affect a job's forecast and, where applicable, recognized revenue.
Ask: "A project manager increases a job's estimated cost to complete. What would you review in the WIP and financial statements, and what would you discuss with the project manager?"
That question gives you a better view of their understanding than asking whether they have prepared a WIP before. Listen for how they connect the estimate to the remaining work, projected margin, revenue calculation, and reporting period.
A capable accountant can learn construction. If you're hiring someone without industry experience, have a practical plan for training and review. Make sure the candidate recognizes the gaps and is willing to work through them. The owner shouldn't discover those gaps after relying on several months of financial statements.
Your financial information probably comes from several places: an accounting system, payroll, field time records, project management software, and spreadsheets. A controller needs to understand how that information reaches the books and where errors or delays can enter the process.
Ask them to describe a reporting process they improved. Where did the data come from? What was being entered twice? How did they check that the new report agreed with the accounting records? Who maintained the process after it was put in place?
Useful improvements might include getting labor onto the right jobs sooner, reducing repeated spreadsheet entry, or making the monthly WIP easier to review. Look for someone who can explain the work and its result without hiding behind software terminology.
The controller should work with operations on the parts that affect the field. Accounting can define what is needed for reliable reporting, while project managers explain how the information is created and used on the jobs. A process needs to work for both teams.
I want a controller who investigates a number that doesn't make sense. If a job's margin changes, they should want to know whether the cause is productivity, purchasing, a missed cost, a change order, or a bad estimate.
Ask: "Tell me about a financial result that surprised you. What did you investigate, who did you speak with, and what did you learn?"
You can also ask what they have learned recently and how they applied it. The answer might involve construction accounting, reporting, software, or a better way to manage the close. What matters is whether learning changes how they work.
A controller should be willing to admit when they need help, find a reliable answer, and improve the process when the same problem keeps coming back. That is especially useful when the business is growing and the old routines are becoming harder to maintain.
Look at the candidate's ability to manage the work, explain the results, and follow through on problems. Credentials and job titles give you background, but the interview should help you understand how they would handle your accounting function.
Also separate the controller's responsibilities from any additional financial leadership you need. If you're considering fractional CFO support, define how that role would work with the controller and who would own each responsibility.
If your accounting team needs help with job costing, WIP preparation, financial reporting, or improving its processes, Levvigo can work alongside the team. Outsourced accounting support may help you address specific gaps while your controller manages the broader accounting function.
Book a call with Levvigo to discuss what your accounting team needs and where we can help.