A CFO resume needs to make the finance mandate clear: the business you served, your responsibilities, the people you led and the decisions or events you supported. Company revenue is useful context when disclosure is permitted, but it is not automatically revenue you generated or a P&L you owned.

This guide shows how to organize promotions, describe financial leadership and check claims about audits, refinancing and transactions. The sample is fictional. Its structure is a starting point, not evidence of a successful executive search or a universal recruiter preference.

Fictional example: Gregory Sloane, the employers, education, projects, training and recognition below are invented to demonstrate a resume structure. Contact details are placeholders. Replace every entry and skill rating with your own verifiable information.

The sample shows finance work beginning in 2006 and a CFO appointment in 2021. It does not claim a real transaction value, professional license or audit outcome. Its combined Controller/VP Finance entry illustrates grouping; applicants should give each actual promotion its own dates when available.

A useful summary gives the reader enough context to understand the target fit without disclosing restricted information. Choose the details relevant to the mandate rather than trying to meet an exact line count.

Consider these four elements:

Fictional wording example: “CFO of a privately held software business, responsible for finance planning, accounting coordination and lender reporting. Previously led the planning function; now oversee financing analysis and preparation of board materials.” Add authorized scope figures where they improve the description.

Replace vague praise with evidence, but do not force a number into every sentence. A specific responsibility, deliverable or decision can be informative without a metric. See the guide to writing a professional summary.

Grouping promotions under one employer can make a long tenure easier to follow. Separate employer entries can also work when the organization, location or role changed substantially. Neither format guarantees a particular ATS parsing result.

For a grouped entry, use the employer name, a short company description, then each title and its actual date range. A possible structure is:

Keep company context separate from your personal contribution. “Company revenue grew during my tenure” does not establish that you caused the growth. Update role-specific scope where responsibility changed, rather than attaching today’s team size to an earlier title.

Assign an accomplishment to the period when it happened. If work continued across promotions, explain that continuity instead of presenting the same result twice. Inspect parsed application fields to confirm that the employer, titles and dates were associated correctly.

Two pages can be a useful starting point for an experienced CFO, but the appropriate length depends on the application and relevant evidence. One page is not inherently inadequate, and a third page does not prove poor judgment. Follow the recipient’s instructions and keep the text readable.

Use relevance to allocate space; the one-page-or-two guide offers general considerations.

Earlier roles can be shorter when their detail repeats more recent work. Retain an older audit, sector, turnaround or systems example if it directly supports the target mandate. There is no automatic cutoff at ten years and no requirement to retain an employer only because its name is prestigious.

Keep titles and dates accurate even when reducing bullets. See how far back a resume should go for ways to prioritize a longer career.

A scope line explains the scale and boundaries of a role before the achievement bullets. Use figures only when accurate and authorized for disclosure. A range, percentage or anonymized description can still reveal confidential information.

Choose relevant details from these categories:

Fictional scope line: “Lead finance planning and accounting coordination for a privately held software group; manage the finance team and present forecasts to the CEO.” If permitted, add the actual reporting period, revenue range, entity count or team size.

For cash and debt, distinguish cash balances, committed facilities and drawn borrowings. For people, distinguish direct reports from the wider organization. Preparing audit-committee materials or presenting to the committee does not imply membership of the committee or a direct reporting line to it.

Describe the finance work the vacancy needs and the contribution you can substantiate. Close management, controls, planning, treasury and transaction support can all be relevant; an exit is not a requirement for every CFO role. Use precise action verbs to distinguish leading, approving, preparing and supporting.

A close improvement needs a consistent definition: calendar or business days, entities covered and the point considered complete. Faster is not automatically better if reconciliation or review work was deferred.

Hypothetical example: a reduction from ten to seven business days is three days, or 30%, using the same scope and definition. A qualitative bullet can instead explain the reconciliation checklist, ownership changes and exception review you introduced. Do not invent a day count.

