The specific signals an experienced financial analyst hiring panel grades on during the eight-second scan.

• Forecast accuracy stated with the underlying plan size

  '±5% across FY24 on a $42M ARR plan' is the metric every CFO grades on first.

• Specific model artifact named (not 'various models built')

  Naming the unit-economics model, the pricing-sensitivity tool, the headcount planner gives the panel something to ask about.

• Business partner cited by role + seniority

  'Co-built with the CFO' beats 'partnered with senior leadership.'

• FP&A tool named by exact product (Adaptive, Anaplan, Pigment)

  Modern FP&A stacks are credentialing fast — name what you ship in weekly.

• Excel depth specified (Power Query, dynamic arrays, etc.)

  'Excel modeling' is filler. The specific functions you use signal depth.

• SQL fluency surfaced at mid+ levels

  Senior FA roles at SaaS increasingly expect SQL against the warehouse, not just Excel pulls.

1. 1

   Lead with the analysis surface and the business partner

   FA hiring panels grade scope first. The first thing they look for is what type of analysis you own and which business partner you support. 'Senior FP&A analyst owning the GTM forecast and quarterly board pack at a Series C SaaS; partner with the VP of Sales weekly' is twenty-five words that tells a recruiter exactly the job you've done.

   For staff / entry analysts, the pattern shifts: 'FP&A analyst supporting the engineering cost-center forecast (320 employees, $52M annual spend).' For senior analysts, the surface widens to a function — GTM, R&D cost, capex planning, or pricing analytics.

2. 2

   Quantify by forecast accuracy and business outcome

   The single highest-value metric on an FP&A resume is forecast accuracy. 'Held forecast accuracy within ±5% across FY24 on a $42M ARR plan' is the bullet a CFO recognises. Variance commentary depth also matters — explaining why actuals deviated from plan is what differentiates analysts who get promoted from those who don't.

   Other metrics that get read: • Cycle-time improvements (close from T+12 to T+7, board-pack assembly from 4 days to 1). • Specific model artifacts (the unit-economics model, the pricing-sensitivity tool, the headcount-planning template). • Business decisions the analysis drove (the v3 pricing rebuild, the org-design refresh, the Q3 hiring freeze). • Audit-side outcomes (cleared all FY24 audit-related FP&A workpapers without modification).

3. 3

   Show modeling depth without listing every model type

   Most FA resumes list 'three-statement modeling, DCF, scenario analysis, sensitivity tables, financial modeling' as bullets. That signals exposure, not depth. The way to demonstrate depth is to surface ONE meaningful model and describe what it drove.

   Examples: • Built the unit-economics model (CAC payback by acquisition channel, LTV/CAC by segment) that became the board's primary deck for the FY25 GTM strategy. • Authored the pricing-sensitivity tool (15 packaging scenarios × 4 demand elasticity curves) that informed the v3 pricing rebuild; ARPU lifted 22% post-launch. • Designed the headcount-planning model integrating the recruiting funnel + ramping productivity; quarterly headcount-actual vs plan variance held within ±3%.

4. 4

   Name the partner — by function and seniority

   Finance is graded heavily on business-partner work. 'Partnered with leadership' is filler. 'Co-built the unit-economics model with the CFO' is concrete. 'Partnered with the VP of Sales on weekly forecast calls; forecast accuracy held within ±8%' is concrete and outcomes-anchored.

   For senior FA roles, naming C-suite partners (CFO, CEO, CRO) is the senior-level signal hiring panels look for. Mid-level analysts name VPs and Directors; senior analysts name C-suite or board-level audiences.

5. 5

   Close with credentials and ongoing learning

   FA-relevant credentials at the bottom: CFA (charter or progress), CPA if you're an analyst with accounting depth, MBA if applicable. Conferences and continuing education: Wall Street Prep, Breaking Into Wall Street, AICPA finance-focused programs, Macabacus, F9 Finance. For modeling-heavy roles, FMVA (Corporate Finance Institute) carries some weight at certain companies.

Each follows the [verb] [object] [number] structure hiring managers grade against. Copy them as a starting point, swap in your own numbers, and read the annotation to understand why each one works.

• Forecast

  Held forecast accuracy within ±5% across FY24 on a $42M ARR plan; authored monthly variance commentary that the CFO referenced in three board meetings.

  Why it works: Pairs the headline metric every CFO grades on (±5%) with depth signal (variance commentary referenced in board meetings).

• Model

  Built the unit-economics model (CAC payback by acquisition channel, LTV/CAC by segment) that became the board's primary deck for the FY25 GTM strategy.

  Why it works: Specific model named with structure + the board-level decision it informed. Verifiable in interview.

• Pricing

  Co-built the pricing-sensitivity tool with the CRO + product marketing (15 scenarios × 4 elasticity curves); v3 pricing rebuild lifted ARPU 22%.

  Why it works: Cross-functional partnership + model dimensions + measurable business outcome.

• Process

  Cut board-pack assembly cycle from 4 days to 1 by automating variance commentary pulls in Adaptive Insights + standardising the slide template.

  Why it works: Cycle-time metrics on operational FP&A work are rarely surfaced but heavily weighted.

• Headcount

  Designed the headcount-planning model integrating recruiting funnel + ramping productivity; quarterly variance vs plan held within ±3%.

  Why it works: Model integration detail + the variance metric proves the model worked, not just that it was built.

• Memos

  Authored the engineering R&D investment memo presented to the board in FY24 capital planning; influenced approval of the $4M ML infrastructure budget.

  Why it works: Memo authorship + board-level audience + specific capex outcome.

• Systems

  Migrated the FP&A team from Excel-only forecasting to Adaptive Insights over a 4-month implementation; partnered with the NetSuite admin on integration.

  Why it works: Migration scope, tooling named (Adaptive + NetSuite), partner function.

• M&A

  Built the three-statement model + LBO analysis on the Acme/Nimbus acquisition ($340M EV); transaction closed within original guidance.

  Why it works: Specific transaction, EV size, model types used, outcome verifiable.

• Cash

  Reduced the variance between forecast cash burn and actual cash burn from ±12% to ±4% via a weekly cash-flow rolling-13-week forecast.

  Why it works: Treasury / cash-flow modeling work is rarely surfaced but heavily valued at growth-stage.

• Scenario

  Modeled the SaaS unit-economics rebuild for the board's FY25 strategic planning offsite; presented six scenario paths with sensitivity tables.

  Why it works: Senior-level audience (board offsite), specific deliverable (six scenario paths), depth signal (sensitivity tables).

• Sales finance

  Partnered with the VP of Sales on weekly forecast calls (Clari + Salesforce); forecast accuracy on sales-pipeline component held within ±8% across FY24.

  Why it works: Tool stack inline (Clari + SFDC), cadence named (weekly), partner role, accuracy metric.

• Mentorship

  Mentored two FP&A analysts through their first independent monthly close + variance commentary; both promoted to senior in 18 months.

  Why it works: Mentorship with verifiable outcomes (promotion within 18 months).

Same intent, two phrasings. Read why the right column lands on the keep-pile and the wrong column doesn't.

Strong verbs lead strong bullets. Replace generic openers (worked on, helped with, was responsible for) with the specific verb that matches what you actually did.

ATS pipelines weight your Skills section as a structured list. Include 15-25 of the items below if they match your experience — not soft skills.