Accounting resumes are read by people who audit numbers for a living, so every figure on yours gets the same scrutiny as a trial balance. Vague bullets ("assisted with month-end close") fail that review; specific ones ("closed the books in 5 days, down from 9, for a $40M revenue entity") pass it. The profession's screening habit is tie-out: a controller reading your resume is mentally checking whether the claims support each other, whether the dates reconcile, and whether the scope matches the title. Write for that reader.
Three things get checked before anything else: CPA status (licensed, candidate, or absent), your ERP systems, and the size of what you accounted for. Put all three in the top half of page one and the rest of the resume gets read charitably. Bury any of them and the reader assumes the answer is unflattering, because in accounting hiring, silence on a standard credential is read as absence. The bullet shape that works everywhere: what you owned in the close, in which system, at what entity scale, and what improved; our bullet-writing guide covers deriving those numbers honestly.
Section order for an experienced accountant: header with credential in the name line ("Daniel Okafor, CPA"), a three-sentence summary, experience, a dedicated Licenses & Certifications section, skills split into accounting and systems, education last. That dedicated certifications section is not formatting taste: parsers map it directly to the credential fields recruiters filter on, while a CPA mentioned only in prose can drop out of the structured data. New grads flip the middle: education (with GPA if strong, since accounting is one of the few fields where firms still ask), exam progress, and internships climb above unrelated work.
Know who reads in what order. A recruiter or firm HR screener goes first, matching credential, ERP, and industry against the req. The hiring manager (a controller, accounting manager, or partner) reads second and differently: they look for close ownership versus close participation, for whether your reconciliations sound like ones you performed or ones you watched, and for the judgment markers of the trade: accrual reasoning, materiality thresholds, audit posture. "Supported month-end activities" tells a controller nothing; "owned 25 balance-sheet reconciliations to a 5-day close" tells them exactly which seat you can fill.
Write the experience section around the close calendar. The close is the metabolism of every accounting job, so anchor each role in it: days to close, entries owned, reconciliations performed, statements produced, and who consumed them. Then layer the differentiators: process improvements (close days cut, entries automated), audit outcomes (adjusting entries, management-letter comments, PBC turnaround), and technical projects (ASC 606 revenue work, ASC 842 lease adoption, system migrations). Public accounting roles translate to client scope: client count, revenue ranges, industries, and areas owned. Use the profession's verbs: reconcile, accrue, close, file, and tie out beat "handled" everywhere they are true; the action verbs guide sorts more by claim.
Split the skills section into accounting and systems, and be exact in both. The accounting line carries the technical vocabulary recruiters search: month-end close, GAAP reporting, balance sheet reconciliation, fixed assets, sales and use tax, whichever are honestly yours. The systems line is a hard filter: name your ERP precisely (NetSuite, SAP, Oracle, QuickBooks) and your close tooling (FloQast, BlackLine), because retraining on a new ERP is an expense hiring managers actively avoid. Excel deserves specificity too: "advanced Excel (pivot tables, XLOOKUP, Power Query)" is a claim; "Microsoft Office" is filler. Our skills section guide covers the trim order when space runs out.
Give credentials their own section and state them precisely. Licensed: "CPA, Illinois, active" with the year. In progress: "CPA candidate, 3 of 4 sections passed" is a legitimate, respected line, and firms filter for it; vague versions ("pursuing CPA") read as stalled. Not pursuing: compensate with system depth (NetSuite administration, automation projects) or a CMA, which carries real weight in cost and management accounting. Education stays short after your first role: degree, school, year, plus the 150-hour completion if your state requires it for licensure. Continuing education lists only when it signals a specialty: ASC 606, ASC 842, or international reporting coursework tied to work you actually did.
Format like the conservative document your reader expects. One column, standard headings, a serif or plain sans font, PDF unless the portal demands otherwise, no photo for US applications. Accounting hiring skews traditional and parses everything through an ATS first, so decorative templates cost twice: they scramble parsing and they signal unfamiliarity with the field's norms. One page up to roughly eight years; two pages once technical projects and audit history genuinely fill them. Name the file plainly (your name, resume) and proofread the rendered PDF, because a typo on an accountant's resume is read as a control failure. The complete parsing rules are in our resume format guide.
Avoid the failures that recur on accounting resumes. Duty lists copied from a job description ("responsible for month-end close activities") with no scale or outcome; claims of "managing" a close the candidate participated in, which dies at the first walkthrough question; ERP names omitted because "systems are all similar" (they are not, and the filter is literal); exam status hidden, which readers interpret pessimistically; and numbers that do not tie, like a "$100M entity" at a company the reader knows is a tenth that size. Each fix is mechanical; run your draft against our common mistakes guide before the next application.
On the top third: use a summary, not an objective, from your first accounting job onward. Three sentences: credential and years, current scope (entity size, close ownership, systems), one improvement or audit outcome. The level-calibrated variants below show that shape at staff, senior, and manager-track weight. Objectives earn their place in three cases covered further down: the new grad with exam progress and internships, the bookkeeper stepping up to staff accountant, and the public-accounting auditor moving to industry. Whichever you use, rewrite it per posting family: a close-focused senior role and a technical-accounting role reward different first sentences.
Tailoring in accounting is mostly vocabulary honesty. Postings say exactly what they mean: "full-cycle close", "consolidations", "multi-entity", "SOX environment", "percentage-of-completion". Mirror the phrases that are true for you, once each, in your summary or top bullets, and do not mirror the ones that are not, because accounting interviews verify technical claims quickly. Match the industry dialect too: manufacturing wants standard costing and inventory, SaaS wants deferred revenue and ASC 606, construction wants job costing and WIP. Ten minutes per application; the tailoring guide shows the method.
The 2026 reality: the profession is short-staffed and automating at the same time. The CPA pipeline has thinned, which strengthens credentialed candidates, while close automation (FloQast, BlackLine, AI-drafted entries and flux commentary) is standard at mid-size companies, which strengthens candidates who automated something rather than resisted it. A bullet like "automated 30 recurring entries, saving 20 staff hours per close" now signals more than another year of manual tie-outs. Use this page in that spirit: the resume below is a complete, realistic example rendered by our actual template engine, and the "Use this example" button opens it in the builder so you can swap in your own entities, systems, and close numbers. Then raid the bullet bank, check the keyword list against your target posting, and read the ATS extract at the bottom to see literally what a parser keeps.
Domande frequenti
- Public accounting to industry: how do I frame the switch?
- Translate audit work into the corporate tasks it maps to, because the controller reading your resume is hiring for a close seat, not an audit seat. Walkthroughs become process documentation, substantive testing becomes reconciliation and analysis, PBC management becomes close coordination, and reviewing client entries becomes preparing your own. Lead with client scale and industries so the reader sees relevant scope: "audited manufacturers from $10M to $200M revenue" tells a $50M manufacturer you have seen their problems at their size. Surface the fragments of preparer work public accounting gave you: proposed adjusting entries, financial statement drafting, technical memos on revenue or leases. Address the known gap honestly in interviews rather than papering over it on the resume: auditors arrive strong on documentation and skepticism and light on system mechanics (posting entries, running the subledgers), and hiring managers price that in for the first cycle. The compensating asset is that you know exactly what the year-end audit will demand, so claim it: "maintains audit-ready support year-round" is a differentiator most industry-trained candidates cannot honestly write. Timing note: the natural exit windows after busy season are well understood by recruiters, so a move at two to four years reads as standard career design, not flight. Quantify per the numbers guide.
- I don't have my CPA. Am I stuck?
- Not for staff and many senior roles, but the ceiling is real and it sits around the manager level, especially anywhere that touches external reporting or public-company work. The practical playbook depends on your position relative to the exam. If you are eligible and willing, write your status precisely: "CPA candidate, 2 of 4 sections passed, FAR scheduled March" is a strong line that many firms filter for, while "pursuing CPA" with no specifics reads as stalled. If you are short of the 150 hours, name the plan ("completing final 12 credit hours, December"). If you are not pursuing it at all, build the alternative currency deliberately: deep ERP capability (NetSuite administration, BlackLine implementation), automation work that saved measurable hours, or a CMA, which is genuinely respected in cost accounting, manufacturing, and FP&A-adjacent roles. Industry choice matters too: private companies, smaller entities, and operationally focused teams weight the license far less than public filers and firms do. What does not work is silence: a resume with no credential line invites the pessimistic assumption. State where you stand, show what compensates, and target the roles where your actual strengths are the filter.
- How far back should my accounting resume go?
- Ten to fifteen years of detail; anything older earns one line or drops off entirely. Accounting standards, systems, and expectations turn over fast enough that decade-old specifics read as filler: pre-ASC 606 revenue work, retired ERPs, and Sarbanes-Oxley war stories from the implementation era tell today's reader nothing about your current capability. The trim order when space tightens: cut bullets from your oldest detailed role first, then collapse roles beyond the ten-year line to a single heading (title, employer, years, no bullets), then drop pre-accounting jobs entirely unless one explains a gap. Never trim the elements recruiters filter on to save space: credential status, ERP names, entity scale, and close ownership are doing more screening work than any prose. Length follows the same logic: one page up to roughly eight years, two pages once consolidations, technical adoptions (606, 842), system migrations, and audit history genuinely fill them; a padded second page reads worse than a dense first one. One exception to the ten-year rule: a marquee employer or a credential-relevant role (Big Four years, a public-company close seat) can stay as a one-liner indefinitely, because the name itself carries information. Our resume length guide covers the edge cases.
- How do I show close improvement without badmouthing the process I inherited?
- State the before and after as measurements, not judgments, and let the delta speak: "cut close from 9 days to 5" describes an achievement without characterizing the predecessor, while "fixed a broken close" describes a grievance. This matters because the controller interviewing you is often the person who owned that process, or knows the person who did, and because accounting is a small-world profession where discretion is itself a screened trait. The strong pattern has three parts: the inherited state as a neutral baseline ("9-day close, 60 aged unreconciled items"), the mechanism you changed ("re-sequenced dependencies, pre-closed recurring entries, moved reconciliations to a standing checklist in FloQast"), and the durable result ("5-day close held for eight consecutive cycles"). Mechanism is what separates credible improvement claims from luck: a reader who sees the how believes the number. Share credit accurately ("with the AP lead" where true) because interviews probe ownership, and an overclaimed improvement collapses under two follow-up questions. Where the improvement is still in progress, say so precisely: "reduced aged items from 60 to 12, cleanup plan on track for zero by Q3" reads as honest and current. The same discipline applies to audit findings you remediated: describe the control now in place, not the failure that preceded it.
- What do accounting employers want to see about automation and AI?
- Evidence that you automated something specific and kept control of it, because that is exactly what they need done internally. Close automation is now standard mid-market practice: recurring entries scheduled in the ERP, reconciliations auto-certified below thresholds in FloQast or BlackLine, flux commentary drafted by AI and reviewed by a human. The resume line that works names the tool, the object, and the saved capacity: "automated 30 recurring journal entries and 12 reconciliations in NetSuite, saving 20 staff hours per close" is a hire; "experience with AI tools" is noise. Equally valued is the control instinct: a bullet about the review step you kept ("AI-drafted variance commentary, reviewed line by line before CFO distribution") signals that you understand automation as a control question, which is how controllers think about it. What to avoid: listing generic AI assistants as skills, claiming automation you merely used rather than built or configured, and implying that automation replaced your judgment rather than extending it. In interviews expect the probe "what would you automate here first?", so arrive with your actual answer from your last close: the repetitive entries, the roll-forward schedules, the tie-outs that never vary. Candidates who resisted automation for a decade and candidates who trust it blindly both screen out; the market wants the accountant in between.
- Staff accountant vs senior accountant vs accounting manager: how do I know which to apply for?
- Match on ownership, not years, because titles inflate and deflate by company size. The staff level executes assigned pieces of the close: entries, a set of reconciliations, schedules someone else reviews. The senior level owns the close outcome for an area or an entity: sequencing the checklist, reviewing staff work, fielding auditor questions directly, producing statements. The manager level owns people and the calendar: hiring, review structure, multi-entity consolidation, and the meetings where the CFO asks why the number moved. Read your own resume against those verbs. If your bullets say "prepared" and "assisted", you screen as staff regardless of tenure; if they say "owned", "reviewed", and "presented", senior is honest; if they say "led the team" with headcount attached, manager is in range. Company size shifts the bands: a senior at a $30M company often does manager-scope work, while a senior at a Fortune 500 may own three reconciliations in depth, and recruiters at each know their own dialect. When in doubt, apply one level up only where you can defend every bullet in a walkthrough, and let the summary state your target plainly ("seeking consolidation exposure and a path to manager"), because accounting hiring rewards candidates whose self-assessment ties out.