Controller phone screen questions: close days, the last audit, CPA status and team scope

A controller phone screen is a 25 to 30 minute recruiter call that checks ownership before the CFO or owner spends time on the candidate: the company's size and entity count, whether the statements are audited or reviewed, the team that reports to them, and the ERP. Then ask how many business days the close takes, what it was when they took it over and what they changed; what the auditors proposed last year; and, if the seat requires it, whether their CPA license is active and in which state. Real controllers answer with days, adjustments and role names. Candidates stretching from accounting manager describe the tasks without saying where the decisions sat.

This page is the first-call version. The deeper bank, with controller types, SOX controls, team questions and a close worked example, is in controller screening questions; the hiring manager's loop, with a variance exercise and a controls check, is in the interview guide for finance roles. For the people who report to a controller, use staff accountant phone screen questions; the general call structure is in phone screen questions for recruiters.

What do you need from the CFO or owner before the call?

The title covers a corporate controller at a lender-backed company, a plant controller who lives in standard costs, and a public company controller who supports SEC filings. Get these facts first; the controller job description template shows where each belongs in the posting.

How should a 25-minute controller phone screen run?

1. Opening (1 to 2 minutes). Who you are, the company and seat in two sentences, the length of the call, and your consent line if you record.
2. Knockouts (5 minutes). Company type and size, team, audit status, ERP, CPA if required, location and close-week hours, work authorization.
3. The close calendar test (6 to 7 minutes). Days now, days at the start, what changed, what they review.
4. The last audit (5 minutes). Engagement type, proposed adjustments, the management letter.
5. Credentials (2 minutes). License status and state, or exam status.
6. Motivation, pay expectations and logistics (4 minutes). Why now, pay needed, notice.
7. Their questions and the next step (2 minutes). Consent to submit and availability for the CFO.

The timings are a planning example. If a knockout fails, say so kindly and end the call or redirect.

Which knockout questions come first?

The authorization wording follows the Justice Department's Immigrant and Employee Rights Section FAQ, which says an employer may ask applicants whether they have the legal right to work in the United States and whether they will need sponsorship for an employment visa (as of November 2026).

What is the close calendar test?

Ask: "How many business days is your close today, what was it when you took it over, and what did you change? And what do you personally review before the books lock?" Write the answers into a grid like this one:

What good and weak answers sound like (examples invented):

• Good: "Eleven days when I started, six now. We moved accruals to a pre-close and replaced a manual intercompany spreadsheet; low-risk reconciliations went quarterly." Days, the changes in their own words and a trade-off.
• Good, and honest: "It's still nine days. Two acquisitions landed in my first year, so I chose to get the entities on one chart of accounts first." The candidate explains a number that did not move.
• Weak: "We close fast." Ask: "How many business days, and what is on day one?" If there is no number, score it as not shown.
• Weak: the review step is "everything", on a team of six, or nothing specific such as a flux review above a threshold or manual entries above a limit.

Follow up once: "What was the last error that got past the close, and how did it surface?" A controller who owns the close has an honest example and the control added after it. The deeper bank has more close questions if the hiring manager wants them on the first call.

What is the last-audit question?

The last audit is the best outside evidence of a controller's work, because a firm tested it. Three questions fit a screen:

1. "Who is the auditor, and is it an audit or a review?" Good: the firm and the engagement type. Weak: does not know.
2. "How many adjustments did the auditors propose last year, and what was the largest?" Good: a count or range, the largest one and why it happened. Weak: "None", at a company that changed systems or bought another business that year.
3. "Was there a management letter, and what did you change because of it?" Good: the comment and the fix, such as segregation of duties in payments. Weak: has never seen one.

At a public company, add: "Did the auditor attest to internal control, or was it management's assessment only?" The SEC's compliance guide on filer definitions explains that certain low-revenue issuers, those eligible to be smaller reporting companies with annual revenue under $100 million, are excluded from the accelerated filer definitions and so do not need the Section 404(b) auditor attestation, though management must still assess internal control (as of November 2026). "SOX experience" therefore means different things at different companies.

How do you verify CPA status and other credentials?

Ask the exact status, because candidates and resumes blur it: licensed and active, licensed but inactive, passed the exam but not licensed, or sitting for it. The details below come from each body's own site, as of November 2026.

If the CPA is required by the client, treat it as a knockout and check it before you submit. If it is preferred, note the status and move on; a strong close and audit story usually matters more to the CFO than the letters.

How do you test motivation on a controller phone screen?

How do you ask about pay without asking salary history?

Many states and cities bar employers and their agents from asking about a candidate's current or past pay, as of November 2026; the list is in salary history ban states. Ask what the candidate needs from the new role.

Keep personal finances off the screen as well. The EEOC's page on financial information says federal law generally allows employers to ask about applicants' finances, but the EEO laws bar using that information to discriminate, and some states have their own laws on employers' use of it (as of November 2026). If the client runs credit checks for finance seats, the FCRA background check process and credit check laws for employers apply to that step, not to your call. If the candidate volunteers a pay number, keep it out of your notes and the submittal and record the expectation instead. This is general information, not legal advice.

When should you advance a controller?

An example rule to agree with the CFO: advance when every knockout passes, the close calendar scores at least 2, and two other areas score 3. Hold when one claim, such as a clean audit after a system change, needs a reference to confirm. Decline when a knockout fails. Once hired, the 30-60-90 day plan for controllers picks up with the balance sheet review, the audit relationship and the close.

What should you not ask a controller on a phone screen?

The EEOC says pre-employment inquiries should be limited to what is needed to judge whether someone is qualified, and that questions which screen out people based on race, color, sex, national origin, religion or age may be used as evidence of intent to discriminate unless a business purpose justifies them. More examples are in illegal interview questions.

If you take the screen through your computer, Interview Signal keeps the close calendar and audit questions pinned until you ask them and writes the candidate's own numbers and words beside each score, with no bot in the call.