Separate the financial-statement audit, internal-control assessment, any auditor opinion on internal control, and remediation work. A favorable opinion on financial statements does not by itself establish that no material weaknesses existed. PCAOB AS 2201 explains that a material weakness can exist even when the financial statements are not materially misstated.

Use the actual report, period and scope for an audit claim. “Prepared schedules and coordinated responses for the external audit” is different from performing an independent audit. Readiness work is not an audit opinion or proof of compliance. The SEC’s smaller-reporting-company guidance also notes that auditor-attestation requirements depend on filer status; do not assume every private or public company has identical Section 404 obligations.

State the transaction and your responsibility accurately: preparing forecasts, evaluating terms, coordinating lender diligence or leading negotiations are distinct contributions. Describe completed financing separately from a proposal or commitment.

Hypothetical arithmetic: a 100-basis-point reduction on a constant $10 million balance would reduce annual interest by $100,000 before fees and other changes. Actual savings may depend on draw levels, benchmark rates, amortization, hedging and transaction costs. Do not call a lower spread a reduction in total cost of capital without the supporting analysis.

For a sale or capital event, name the workstream you handled and the stage reached. Data-room preparation, quality-of-earnings support and management presentations do not automatically mean you negotiated or closed the deal.

Use transaction values or multiples only when disclosure is permitted and the definition is clear. Enterprise value, equity value, revenue and EBITDA multiples are different measures. A multiple alone does not establish transaction quality or personal achievement. An abandoned process can still demonstrate useful work when accurately described.

Keep team attribution, dates and evidence consistent. Do not disclose a confidential data room to prove a resume claim; use an authorized description and discuss verification through the appropriate process.

Some CFO applications use applicant tracking systems and others rely on search-firm or direct review workflows. This guide does not measure how frequently a keyword is used or establish a universal screening threshold.

Compare the actual vacancy with these possible areas of finance work:

A skills list can help navigation; experience bullets show how a standard or system was used. “Prepared revenue schedules for review during an ASC 606 implementation” describes a different responsibility from leading the accounting-policy decision. Do not inflate familiarity into implementation ownership.

Use terms from the specific posting only where accurate. Public-company reporting, lender reporting, 13-week cash-flow forecasting and IPO readiness are possible requirements, not interchangeable labels. SEC reporting experience should identify the actual work performed.

Make relevant qualifications and governance experience easy to find. Their placement is an editorial choice unless the application specifies otherwise. Neither an MBA nor a CPA is a universal requirement for all CFO jobs.

List an earned credential with its exact title, issuer or jurisdiction and accurate status. Do not use a regulated designation merely because you completed coursework or passed part of an exam. Confirm permitted wording with the relevant licensing authority when status has changed.

A relevant earlier qualification can remain useful; sharing a credential with a controller is not a reason to omit it. Distinguish professional certification from internal training. See credential placement guidance.

Ownership and stage can change the mandate, but they do not define every hiring decision. Read the vacancy, business context and instructions. These examples suggest emphasis to investigate rather than stereotypes about what each employer will accept:

For interim work, label the contract or engagement and its actual term. Describe the mandate, work completed and handoff; do not imply every departure followed successful completion. Group engagements under your consulting business or list them separately, according to the real relationship.

Maintain a factual base resume and tailor by selecting relevant evidence. In Roleframe, inspect imported dates and figures, and review any AI-assisted wording before using it. A match assessment is an editing aid, not an employer’s screening score or a forecast of interview success.

Use clear headings, consistent title and date formatting, and sufficient spacing for financial figures. A simple layout is a practical starting point, but no template guarantees parsing or a positive hiring decision. Check the ATS formatting guide and inspect the final file.

Follow the recipient’s accepted file types. For PDF, verify selectable text, symbols, line breaks and reading order. For Word, check layout in the exported file. Review parsed application fields where offered; neither file format is universally required or error-free.