Chief Financial Officer (CFO) Resume Writing & Executive Branding

Works: Naming exactly which functions you owned: FP&A, treasury, tax, controllership, investor relations, internal audit.

Stalls: Writing that you led finance.

Why: The CFO title spans controller-level stewardship to full strategic partnership. The reader cannot place you until you say which.

Works: Capital markets work with your role in it: raises, debt facilities, refinancings, IPO readiness, transaction financing.

Stalls: Naming the company's capital events without your part.

Why: This is the fastest separator in a CFO field, and it is also the easiest claim to check.

Works: Your working relationship with the audit committee and the board.

Stalls: Omitting governance exposure.

Why: Audit committee credibility is a gate. A committee filling a public or sponsor-backed seat treats its absence as disqualifying.

Works: Systems and close work written with the business result: cycle time, forecast accuracy, what decisions became possible.

Stalls: An ERP implementation listed as an achievement.

Why: Nobody buys a system. They buy faster and better decisions.

Works: The ownership model and reporting environment: public reporting, sponsor-held, pre-IPO, private with covenant obligations.

Stalls: Treating each employer as an interchangeable finance seat.

Why: Quarterly guidance and a lender covenant package demand different instincts.

Works: Margin and cost outcomes stated as numbers you influenced.

Stalls: Describing cost discipline as a philosophy.

Why: Adjectives are unverifiable, so the reader discounts them to zero.

Works: A LinkedIn profile carrying the same scope and capital record as the resume.

Stalls: A profile that says finance leader and stops.

Why: Finance searches begin on LinkedIn, and a thin profile behind a strong resume raises the question of which one is accurate.

Works: Evidence you shaped a decision the business would otherwise have made differently.

Stalls: Reporting results without influence on them.

Why: This is the whole scorekeeper question, and one concrete instance settles it.

They assume: A CFO from a controller or audit background is a technician rather than a partner.

You answer it by: Leading with decisions you influenced outside finance: pricing, capital allocation, which businesses got funded and which did not.

Why: The gap between reporting the numbers and shaping them is the whole distinction the reader is testing for.

They assume: A CFO with no transaction history has not been tested.

You answer it by: Naming the events and your role inside them: diligence led, structure negotiated, integration owned, covenant renegotiated.

Why: Transactions are where finance leadership becomes visible, and a record without them reads as steady state only.

They assume: Private company experience does not carry into a public reporting environment.

You answer it by: Stating the regime you operated under and what it demanded: audit, controls, board reporting cadence, external scrutiny.

Why: The reader is estimating how much of the job would be new to you on day one.

Works: The finance functions you owned, listed once: FP&A, treasury, tax, audit, investor relations, technology if it reported to you.

Stalls: Assuming the title implies the scope.

Why: CFO covers a wide range of actual jobs. The reader cannot price you until they know which one you held.

Works: Results as movement: margin from one figure to another, days sales outstanding before and after, cost of capital at entry and at exit.

Stalls: Static figures that describe the company rather than your effect on it.

Why: A number with no starting point proves the company existed, not that you changed it.

Works: Two pages, with the transaction record grouped so it can be read in a single pass.

Stalls: Deals scattered through the roles where they happened.

Why: The transaction record is usually the first thing scanned, and scattering it forces the reader to reassemble it.