Financial Controller Resume Examples & Writing Guide

Two pages is normal at this level, but page one has to carry the story. Below is page one for a controller with 11 years in accounting, 5 of them running the books. The people and companies are invented. Every role names revenue, team size and the ERP, because those three facts decide whether a CFO keeps reading.

Controller postings get fewer applicants than analyst postings, but the screening is harder, because the CFO is handing over the books. Four questions decide the first call.

• Have you closed books this size before? Revenue, entity count and whether there is inventory, multi-currency or revenue recognition complexity. A $30M single-entity service business is not preparation for a $400M multi-plant manufacturer.
• How clean is your audit history? Clean opinion, no material weaknesses, few adjustments. Say it plainly, because silence here reads badly.
• Do you run a team or do the work yourself? Give the headcount and the roles that report to you. Controllers who have never managed get moved to assistant controller offers.
• Which ERP, and did you implement or just use it? An implementation or migration on your resume is worth more than five years of steady-state use, because it is the project the hiring company is often about to start.

“Half the controller resumes I read are a job description with the pronouns removed. The ones that stand out give me three numbers in the first paragraph: revenue, close days and team size. If those are missing, the only way to find out what you did is an interview, and my first call goes to the person who told me up front.”

People search for controller achievement examples because the job feels like maintenance: the books close, the audit passes, nothing burns. Your achievements are hiding in the improvements, the clean-ups and the systems. Rewrite duties into results like these.

Four lines at most. Years, size of the books, team, close speed, audit record, ERP, CPA. Skip adjectives entirely.

Twelve to fifteen items, grouped so a CFO can find the accounting content, the systems and the leadership in three seconds. Only name what you would survive a technical question on.

• Technical accounting: US GAAP, consolidation, multi-entity and multi-currency, revenue recognition (ASC 606), leases (ASC 842), inventory and standard costing
• Close and reporting: close calendar design, account reconciliations, flux analysis, financial statement preparation, board and lender packages
• Audit and controls: external audit management, PBC coordination, control documentation and testing, segregation of duties, SOX 404 if you have worked in a public company
• Treasury and cash: 13-week cash forecasting, covenant compliance, banking relationships, AP and AR cycle management, DSO and DPO improvement
• Tax coordination: sales and use tax, 1099s, property tax, working with outside preparers on federal and state returns
• ERP and systems: NetSuite, SAP, Oracle, Microsoft Dynamics 365, Sage Intacct, QuickBooks Enterprise, and any implementation or migration you led
• Automation tools: BlackLine or FloQast for reconciliations, Bill.com, Concur, Power Query, Power BI
• Leadership: hiring, training and reviews, offshore or shared service teams, working with plant managers and sales leaders who do not read financial statements

Most US controller postings ask for a CPA, and many treat it as a hard filter. If you have one, make it impossible to miss. If you do not, say what you have instead and stop apologizing for it.

• Public accounting time is worth naming even if it was a decade ago. Write it as a line in your work history or a clause in your summary: audit trains the exact judgment a CFO wants.
• An MBA helps if you are aiming at finance director or CFO, and matters less for a pure controller role. List it above your bachelor's degree with the concentration.
• Never write an inactive or lapsed license as if it were active. License status is checked on the state board lookup, and a wrong claim ends the process.
• Industry-specific credentials are worth a line where they apply: NetSuite or Sage certifications, a Certified Internal Auditor (CIA) if you came from internal audit.

• Two pages is right for a controller. One page hides the audit and systems detail; three pages reads as a career history rather than an application.
• Reverse chronological, single column, no tables or text boxes. Accounting recruiters use applicant tracking systems heavily, and a two-column layout is the most common parsing failure.
• Put a short header block under your name: CPA, ERP names, entity count. Some CFOs never scroll past it.
• Mirror the posting's language: month-end close, consolidation, US GAAP, internal controls, audit coordination, ASC 606, ASC 842, fixed assets, AP and AR oversight, cash flow forecasting, ERP name, team size.
• Send PDF, named lastname-firstname-controller.pdf. Keep a Word copy for recruiters who reformat.
• US conventions: no photo, no date of birth, no marital status. If you are applying from the UK or Ireland, where this document is called a CV and a photo is sometimes used locally, drop the photo for US employers.

If the posting says finance manager, finance director or head of finance, read the duties before you retitle anything. In smaller US companies those titles often describe the same job as controller plus FP&A, and the resume that matches the duties beats the resume that matches the title.