| License required for the title | None. No US state licenses or registers "controller" as an occupation, and you can legally hold the title with no credential at all. What is restricted is the CPA designation itself and assurance work (audits, reviews and compilations issued under your name), which is reserved to licensed CPAs under state accountancy acts. The gate on a controller job is the market, not the law: most mid-size and larger postings ask for a CPA even though none of them has to. |
|---|---|
| CPA, what it actually takes | An accounting-heavy degree plus additional credit hours (historically 150 in total, and a number of states have added alternative pathways that trade credit hours for extra supervised experience), the four-section Uniform CPA Examination under the CPA Evolution structure (three core sections in auditing and attestation, financial accounting and reporting, and taxation and regulation, plus one discipline section chosen from business analysis and reporting, information systems and controls, or tax compliance and planning), roughly one to two years of qualifying experience signed off by a licensed CPA depending on the state, and in most states an ethics exam. Requirements differ state by state and are actively being amended, so confirm yours with your state board of accountancy and NASBA rather than with a forum post or an article. |
| Realistic time to CPA licensure | Four to five years of education, then commonly twelve to eighteen months of exam study and sitting while working full time, with the experience requirement running in parallel. People who start in public accounting usually finish both inside their first few years, because the firm's promotion structure pushes them to. People who start in industry take longer, because nothing at work forces the issue and the exams are the first thing that slips. |
| Alternative credential | CMA (Certified Management Accountant, from the IMA): a bachelor's degree, a two-part exam covering financial planning, performance and analytics plus strategic financial management, and two years of qualifying experience. It carries real weight in manufacturing, distribution, cost-heavy and divisional controller roles, and far less weight in a pre-IPO or audit-facing role, where the CPA is what the board, the audit committee and the sponsor want to see. |
| Typical years of experience | Six to twelve years to a first controller title, usually staff accountant to senior to accounting manager to assistant controller, or three to five years in public accounting audit followed by an industry move at accounting manager or assistant controller level. A controller at a $10M family-owned business can be appointed after five or six years. A group controller at a $500M business is normally fifteen years in. There is no credible path that starts at the title. |
| How the hiring process runs | Four to eight weeks at a private mid-size company, longer where a board or audit committee signs off. Typical stages: a recruiter or search firm screen, a CFO interview on the close and the audit, a technical or case exercise, peer interviews with FP&A and operations, a session with the CEO or the sponsor, then references, a background check and, because the role controls payments, often a credit check. At companies under roughly $25M in revenue with no CFO there may be only two conversations with the owner plus a call to the outside CPA firm. |
| What gets checked here that does not get checked elsewhere | Your audit history, by name. Expect questions about who the external auditor was, whether the opinion was clean, how many and how large the audit adjustments were, whether any significant deficiency or material weakness was ever communicated, and whether a restatement happened on your watch. References are often taken from a former CFO and sometimes from the audit partner. Background and credit checks run under the Fair Credit Reporting Act, which means the employer must disclose and get your written authorization first, and several states limit credit checks except for roles with financial authority, which this one is. |
| Where to get real pay numbers | BLS Occupational Employment and Wage Statistics for SOC 11-3031 (Financial Managers), the classification controllers fall into, filtered by metro area and industry. Then read live postings in pay-transparency jurisdictions (Colorado, California, New York, Washington, Illinois and a growing list of others), because those carry posted ranges attached to real jobs with stated scope. Cross-check the Robert Half Salary Guide and other specialist accounting recruiter guides, which break pay out by company revenue, the dimension government data does not give you. Pay moves on revenue, entity complexity and public versus private far more than on the title. |
What a controller actually owns, and how it differs from the jobs next to it
A controller owns the past. Everything that has already happened to the company has to be recorded, reconciled, closed and reported accurately and on a date, and the controller is the person accountable when it is not. That means the general ledger, the monthly and annual close, the financial statements and any footnotes, the subledgers and the teams that run them (accounts payable, accounts receivable, payroll, often treasury), the internal controls around cash and approvals, the technical accounting positions the company takes, and the relationship with the external auditor and the outside tax firm.
The CFO owns the future and the outside: capital, lenders, investors, the board, strategic deals, and ultimately the numbers too. FP&A owns the forecast, the budget and the explanation of variances going forward. The controller owns the record, and the line between controller and FP&A is the line between what happened and what will happen. In companies under roughly $50M in revenue those lines collapse and the controller does all three jobs, which is why a small-company controller resume reads nothing like a large-company one and why the interviews look nothing alike.
Title inflation runs in both directions, so read the job description, not the title. "Controller" at a thirty-person startup can mean you are the only accountant, you run payroll yourself and you also build the board deck. "Controller" at a $900M group can mean you own technical accounting and consolidations for seven entities and have four managers reporting to you but never touch a bank portal. "Assistant controller" at a large public company is frequently a more technical job than "controller" at a small one. The scope paragraph in the posting tells you which job it is: count the entities, the revenue, the headcount, and look for whether an audit is named.
One scoping note before the rest of this is useful to you. This describes the United States market: US GAAP, state accountancy acts, the CPA and the CMA. The shape of the job travels (close, controls, audit, scope), but the credentials do not. In the UK and much of the Commonwealth the equivalent qualifications are ACA, ACCA or CIMA; in Canada it is CPA Canada; in Australia, CA ANZ or CPA Australia. If you are hiring-side or job-hunting outside the US, read the scope and systems sections as written and substitute your own credential and reporting framework.
- Owned in nearly every controller role: the close calendar and close completion, account reconciliations, journal entry review and approval, the trial balance, financial statement preparation, the audit or review, fixed assets, accruals and prepaids, the chart of accounts, and the integrity of what the subledgers push into the ledger.
- Usually owned: accounts payable and the payment run, accounts receivable and collections, payroll processing and the payroll reconciliation, sales and use tax filings, 1099 filings, insurance and benefits renewal paperwork, and the retirement plan's Form 5500 and its audit once the plan passes the participant-count threshold.
- Often owned in smaller companies: cash forecasting, banking relationships, covenant compliance and lender reporting, budget consolidation, the board package, and whatever operational analysis nobody else has time for.
- Rarely owned: the forecast model itself where there is a real FP&A function, tax return preparation (almost always outsourced to a CPA firm, with the controller owning the data and the provision), and treasury investment policy at larger companies.
- Sub-types that are genuinely different jobs: plant or manufacturing controller (standard costing, variances, inventory, physical counts), construction controller (work in progress schedules, over and under billings, bonding and surety), nonprofit controller (restricted net assets, Form 990, and a federal single audit once award spending passes the Uniform Guidance threshold, which has been raised and should be checked rather than remembered), healthcare, dealership and hospitality controllers, and government controllers working under GASB rather than FASB rules.
- The constant across all of them: someone outside the company relies on the numbers you produce, and when they are wrong it is your name on the explanation.
What gates the job: the CPA, the alternatives, and the years
Nothing in law stops you from being a controller. The title is unregulated: no apprenticeship hours, no state exam, no board. What is regulated is the CPA designation and assurance work. You may not describe yourself as a CPA, and you may not issue an audit, review or compilation report, unless you are licensed under your state's accountancy act. Writing "CPA candidate" on a resume is fine. Writing "CPA" because you passed the exams but never completed the experience requirement is not, and a hiring CFO who is licensed will spot it in the first ten seconds of reading, then check the state board register, which is public and free.
The market gate is a different thing from the legal one. Postings at companies with an external audit, a private equity or venture sponsor, a lender covenant package, or any public reporting ambition will say CPA required or strongly preferred, and the preference hardens as the company gets bigger and as outside parties start relying on the statements. Below that, plenty of effective controllers at owner-operated companies have no CPA and were promoted out of the accounting manager seat on the strength of running a clean close. If you do not have the CPA and do not intend to get it, aim deliberately at owner-operated, family-owned and lower-middle-market companies rather than sending the same resume into pre-IPO roles that will filter you out on the first pass.
The CPA itself is four exam sections under the CPA Evolution structure: three core sections covering auditing and attestation, financial accounting and reporting, and taxation and regulation, plus one discipline section you choose from business analysis and reporting, information systems and controls, or tax compliance and planning. Which discipline you pick does not restrict your licence, and for a controller track business analysis and reporting maps most directly onto the work. Education and experience requirements are set state by state, they are not identical, and several states have added or are debating pathways that substitute additional supervised experience for part of the traditional credit-hour requirement. Check your own state board and NASBA directly, because this is exactly the kind of rule that changed after whatever article you last read about it was written.
The CMA is the serious alternative and it is undersold. Two exams plus a degree and two years of experience, cheaper and faster than the CPA, and in manufacturing, distribution and divisional roles the cost accounting and performance management content maps better onto the actual work than the audit content does. What it will not do is satisfy a board, an audit committee or a sponsor that has decided the controller must be a CPA. Treat it as a strong credential for operating roles and a weak one for technical reporting and audit-facing roles.
Past a point the years matter more than either certificate. A first controller title typically arrives six to twelve years in, by one of two routes. The public accounting route is three to five years in audit at a Big 4, national or strong regional firm, an exit at senior associate or manager level into an accounting manager or assistant controller seat, then the controller title two to four years later. That route teaches you the audit from the other side of the table, which is worth a great deal in these interviews. The industry route is staff accountant to senior to accounting manager inside one or two companies, which teaches you the operational reality of systems, volume and people, but leaves a gap on technical accounting and audit that you have to close deliberately rather than hope nobody notices.
- Legally restricted: calling yourself a CPA without a licence, and issuing any assurance report. Everything else about the controller title is open.
- Strongly preferred by the market: an active CPA licence at audited companies, sponsor-backed companies, and anything with a public reporting path.
- Not a gate: an MBA. It helps on a CFO track and almost never decides a controller hire. A master's in accounting is usually taken to hit a credit-hour requirement, not because employers ask for it.
- Inactive CPA status is common and perfectly acceptable in industry if you label it honestly as inactive. Reinstating a lapsed licence usually means catching up on CPE and paying fees, which is worth doing before a search rather than during one.
- Career changing into accounting: the honest sequence is staff accountant, then senior, then manager. Someone applying straight into controller roles from an adjacent finance job reads as a person who has never owned a close.
- Audit experience is a shortcut to credibility but not to competence. Auditors who move into industry are frequently strong on technical memos and weak on the first close they have to run themselves, and good interviewers probe exactly that seam.
Scope, systems and audit history: the three things a company checks
Every controller search comes down to a comparison between the shape of your last job and the shape of this one. The CFO is asking one question: has this person already carried something of roughly this size and complexity, or will they be learning on my close? Everything in your resume and your answers should make that comparison easy to make in your favour.
Scope is the first screen and it is arithmetic. Revenue, number of legal entities, number of currencies, whether consolidations with intercompany eliminations were involved, headcount reporting to you and at what levels, transaction volume, and which functions sat underneath you. Say the numbers. "Controller of a $120M distributor, four legal entities, two currencies, team of nine including two managers, with AP, AR, payroll and treasury reporting in" tells a CFO more in one line than a page of duties. If you are moving up in size, name the adjacent evidence: the acquisition that doubled your entity count, the year volume grew sharply and the close did not slip.
Systems is the second screen and it is often a hard filter applied by a recruiter matching strings. Name the ERP, name your role in it, name the subledgers around it. There is a large difference between having used NetSuite and having led a conversion to NetSuite, and the difference is worth stating explicitly, because an ERP implementation on your record is one of the most portable assets a controller has. If you have run a system conversion, say so in the first three lines of your resume, not on page two.
Audit history is the third check and the one candidates prepare for least. A company that gets audited is hiring someone who will be sitting across from an auditor within months. Expect direct questions: who was your auditor, how long did fieldwork take, how many audit adjustments were posted and what was the largest, were there passed adjustments, was a management letter issued, was any significant deficiency or material weakness communicated, and if so what you did about it. The right answer to a material weakness question is never that there was never one. It is the specific remediation: what the control was, why it failed, what you redesigned, how you evidenced it, and the year the auditor cleared it.
There is a fourth check that is less visible and decides a surprising number of hires: whether you have carried a particular event. First audit at a company that had never been audited. First consolidated audit after an acquisition. An ERP cutover. A revenue or lease standard implementation. A quality of earnings process during a sale. A covenant breach or a waiver negotiation. A fraud discovered and dealt with. Those events are rare enough that having one on your record puts you in a shorter pile, and specific enough that you cannot fake them under questioning.
- Scope items worth quantifying: annual revenue, legal entities, countries and currencies, consolidation points, direct and total reports, monthly transaction or invoice volume, locations, and whether the company is audited, reviewed or neither.
- Complexity multipliers that raise your market value: multi-entity consolidations, foreign subsidiaries and functional currency translation, inventory and standard costing, multi-element contracts under the revenue standard, revenue recognized over time, multi-state payroll and sales tax, and any acquisition accounting.
- Systems detail that actually matters: the ERP, whether you implemented or inherited it, the close management tool, the AP automation tool, the payroll provider, the billing or revenue system, the expense and card platform, and how data gets out (reporting layer, warehouse, SQL access).
- Audit facts to have at your fingertips: firm name, opinion type, fieldwork timeline, the order of magnitude of materiality, adjustment count and size, management letter comments, any deficiency and its remediation, and the name of the manager you dealt with day to day.
- Events to surface if you have them: first audit, ERP conversion, standard implementation, acquisition integration and opening balance sheet, carve-out financials, covenant breach or waiver, diligence or quality of earnings support, system of record migration, and a close that went from double digits to single digits in days.
- What nobody checks: your GPA after the first job, the university name, and the row of adjectives at the top of the resume.
How controller hiring actually runs, who decides, and how to get in front of them
There is no single process, and company size changes it completely. Below roughly $25M in revenue with no CFO, it is often two conversations with the owner, a reference call to the outside CPA firm that prepares the tax returns, and an offer inside two weeks. The owner is not testing lease classification. They are testing whether you will give them numbers they can trust, tell them bad news early, and not steal from them. Technical depth is barely probed and trust carries everything, which is why a candidate who opens with the codification in that room loses to one who opens with cash.
At a mid-size private or sponsor-backed company the process is four to six stages over four to eight weeks. A specialist recruiter screens first on scope, systems, compensation expectation and notice period, and that screen is far more mechanical than candidates expect: they are matching your numbers against a written brief. Then the CFO, who will spend most of the hour on the close, the audit and the team. Then a technical or case exercise. Then peers: the FP&A lead, the head of revenue operations or supply chain, sometimes the IT lead if a system project is coming. Then the CEO, and at sponsor-backed companies often the private equity operating partner or the deal team member who reads the monthly package.
At a public company the process adds an audit committee or board dimension and slows down. Expect a longer technical screen, internal control and SOX questions throughout, a writing sample or memo exercise in some processes, and a formal background and reference process that can run for weeks. For a public company controller or chief accounting officer role, your filings history and your auditor relationships are the substance of the conversation rather than a section of it.
Sponsor-backed hiring has its own flavour and is worth preparing for separately. A private equity portfolio company controller is hired to produce a reporting package on a fixed calendar, keep lender covenants from surprising anyone, support add-on acquisitions and their opening balance sheets, and stay audit-ready and diligence-ready at all times because an exit is always somewhere on the horizon. The interview will push on reporting discipline, speed, add-on integration and whether you have been through a sale process. Say plainly whether you have.
Now the part most articles leave out: how you actually get into these processes. Controller roles are filled through specialist recruiters far more often than through a careers page, so go at the recruiters directly. Pick four or five who place accounting and finance in your metro, send each one a six-line scope block rather than a resume and a greeting, and ask one question: which of your current clients sit in this revenue and ERP band. A recruiter can place you in thirty seconds if you hand them the matching criteria, and cannot do anything with "experienced finance leader seeking new opportunity". Then work the two routes they do not cover: your former audit firm's alumni network, which is the single highest-yield source of controller introductions for anyone who came out of public accounting, and the CFOs you have already worked for, who move companies and take controllers with them.
Interim and fractional controller work is a real market, not a consolation prize. Firms place interim controllers for parental leave, sudden departures, system implementations and pre-sale clean-ups, usually on a day rate and often starting within a week. It is the fastest way to collect the scope and event experience the permanent market screens on. A sequence of interim engagements that each name a company size, a system and an outcome reads well, provided you present them as engagements with an end date and not as job-hopping.
Timing is worth knowing. Companies that run a calendar year want a controller in the seat before year-end close and the audit, which pushes a lot of searches into late summer and autumn. Candidates coming out of public accounting mostly move after busy season, roughly May through August, so that is when the applicant pool is deepest and competition hardest. If you are coming from industry and can move in the autumn, you are competing against fewer people for roles the company is in a hurry to fill.
- Who screens: a specialist accounting and finance recruiter (Robert Half, Addison Group, Creative Financial Staffing, Brewer Morris and the strong regional firms, which merge and rebrand often) or an internal recruiter, a retained search firm for larger roles, and at the smallest companies nobody, because the owner reads the applications.
- Who decides: the CFO in most cases, the CEO or owner where there is no CFO, with a sponsor operating partner holding effective veto at private equity backed companies and the audit committee having a say for public company roles.
- Typical screen questions: revenue and entity count you last handled, ERP, team size, CPA status, reason for leaving, compensation expectation, notice period, and whether you are willing to be onsite on close days.
- Common exercises: find the errors in a trial balance or a reconciliation pack, write a short technical memo on a scenario, build or critique a thirteen-week cash forecast, present a first ninety days plan, or walk through how you would shorten a twelve-day close.
- Reference reality: controllers get deeper reference checks than most roles. Expect calls to a former CFO, in some processes a former auditor, and at least one direct report. Background checks are standard, and credit checks are common for roles with payment authority, run under the Fair Credit Reporting Act with disclosure and written consent.
- Timeline to prepare for: two weeks at a small owner-run company, four to eight weeks at a mid-size private company, eight to sixteen weeks at a public company or anywhere a board approves the hire.
What the interview really tests, question by question
Controller interviews test four separable things, and strong candidates lose because they prepare only for the first. The four are technical accounting, operating a close, running people and process, and judgment under pressure. The last one decides more offers than the first.
Technical accounting questions are predictable and you should be able to answer them out loud, with the entry and both sides, without hedging. Revenue recognition: the five steps, a contract with multiple performance obligations, the difference between deferred revenue, a contract asset and unbilled receivables, and what you do with a contract modification. Leases: the classification test, the entries at commencement, how the expense pattern differs between an operating and a finance lease, and what happens on a modification or early termination. Stock compensation: grant date fair value, the expense pattern, forfeitures, and the effect of a repricing. Income taxes: current versus deferred, what creates a deferred tax asset, when a valuation allowance is needed, what the rate reconciliation is telling you, and the newer requirement to disaggregate that reconciliation and income taxes paid. Business combinations: the opening balance sheet, intangibles recognized separately from goodwill, measurement period adjustments. Expected credit losses on trade receivables. Capitalized internal-use software, where the FASB has issued targeted improvements moving away from the old project-stage framework toward a threshold based on management authorization and whether completion and use is probable, so read the current text and its effective date rather than reciting the three stages you learned. If the company holds inventory, add standard cost setting, purchase price and usage variances, absorption, and the excess and obsolete reserve.
Close questions are where a good candidate separates from a credentialed one. Be ready to describe your close calendar day by day: what closes on day one, when subledgers are cut off, when accruals go in, when the intercompany reconciliation has to tie, when the balance sheet review happens, when the flux analysis is written, and what date the package goes out. Then the follow-up, which is the real question: what used to break, what you changed, and what the close takes now. Twelve business days to five, with the two specific changes that did it, is the single most convincing thing you can say in the hour.
Process and people questions are about whether the function survives you being on holiday. Expect: how do you review a reconciliation and what makes you reject one; what is your journal entry approval threshold and who approves yours; how do you document a process so a new hire can run it from the document; how have you structured a team of five, and what did you outsource or offshore and why; how would you handle a senior accountant who is reliable but slow and a junior who is fast and sloppy. If you have managed an outsourced or offshore team, say how you built the review layer, because that is the practical problem and the interviewer has probably lived it.
Judgment questions are the ones to rehearse honestly, because the answers are checkable against your face. The CEO wants revenue recognized this quarter that you do not believe is earned. Sales wrote a side letter that changes the contract terms and did not come through you. A payment request arrives for a vendor nobody can identify. You find a related-party transaction that was never disclosed to the auditor. You discover an error in a period that is closed and already reported to the bank. The structure of a good answer is the same each time: state the accounting conclusion, say what you would do first (get the underlying document), say who you would involve and in what order, and say what you would do if you were overruled. A candidate who answers these smoothly and with no visible discomfort is usually less credible than one who says plainly that it was hard and then says what they did anyway.
Finally, expect a cash conversation, and in lower-middle-market companies expect it to be most of the interview. How do you build a thirteen-week cash forecast and what drives the variance in week three. What is a borrowing base certificate and what do people get wrong filling one out. What is a fixed charge coverage ratio and how would you know a month in advance that you were going to breach it. If you have never been near a credit agreement, read one before the interview, because the covenant definitions section is where the whole conversation lives.
- Have cold: the revenue standard's five steps, the lease classification test and commencement entries, deferred versus current tax, the purchase accounting sequence, and the entry that records accrued payroll, the related liability and its clearing against the provider's report.
- Have a close calendar you can describe from memory, with specific day numbers and the specific bottleneck you removed.
- Have one audit story with a number in it: the adjustment that got posted, what caused it, and the control you built so it could not recur.
- Have one controls story: a segregation of duties problem you found and fixed, naming who could do what before and after.
- Have one people story: a hire you made or a performance problem you handled, with what you did and how it ended.
- Have one refusal story: a time you said no to something a senior person wanted. If it ended badly for you, say so. Interviewers trust that version more than the triumphant one.
- Have one cash story: a week you could see a shortfall coming and what you moved, delayed or drew down to cover it.
The resume that gets a controller shortlisted, and what gets skipped
A controller resume gets about twenty seconds from someone deciding whether your last company looks like their company. Build it so that comparison is possible without hunting. Put a short scope block at the top: current title, company revenue, industry, ownership (family-owned, private equity backed, venture backed, public), entity and currency count, team size, ERP, audit status. Four lines of that beat a paragraph of positioning language, and the same four lines are what you read out when a recruiter calls.
Under each role, give the company context before the bullets. A reader cannot calibrate "managed the monthly close" without knowing whether it was a $6M single-entity services business or a $400M eight-entity manufacturer with inventory in three countries. One italic line under the company name fixes it: industry, revenue, ownership, entity count, auditor if audited.
Bullets should be outcomes with units. Close days before and after, with the definition stated. Audit adjustments before and after. Days sales outstanding reduced, with the collections change that caused it. The ERP conversion with the go-live month and whether the first close after it landed on time. The reconciliation backlog cleared, with the number of accounts and the value of what it turned up. Headcount built or restructured. Reserve methodology rebuilt. Sales tax exposure quantified and resolved through a voluntary disclosure agreement. If a bullet has no number and no named artefact in it, it is almost certainly describing the job description rather than you.
What gets skipped: a skills section reading "GAAP, financial reporting, detail-oriented"; a long list of software with no indication of depth; responsibilities lifted from the posting; a summary paragraph that could belong to any of four hundred candidates; and anything about your university beyond the degree line once you have five years of experience. Certifications belong in one short factual line: CPA with state and active or inactive status, CMA, and nothing invented.
Two things to include that candidates routinely leave off. First, the external auditor's name where the company was audited, because it tells a CFO instantly what standard of documentation you are used to working to. Second, the specific technical standards you have implemented or applied in anger, named: the revenue standard, the lease standard, acquisition accounting, credit losses, capitalized software, segment reporting. Those are keyword matches and substantive signals at the same time.
For applicant tracking systems, use both the words and the codes. Write "revenue recognition (ASC 606)" and "lease accounting (ASC 842)" rather than one or the other, name the ERP exactly as the posting names it, and spell out "month-end close", "account reconciliations", "consolidations", "internal controls" and "audit" in plain text rather than burying them in a graphic or a table that parses badly. Keep it a clean single-column document, because multi-column templates still shred in older parsers and you will never be told that is what happened.
- Open with a four-line scope block: title, revenue and industry, ownership structure, entities and currencies, team size, ERP, audit status.
- One context line per employer: industry, revenue, ownership, entity count, auditor. Without it, every bullet underneath is unreadable.
- Quantify the six things controllers are measured on: close duration, audit adjustments and findings, days sales outstanding or collections, reconciliation completeness, headcount and structure, and any system go-live.
- Name the events: first audit, ERP conversion, standard implementation, acquisition and opening balance sheet, diligence or quality of earnings support, covenant reporting, carve-out or restructuring.
- Cut: "detail-oriented", "team player", "proven track record", objective statements, software logo grids, and responsibilities indistinguishable from the posting text.
- Two pages up to roughly fifteen years of experience. Three only if you are a public company controller listing filings and standards work that genuinely needs the space.
The systems stack you are expected to know, and the implementation work nobody plans for
Controllers are filtered on systems more aggressively than any other finance role, because the hiring company has one ERP and the switching cost of a bad hire is high. Know where you sit in the market. Below roughly $20M in revenue you will mostly see QuickBooks Online and Xero. From roughly $20M to $400M it is mostly Sage Intacct and NetSuite, with NetSuite more common in venture-backed and product companies and Intacct common in services, nonprofits and healthcare. Microsoft Dynamics 365 Business Central and Dynamics 365 Finance appear across the middle market, especially in distribution and manufacturing. SAP S/4HANA, Oracle Fusion and Workday Financials appear at the top end. Moving across those bands is possible, but you have to say explicitly that you have done it, because the recruiter's filter will not infer it.
The ERP is only the middle of the stack. Around it sit the tools where a lot of the actual work now happens: close management and reconciliation platforms (FloQast, BlackLine, Numeric), accounts payable automation (BILL, Tipalti, Coupa, Stampli), corporate cards and expense (Ramp, Brex, Expensify, Navan), payroll (ADP, Paychex, Paylocity, Paycom, Rippling, Gusto, or a professional employer organization), billing and revenue (Stripe, Chargebee, Zuora, Maxio, Recurly, and increasingly the ERP's own revenue module), sales tax (Avalara, Vertex), equity (Carta), lease accounting tools, fixed assets, and for public companies the reporting layer (Workiva). Name the ones you have run and say what you did with them.
Know your way out of the system as well as into it. Controllers who can write SQL against a replica, or at least drive a reporting layer like Power BI, Tableau or Looker, settle arguments faster than controllers who wait for a report request to be fulfilled by someone else. Excel is still the real workbench: fluency with lookups, pivots, Power Query for repeatable transformations of ugly exports, and workbooks structured so another person can audit them. A candidate who cannot clean a sixty thousand row export without help will struggle in this job regardless of their technical accounting.
The thing nobody plans for is implementation work, and it is the single most valuable line on a controller resume because it is the thing the person hiring you fears most. ERP conversions go wrong in the same predictable places: an opening balance that does not tie, a chart of accounts designed around the old system rather than the reporting the business needs, historical data converted at the wrong level of detail, subledger integrations that post in summary when you needed detail, cutover timed badly against the close, and a first post-go-live close that takes three weeks. If you have been through one, tell the story with those specifics. If you have not, say so plainly rather than overclaiming, and talk about the smaller migrations you did run: a payroll provider change, an AP tool rollout, a chart of accounts redesign.
One more system reality for 2026 and 2027: access and payment security sit with the controller more than they used to. Who can create a vendor, who can change bank details, who can release a payment, who holds admin rights in the ERP, and whether those are genuinely different people, is a question an auditor asks and an insurer may ask too. Business email compromise and spoofed approval requests are a persistent, well-documented fraud pattern (the FBI's Internet Crime Complaint Center publishes the annual figures, and that is the source to quote rather than a vendor's marketing page). The controls that work are dull and specific: call-back verification on any bank detail change to a number you already held, dual approval above a threshold, positive pay with the bank, vendor master changes separated from payment release, and a written rule that no approval arriving by voice or video alone is sufficient. Be able to describe yours without notes.
- Say which band you have operated in: QuickBooks and Xero below roughly $20M, Sage Intacct and NetSuite through the middle, Dynamics 365 across distribution and manufacturing, SAP, Oracle and Workday at the top.
- Name the surrounding tools with your role in each: close management, AP automation, cards and expense, payroll, billing and revenue, sales tax, equity, fixed assets, leases, reporting.
- Excel skills that are actually tested: lookups and index matching, pivots, Power Query, basic modelling, and reconciling two ugly exports against each other without eyeballing them line by line.
- Worth learning if you do not have it: enough SQL to pull and join your own data, and one reporting tool well enough to build a management pack that refreshes itself.
- Implementation stories that carry weight: an ERP go-live, a payroll provider change, an AP automation rollout, a billing system migration, a chart of accounts redesign, and a consolidation moved off spreadsheets.
- Controls to be able to describe cold: vendor master changes, bank detail change verification, payment approval thresholds, positive pay, journal entry approval and evidence of review, and periodic ERP user access reviews.
Pay, demand, and which controller jobs are worth going after in 2026-27
Do not take a salary number from an article, including this one. The authoritative public source is the BLS Occupational Employment and Wage Statistics series for SOC 11-3031, Financial Managers, the classification controllers fall into. It publishes median and percentile wages by state, metro area and industry. It is broad, because it also contains treasurers and finance directors, so read it as a shape and a floor rather than a quote. Then read live postings in pay-transparency jurisdictions, where employers must publish a range: Colorado, California, New York, Washington, Illinois and a growing list of others. Those ranges are attached to real jobs with stated scope, which makes them better evidence than any survey. Cross-check the Robert Half Salary Guide and the published guides from specialist accounting recruiters, which break pay out by company revenue, the dimension government data does not give you.
What actually moves controller pay, roughly in order: company revenue and complexity, public versus private, metro area, industry, CPA status, and whether the role carries a team. A private equity backed company will often pay above market base plus a meaningful bonus and sometimes a management incentive unit tied to exit. A venture-backed company pays partly in options that may be worth nothing, and the right questions are the strike price, the current preferred price, the total raised and the liquidation preference stack, because a controller of all people should understand what sits in front of their shares. On bonus, do not trust a range from an article: the target percentage is a number the employer knows, it appears in many pay-transparency postings, and you should ask for it in writing with the formula and the last three years of actual payout against target.
On demand: the supply of qualified accountants in the United States has been tightening for years, and the honest sources for the shape of that are the AICPA Trends report on accounting graduates and new CPA candidates, and the BLS employment projections for the occupation. What a candidate can see directly is more useful than either: how long the role you are interviewing for has been open, how many times it has been reposted, and whether the company has started negotiating on things it used to refuse, such as full-time onsite attendance outside close week. Where those signs are present you have real leverage, and it is worth spending on scope and close calendar as well as on pay.
Which jobs are worth going after depends on what you are missing. If you lack audit exposure, take the audited company even if the title is assistant controller, because the audit is the experience that unlocks the next three jobs. If you lack systems, take the company that is about to implement one and get your name on the project. If you lack scale, a divisional or plant controller role inside a large group buys you consolidated-group experience that a standalone small-company controller role never will. If you lack technical depth, a pre-IPO or recently public company will give you more of it in two years than a decade elsewhere.
The jobs to be careful with are the ones where the title is doing a lot of work. A controller role at a company with no CFO, no FP&A, a failing ERP, a first audit coming and a sponsor who expects a package on business day five is four jobs, and plenty of capable people have taken it, burned out and left inside a year. Ask in the interview: why is this role open, what did the last person find hardest, when was the last close completed and on what business day, and what does the most recent management letter say. If the answers are vague on all four, you are being hired to absorb a mess somebody already knows about. That can be a great job if you go in with your eyes open, a written mandate and the budget to fix it, and a bad one if you go in believing the posting.
- Pay sources in order of usefulness: live postings in pay-transparency states, BLS OES for SOC 11-3031 filtered by metro and industry, Robert Half and specialist recruiter guides broken out by company revenue, and published schedules where the employer is a government body or a nonprofit filing a Form 990.
- Pay drivers: revenue and entity complexity, public versus private, metro, industry (manufacturing and healthcare pay differently from nonprofit), CPA status, team size, and sponsor ownership.
- Variable pay: ask for the bonus target as a percentage, the formula, who sets the targets and the actual payout against target for the last three years. A target nobody has hit is not compensation.
- Negotiate on more than base: close calendar expectations, onsite days during close versus the rest of the month, headcount, budget for a close tool or an outsourced provider, and whether the sales tax and provision work is coming to you or staying with an external firm.
- Four questions that reveal the real job: why is the role open, what was the last completed close and on what business day, what is in the latest auditor communication or management letter, and who approves payments today.
- Red flags: no close calendar exists, the last two controllers each left inside a year, the auditor has been changed twice, bank reconciliations are months behind, or the owner describes the books as "basically fine, just needs tidying".
What AI has actually changed for controllers, and what it has not
Start with the honest version, because the hype is doing damage in both directions. The core of the controller job has not been automated and is not close to it. That core is judgment on estimates, accountability for a number somebody outside the company relies on, control over who can move money, and the relationships with an auditor, a lender and a CEO. None of that is a text generation problem. A model cannot be held responsible for a misstatement, cannot sign a representation letter, and cannot decide whether a reserve is adequate when the answer turns on facts nobody has written down yet. If anyone tells you the controller role is being automated away, they are describing the accounts payable clerk's job and using your title.
It is also worth saying which force has actually reshaped accounting departments over the last few years, because candidates get this backwards in interviews. Offshoring and outsourced accounting providers have moved more transactional headcount than AI has. AI has accelerated that shift and made the remaining review work heavier, but the structural change was already running. A controller who talks about automation and never mentions the outsourced provider or the offshore team is describing half the picture, and the CFO sitting opposite is managing both.
What has genuinely changed is the layer underneath you. Transaction coding, invoice capture, three-way matching, bank feed categorization, reconciliation preparation and matching, data extraction from contracts and leases, first-draft flux explanations and first-draft technical memos are now either automated or substantially assisted. Close management platforms have added AI-assisted matching and anomaly flagging on journal entries, AP platforms code and route an invoice without a person touching it, and the ERPs have shipped assistants that will answer a plain-language question against the ledger. The practical result is that the team under a controller is getting smaller and more senior, and the controller's job shifts from supervising keystrokes to designing and evidencing review.
That shift creates the single most important new skill in this role: controlling output you did not produce. If an automated process codes an invoice, or an assistant drafts an accrual calculation, that is a control point, and an auditor will ask who reviewed it, what they reviewed it against, and what evidence exists that the review happened. "The system does it" is not an answer. Controllers who can describe a review control over an automated process, including the exception report, the threshold, the reviewer and what happens when the tool is wrong, are being hired ahead of controllers who can only name the tool.
The audit side has changed too, and you should know it before you sit across from an auditor. The large firms and many mid-tier firms now run analytics over complete populations rather than relying only on samples, and the audit standards have been updated to deal with automated tools and techniques as a source of evidence. The effect on you is simple: anomalies that used to pass unnoticed now generate questions. Round-dollar manual entries at period end, entries posted by a user who should not be posting, credits to revenue from a non-revenue source, duplicate vendor records, payments sitting just under an approval threshold. Clean, consistently described, properly supported journal entries are worth more than they were five years ago, and a messy entry listing costs you days of the close answering questions about entries that were fine.
Two risks now sit with the controller that did not exist a few years ago. The first is data governance: what financial information may be put into an external model, under what agreement, whether the vendor trains on your data, and whether any of it breaches a confidentiality clause or, in a public or pre-IPO company, touches material non-public information. Expect to be asked what your policy is. The second is impersonation fraud in exactly the approval workflows you own, including voice and video cloning of an executive asking for a payment or a bank detail change. The defence is unglamorous and specific, and it is the one place where AI has made a controller's job measurably harder rather than easier.
What none of this means is that you need to write code. A controller does not need to build models, fine-tune anything or learn Python to stay employable. What a controller needs is one automation they have put into production and can talk about honestly: what it cost, what it saved in hours or close days, what it got wrong, and what review control sits on top of it. That single concrete story outperforms any list of tools, and its absence is increasingly noticed.
Designing a review control over automated output
Automation has moved accounting work from being performed by people to being reviewed by people, and the standard for a review control is specific: who did it, against what, when, and with what evidence. A controller who automates coding or reconciliation matching without building the review layer has not saved work, they have moved an error from a place where someone would have seen it to a place where nobody will. This is now a common gap auditors raise at companies that adopted tooling quickly.
Show it: Describe one automated process end to end: what the tool does, what the exception report shows, what threshold triggers a human look, who performs that look, what artefact proves it happened, and the one time it caught something real. Name the tool once, then spend the rest of the answer on the control.
Reconciling to source documents rather than to a system's own output
Every automation layer increases the temptation to agree the ledger to a feed rather than to the document a third party issued. A feed can duplicate, drop days or re-import under a new account after a bank migration, and a matching engine can confidently pair the wrong two items. A reconciliation is only a control when it ties to the bank statement, the lender's amortization schedule, the payroll provider's quarterly filing or the merchant settlement report.
Show it: Say what you tie each major account to, name the document, and say where it is filed. Mention loans, credit cards and payroll specifically, because those are the accounts people skip. Give one example of a difference the automated match missed and how you caught it.
Using AI for first drafts of technical memos while owning the conclusion
Drafting a revenue, lease or business combination memo is a real time sink, and models are genuinely good at structure and at surfacing the considerations you should address. They are also capable of citing guidance that does not say what they claim, or quietly applying a superseded standard. A controller who files an unchecked memo into an audit file has created a problem that will be found, because the auditor reads the memo against the codification.
Show it: Say you use drafting assistance, then say exactly how you verify: that you open the codification yourself, that every conclusion is tied to specific contract language, and that the memo names the facts it relies on. Offer a memo you wrote as a writing sample. Interviewers rarely ask and are visibly impressed when one appears.
Journal entry hygiene under full-population audit analytics
Auditors increasingly test complete populations rather than samples, so entries that are poorly described, posted by unexpected users, round-dollar, posted after period end or lacking attached support generate questions whether or not they are wrong. Answering those questions comes straight out of your close, and a pattern of them undermines the auditor's view of your control environment before anyone has found an error.
Show it: Describe your entry standard: naming convention, required support attachment, who may post and who must approve, the rule for manual entries at period end, and your own monthly review of the entry listing. Say what your top-side entry count is and whether it went down.
Setting a policy for what financial data leaves the building
Controllers are custodians of information that is confidential by contract and, in public or pre-IPO companies, sensitive before release. Putting a draft close, a customer contract or unreleased results into an unapproved external tool can breach a confidentiality obligation and, in the wrong company, create a securities problem. Employers have started asking the question directly in interviews and most candidates have no answer ready.
Show it: State your position in one sentence: which tools are approved, whether the vendor agreement permits training on your data, which categories of information never leave approved systems, and how you handle vendor review with IT and legal. If your last company had no policy, say that you wrote one, or that writing one is in your first ninety days.
Hardening payment controls against impersonation and cloned approvals
The approval workflows controllers own are the exact target of business email compromise and, increasingly, of voice-cloned and video-cloned approval requests. The money leaves in minutes and recovery is rare. This is not a theoretical risk, it is the single clearest example of AI making this job harder, and the controls that stop it are process controls you can describe.
Show it: Describe the specific controls: call-back verification to a number held before the request arrived, dual approval above a threshold, vendor master changes separated from payment release, positive pay with the bank, and an explicit written rule that voice or video alone never authorizes a payment or a bank detail change. Add how you train the AP team to escalate an urgent request from an executive.
Redesigning the team around what is now automated or outsourced
The headcount shape of an accounting department has changed: fewer transaction processors, more senior reviewers, more work sent to outsourced or offshore providers with the review layer kept in house. A controller who can plan that transition honestly, including what to keep internal and why, is solving the problem the CFO is actually worried about, which is cost and capability at the same time.
Show it: Give a before and after structure with numbers: roles, levels, what was automated, what was outsourced, what you deliberately kept in house and why, what it cost, and what happened to the close and to the error rate. If a role was eliminated, say how it was handled. Interviewers notice whether you talk about people as people.
What a screen is looking for
These are the terms that a resume screen, human or automated, is matching against for this role. Use the ones that are true of you, in the words the posting uses.
- Controller
- Financial Controller
- Corporate Controller
- Assistant Controller
- Divisional Controller
- Plant Controller
- Group Controller
- Director of Accounting
- Head of Accounting
- Chief Accounting Officer
- Accounting Manager
- Interim Controller
- Fractional Controller
- Controllership
- Month-end close
- Close calendar
- Close checklist
- Account reconciliations
- Balance sheet reconciliation
- Journal entries
- Journal entry approval
- General ledger
- Trial balance
- Chart of accounts
- Accruals and prepaids
- Fixed assets
- Consolidations
- Intercompany eliminations
- Multi-entity accounting
- Multi-currency
- Foreign currency translation
- US GAAP
- IFRS
- ASC 606
- Revenue recognition
- ASC 842
- Lease accounting
- ASC 718
- Stock-based compensation
- ASC 805
- Purchase accounting
- Opening balance sheet
- ASC 740
- Income tax provision
- ASC 350-40
- Capitalized software
- ASC 326
- Current expected credit losses
- Segment reporting
- Technical accounting memo
- Financial statement preparation
- Footnote disclosures
- Audit readiness
- External audit
- PBC list
- Audit adjustments
- Management letter
- Material weakness
- Significant deficiency
- Internal controls
- SOX 404
- SOX 302
- ICFR
- Segregation of duties
- Risk and control matrix
- Process walkthroughs
- Review engagement
- Compilation
- Single audit
- Uniform Guidance
- Form 990
- Form 5500
- Fund accounting
- GASB
- WIP schedule
- Percentage of completion
- Over and under billings
- Standard costing
- Cost accounting
- Purchase price variance
- Inventory reserve
- Cycle counts
- Physical inventory
- Accounts payable
- Accounts receivable
- Days sales outstanding
- Collections
- Payroll
- Multi-state payroll
- Sales and use tax
- Economic nexus
- Voluntary disclosure agreement
- Property tax
- Unclaimed property
- 1099 filings
- Treasury
- Cash management
- 13-week cash forecast
- Covenant compliance
- Borrowing base certificate
- Compliance certificate
- Debt schedule
- Budget versus actual
- Variance analysis
- Flux analysis
- Management reporting package
- Board reporting
- Lender reporting
- Private equity backed
- Quality of earnings
- Net working capital
- Due diligence
- Data room
- Carve-out financials
- NetSuite
- Sage Intacct
- Microsoft Dynamics 365 Business Central
- SAP S/4HANA
- Oracle Fusion
- Workday Financials
- QuickBooks Online
- Xero
- FloQast
- BlackLine
- Numeric
- Bill.com
- BILL
- Tipalti
- Coupa
- Stampli
- Ramp
- Brex
- Expensify
- Navan
- Avalara
- Vertex
- ADP
- Paylocity
- Paycom
- Rippling
- Stripe
- Chargebee
- Zuora
- Workiva
- Carta
- Power BI
- Tableau
- Excel
- Power Query
- SQL
- ERP implementation
- System conversion
- Process improvement
- Team leadership
- CPA
- CMA
- Big 4
- Public accounting
Mistakes that cost people this job
Describing the job in duties instead of scope, so the reader cannot tell what size company you have actually carried.
Lead with arithmetic. Revenue, entities, currencies, team size, ERP, audit status, in the first four lines. A CFO is comparing your last job to theirs, and "managed all aspects of accounting" makes that comparison impossible, so they move to the next resume where it is possible.
Claiming a clean audit history by saying there were never any findings.
Name the finding and the remediation. Every audited company has adjustments and most have had a deficiency at some point. A candidate who says there were none either worked somewhere without a real audit, did not understand the communications, or is not telling the truth, and experienced interviewers hear all three at once. The remediation story is the thing that gets you hired.
Listing every software package you have ever opened as though all exposure is equal.
Say what you did in each one. "Led the conversion from QuickBooks to NetSuite for three entities, go-live in January, first close after go-live completed on business day seven" is worth more than twelve logos. Inherited, administered and implemented are three different claims and the interviewer will separate them in the first minute.
Applying to controller roles straight from an FP&A, treasury or business finance job with no close ownership.
Be honest about the gap and target around it. If you have never owned a close, an assistant controller or accounting manager role is the real next step, and taking it costs you eighteen months rather than the two years you lose failing in a controller seat. If you genuinely have closed books, say so in those words, because FP&A titles hide it.
Preparing only technical accounting and getting caught by the judgment questions.
Rehearse the uncomfortable ones with specifics: the quarter-end revenue push, the undisclosed side letter, the unidentifiable vendor payment, the error found in a period already reported to the bank. Structure every answer the same way: the accounting conclusion, the document you would get first, who you would involve and in what order, and what you would do if overruled.
Saying you want the controller job because it is a step toward CFO.
Say what you want to build in this function. The CFO ambition is fine and common, but leading with it tells the person hiring that you see their close as a waypoint. Talk about the close you want to shorten, the controls you want to put in and the team you want to develop, and let the trajectory be obvious.
Writing CPA on a resume when the exams are passed but the experience requirement is not complete.
Write "CPA exam passed, licence pending experience requirement" or "CPA (inactive)" exactly as it is. Nearly everyone interviewing you is licensed and understands the difference, and the state board register is public and free to search. Getting this wrong converts a minor gap into a credibility problem.
Taking the job without asking why the role is open and when the books were last closed.
Ask directly: why is this open, when did the last close actually complete and on what business day, what does the latest auditor communication say, and who approves payments today. Vague answers to all four mean you are being hired into a known mess. That can still be the right job, but only if the mandate and the budget come with it in writing.
Treating the recruiter screen as a formality.
Treat it as the hardest filter. Specialist recruiters are matching a written brief on revenue size, entity count, ERP, team size, CPA status and compensation, and most rejections happen here on information you could have supplied in one sentence. Open the call by reading them your scope block so they can place you immediately.
Waiting for controller roles to appear on job boards.
Go at the specialist recruiters directly with a scope block rather than a resume, and ask which of their clients sit in your revenue and ERP band. Then work your former audit firm's alumni network and the CFOs you have already worked for. Most controller seats are filled through those three channels before a posting does much work.
Talking about automation in tool names rather than in controls and results.
Bring one concrete automation with numbers attached: what it cost, what it saved, what it got wrong, and the review control that sits over it. "We implemented a close tool" is a procurement decision. "Reconciliations moved into FloQast, close went from eleven days to six, and here is the exception review that runs on top of the auto-matching" is a controller.
Having no answer when asked what financial information may be put into an external AI tool.
Have a one-sentence policy ready: which tools are approved, whether the vendor agreement permits training on your data, which categories of information never leave approved systems, and how pre-release results are handled. If your last employer had no policy, say that you wrote one or would write one on arrival.
Underselling small-company breadth when moving upmarket, or overselling it when moving to a large group.
Say what your version of the job actually was. At a $15M company, personally running payroll, sales tax, the bank relationship and the board pack is breadth, and it is genuinely valuable at another small company. At a $600M group it is not the same job and pretending otherwise fails fast. Match the story to the target and name the parts you have not done.
Giving a close duration without saying what it is measured to.
Define it before you say it. Business days to a complete, reviewed close with the balance sheet reconciled, days to a flash number, and days to the board package are three different claims, and candidates routinely quote the fastest one. State the definition first and the number becomes credible instead of suspicious.
Ignoring the sub-type specifics for the industry you are applying into.
Prepare that industry's signature mechanic. For construction it is the work in progress schedule and over and under billings. For manufacturing it is standard cost setting and variance analysis. For nonprofit it is restricted net assets, the Form 990 and whether a single audit applies. For software it is the revenue standard and deferred revenue. Being fluent in the one thing that industry's controllers argue about beats general polish.
Questions people ask
Do you need a CPA to be a controller?
Not legally. No US state licenses or registers the controller title, so you can hold it with no credential at all. What state accountancy acts restrict is the CPA designation itself and assurance work such as audits, reviews and compilations. In practice the market is the gate: postings at companies with an external audit, a private equity or venture sponsor, or a public reporting path say CPA required or strongly preferred, while many controllers at family-owned and lower-middle-market companies have no CPA and were promoted out of an accounting manager seat on the strength of running a clean close. If you do not have one and do not want one, target that end of the market deliberately rather than sending the same resume everywhere.
How long does it take to become a controller?
Typically six to twelve years of accounting experience. The two common routes are three to five years in public accounting audit followed by an industry move into an accounting manager or assistant controller role and then the controller title two to four years later, or an in-house progression from staff accountant to senior accountant to accounting manager to assistant controller. A first controller title at a small single-entity company can come after five or six years. A group controller role at a $500M company is normally fifteen years in. There is no credible path that starts at controller, and applying straight into the title from an adjacent finance job signals that you have never owned a close.
What is the difference between a controller and a CFO?
The controller owns what has already happened: the general ledger, the close, the financial statements, internal controls, the external audit and the accounting team. The CFO owns what happens next and everything facing outward: capital structure, lenders, investors, the board, strategic transactions and the forecast, and is ultimately accountable for the numbers as well. In companies under roughly $50M in revenue the two jobs overlap heavily and the controller frequently does the forecasting and lender reporting too. Moving from controller to CFO usually means adding capital markets or lender experience, FP&A depth and board exposure, which is why controllers who want that path volunteer for the covenant package and the board deck.
What do companies check before hiring a controller?
A controller is checked on three things, in this order. Scope: the revenue, legal entity count, currencies, consolidation complexity and team size you have actually carried. Systems: the ERP by name and whether you inherited, administered or implemented it, plus the subledgers around it such as the close management, accounts payable, payroll and billing tools. Audit history: who the external auditor was, whether the opinion was clean, how many and how large the audit adjustments were, and whether any significant deficiency or material weakness was ever communicated and what you did to remediate it. Because the role controls payments, expect a background check and often a credit check, run with disclosure and written consent under the Fair Credit Reporting Act, plus reference calls to a former CFO and sometimes the audit partner.
What technical accounting questions come up in a controller interview?
A controller interview works through a reliable list: the revenue standard's five steps and the difference between deferred revenue, a contract asset and unbilled receivables; lease classification, the entries at commencement and how operating and finance lease expense patterns differ; stock compensation measurement and expense recognition; capitalized internal-use software; the income tax provision, deferred tax assets and when a valuation allowance is required, including the newer disaggregated rate reconciliation disclosure; business combinations, the opening balance sheet and intangibles recognized separately from goodwill; and expected credit losses on trade receivables. If the company holds inventory, add standard cost setting, purchase price and usage variances, absorption and the excess and obsolete reserve. Answer out loud, with the entry and both sides, and do not hedge.
What should a controller resume lead with?
A controller resume should open with a four-line scope block: current title, company revenue and industry, ownership structure (family-owned, private equity backed, venture backed or public), entity and currency count, team size, ERP, and whether the company is audited. Then one context line under each employer giving the same facts for that company, because a bullet about managing the monthly close is unreadable without knowing whether it covered a $6M single-entity services business or a $400M manufacturer with inventory in three countries. Bullets should carry units: close days before and after with the definition stated, audit adjustments reduced, days sales outstanding improved, the ERP conversion and whether the first close after go-live landed on time, and the reconciliation backlog cleared with what it turned up.
Is the controller job being automated by AI?
The core is not, and the layer underneath it is, substantially. Transaction coding, invoice capture and matching, bank feed categorization, reconciliation preparation, data extraction from contracts and leases, and first drafts of flux explanations and technical memos are now automated or heavily assisted. What has not moved is judgment on estimates, accountability for numbers that outsiders rely on, control over who can move money, and the relationships with an auditor, a lender and a chief executive. Offshoring and outsourced accounting providers have in fact moved more transactional headcount than AI has so far. The practical effect on hiring is that accounting teams are smaller and more senior, and controllers are assessed on whether they can design and evidence a review control over output a machine produced.
How long does controller hiring take?
A controller search takes four to eight weeks at a typical private mid-size company, running through a recruiter screen, a CFO interview focused on the close and the audit, a technical or case exercise, peer interviews, a session with the chief executive or the private equity sponsor, then references and checks. Public company processes run eight to sixteen weeks because a board or audit committee is involved and the background and reference process is formal. At companies below roughly $25M in revenue with no CFO it can be two conversations with the owner plus a call to the outside CPA firm, with an offer inside two weeks. The small-company version tests trust and cash sense far more than technical depth.
Is a CMA good enough instead of a CPA for a controller role?
For operating roles, often yes. The CMA is two exams plus a bachelor's degree and two years of experience, and its cost accounting and performance management content maps directly onto manufacturing, distribution and divisional controller work, where it is genuinely respected. It will not satisfy a board, an audit committee or a sponsor that has decided the controller must be a CPA, and it carries little weight for technical reporting, audit-facing and pre-IPO roles. Treat it as a strong credential for operating controller jobs and a weak substitute for audit-facing ones. If you are undecided about your path, the CPA keeps more doors open.
Where can I find real controller salary figures?
Start with live job postings in pay-transparency jurisdictions such as Colorado, California, New York, Washington and Illinois, where employers must publish a range attached to a real role with stated scope. Then use the BLS Occupational Employment and Wage Statistics series for SOC 11-3031, Financial Managers, which is where controllers are classified, filtered by metro area and industry, reading it as a shape rather than a quote because it also contains treasurers and finance directors. Cross-check the Robert Half Salary Guide and other specialist accounting recruiter guides, which break pay out by company revenue, the dimension that moves controller pay most. For the bonus, ask the employer for the target percentage, the formula and the actual payout against target for the last three years rather than trusting a published range.
Put this on a resume in about a minute
Paste your history once and point it at the Controller posting you are looking at. No account, no card.
Build my resume free More roles