Why Every Controller Listing Wants a CPA, an MBA, and Ten Years at a Two-Year-Old Startup

This is satire, although the hiring committee has asked that it be treated as a serious candidate requirement. The modern controller posting is no longer a request for someone who can own the close, build a team, protect controls, and tell management what the numbers mean. It is an archaeological record of every anxiety ever felt by a CFO, investor, board observer, payroll vendor, and one director who once heard the phrase “audit readiness” at a conference.

The Ideal Candidate Has Already Lived This Exact Company’s Future

Consider the standard listing for Controller, High-Growth Disruptive Platform. The company has been operating for twenty-four months, has 37 employees, three legal entities, a revenue model described as “flexible,” and an ERP that is technically a spreadsheet with a lock icon. It seeks a CPA with an MBA, 10–15 years of progressive experience, public-company reporting exposure, pre-IPO experience, international consolidations, debt covenant management, M&A integration, stock compensation expertise, SOX ownership, NetSuite implementation, and the ability to be “hands-on.”

The apparent contradiction—how can someone have ten years of experience at a two-year-old startup?—is easily resolved. The candidate must have worked at the company spiritually. They should have anticipated its Series B, its first late close, and its decision to sell in three currencies before anyone had selected a chart of accounts.

At Seedling Orbital Snacks, a fictional company making protein bars for commercial satellites, the Controller role is expected to “operate at both 30,000 feet and in the details.” This means the candidate will present a five-year margin narrative to the board at 9:00 a.m., investigate an $18.42 employee reimbursement for “launch-adjacent coffee” at 10:15, and explain why neither activity can happen until someone approves the new vendor form.

Credentials as Decorative Load-Bearing Architecture

The CPA requirement is usually sincere, except when it is not. In a regulated business, a complex reporting environment, a public company, or a company with an audit committee that asks difficult questions, a license or deep equivalent technical background may be central to the job. In the rest of the market, “CPA required” can mean one of several things: the CFO is a CPA and finds the designation reassuring; the prior controller was a CPA; the outside auditors have strong feelings; or the hiring manager would like a small brass plaque on the org chart.

Then comes the MBA. The MBA is included not because the role requires discounted cash flow analysis—though the controller may need to challenge it—but because the company wants evidence that the candidate can enter a conference room without causing the strategy deck to recoil. The listing will say “CPA and MBA strongly preferred,” creating a candidate shaped like a Swiss Army knife that also has feelings about revenue recognition.

Meanwhile, the actual first six months may be dominated by less credential-sensitive work:

• Finding out which bank account payroll actually debits.
• Explaining that “we’ll true it up next quarter” is not a control environment.
• Getting department leaders to submit invoices before the vendor threatens to involve folklore.
• Determining whether the sales team’s side agreement is a contract, a promise, or performance art.
• Closing the books in fewer than 19 business days without inventing a new month.

The Job Description Was Written by a Committee, Which Is Why It Has Eight Owners

Controller listings become extraordinary when several stakeholders contribute without being required to remove anything. The CEO adds “strategic business partner.” The CFO adds “technical accounting leader.” The board adds “IPO-ready.” The Head of People adds “player-coach.” The procurement lead adds “experience optimizing P2P.” The IT leader adds “systems transformation.” Someone who has just completed an expense report adds “must be scrappy.” No one deletes a bullet because every bullet represents a trauma.

The resulting role has a reporting line to the CFO, a dotted line to Operations, a close relationship with Legal, partnership expectations with every budget owner, and responsibility for “building scalable infrastructure.” In practice, this means the controller is accountable for the system, the process, the documentation, the exception, the exception to the exception, and the person who insists their invoice cannot be coded because the cost center is “more of a mindset.”

Company size changes the mix, which is the part the listing tends to conceal. At a smaller company, a controller may genuinely need to be broad: close owner, policy setter, treasury backup, tax coordinator, audit lead, systems administrator, and manager of one heroic senior accountant. At a larger company, the role may be more specialized, with dedicated tax, treasury, SEC reporting, internal audit, and systems teams. The requirements should change accordingly. Instead, both companies use the same template, presumably maintained in a vault beneath the Society for Maximum Optionality.

How the Interview Tests Whether You Can Perform the Myth

The screen usually begins with a recruiter asking whether you have “been there before.” This does not mean: have you closed complex books, built sound processes, led people, and made defensible judgments in ambiguity? It means: can you name a former employer whose funding round, industry label, and headcount curve resemble ours closely enough to soothe us for eleven minutes?

Later, the CFO may ask how you would prepare the company for an IPO. A useful answer is not a ceremonial recitation of SOX, auditors, and NetSuite. It is to ask what exists now: entity structure, revenue arrangements, close calendar, controls, audit history, reporting deadlines, systems ownership, and the actual horizon. But the job description has already declared that the candidate must have “taken two companies public,” preferably before lunch.

The final case study may require you to diagnose a delayed close, design a finance organization, assess a broken approval workflow, and present a plan in 30 minutes. The committee will admire candidates who clarify scope, identify dependencies, distinguish immediate stabilization from longer-term design, and state what information they would need. It will then select the person who says “I simply centralized everything” with the calm certainty of someone who has never met Accounts Payable.

A More Accurate Posting, Should Anyone Wish to Use One

The honest version would read: “We need a controller who can bring order to a business that has outgrown informal finance, while helping us decide which formalities actually matter now. You will need strong judgment, credibility with leadership, enough technical depth for our reporting risk, and the willingness to work in imperfect systems. Some experience in our industry would help; exact replicas of our past are not required. We will tell you what is broken, who owns what, whether this is a builder role or a steady-state role, and what authority comes with the accountability.”

This posting may attract fewer mythical CPA-MBA astronauts with a decade at a company founded during the previous administration. It may, however, attract controllers who can do the job. The true observation beneath the joke is simple: the best hiring process starts when a company separates the capabilities the role genuinely needs from the anxieties it would like a new hire to absorb.