How to write a CV for a financial analyst role

What a hiring manager reads for first

A financial analyst CV gets scanned for two things before anything else: what you modelled and what happened because of it. Not "performed financial analysis to support business decisions" — that sentence appears on hundreds of CVs a week and tells the reader nothing. They want the specific model type (three-statement, DCF, LBO, variance, working capital), the specific output (a forecast, a valuation range, a budget variance report), and the specific consequence (a decision made, a number that changed, a process that got faster).

Most hiring managers in this field have built the same models you have. They read your bullet points the way a mechanic listens to an engine — they can tell in one sentence whether you actually did the work or supervised someone who did, or copied a template. "Built a rolling 13-week cash flow forecast used to renegotiate a covenant with the lender" survives that test. "Responsible for cash flow forecasting" does not.

They also scan for the software stack before the job titles, because it tells them how much retraining you need. If you list Excel and stop there, that reads as either junior or dated, depending on the rest of the CV. Name what you actually built things in: Excel with specific function use (array formulas, Power Query, VBA if you wrote macros rather than recorded them), plus whichever of Power BI, Tableau, SQL, Python, Adaptive Insights, Anaplan, Hyperion, SAP BPC, or Bloomberg Terminal you've used and for what. "SQL" alone is vague — "wrote SQL queries against the general ledger to reconcile intercompany balances" tells them you can be productive in week one.

Qualifications and where they actually sit

The CFA designation is the one credential in this field that changes how a CV is read, and it changes it differently depending on level. If you're a CFA charterholder, that goes near your name or in a one-line summary at the top — not buried in an education section at the bottom. If you're partway through — Level II cleared, Level III scheduled — say exactly that: "CFA Level II, passed [year]" or "CFA candidate, Level III exam [month/year]". Don't write "pursuing CFA" with no detail; it reads as unfinished and vague rather than in progress.

Other credentials that carry weight depending on the specific role: the CAIA for alternative investments work, the FRM if the role touches risk analysis rather than pure valuation or FP&A, and an ACA, ACCA or CPA if the role sits closer to the accounting side of financial analysis (technical accounting, financial reporting analysis, audit-adjacent work). None of these substitute for each other, and listing one when the role calls for another suggests you haven't read the advert closely — which is exactly the kind of thing the person screening CVs is trained to notice.

An MBA or a master's in finance is worth a line but not a headline unless the employer has specifically asked for it or the role is at a level where it's genuinely differentiating (associate-to-VP transitions in banking-adjacent analyst roles, for instance). A bachelor's degree in finance, economics, accounting or a quantitative field is assumed; spending more than one line on it usually means something more relevant got squeezed out.

How to evidence experience so it's actually checkable

Financial analyst work is unusually easy to make sound better than it was, which means hiring managers have learned to discount anything that isn't specific. Two things make a bullet point credible rather than decorative.

First, scale. State the size of what you were responsible for: the revenue of the business unit, the AUM of the fund, the size of the budget, the number of cost centres, the size of the deal. "Managed the quarterly forecasting process for a $40m business unit across four cost centres" is checkable in a way that "managed forecasting processes" is not. If you don't remember exact figures, an approximate range is better than nothing and still far better than omitting scale altogether.

Second, the audit trail of accuracy. Financial analysts are judged partly on how close their forecasts came to reality, and stating that — where you have the figure and it reflects well on you — is one of the strongest things you can put on a CV in this field. "Forecast quarterly revenue within a defined variance tolerance over six consecutive quarters" is a stronger sentence than any adjective you could add. If you don't have a clean number, describe the mechanism instead: what you forecast, how often, and what you did when actuals diverged from plan. That last part — what you did with a variance — often matters more to a reader than the size of the variance itself, because it shows judgement rather than just arithmetic.

Where you sat relative to the model also matters and gets glossed over constantly. "Built" a model and "maintained" a model are different skills; "presented" a model's output to a committee is a third skill again. If you built the model, say so. If you inherited someone else's and extended it, say that instead of implying you built it from scratch — this comes up in interviews and inflating it costs you credibility at exactly the point you need it most.

What gets left off, and why that's a mistake

The most common omission is the reporting line and the audience. Financial analysts routinely leave out who they presented findings to — the CFO, the board, a lending committee, a portfolio manager — because it feels like status-signalling rather than evidence. It isn't. It tells the reader the level of scrutiny your numbers survived and the level of communication skill the role required. "Prepared monthly variance analysis" says less than "prepared monthly variance analysis presented directly to the CFO and divisional heads."

The second common omission is the accounting standard or regulatory framework the work sat under, when it's relevant. If you worked under IFRS or US GAAP specifically, or your analysis fed into SOX-compliant reporting, or you worked within a regulated fund structure, naming it tells a reader in a similarly regulated environment that you won't need retraining on the basics. Leaving it out is understandable — it feels like background noise rather than an achievement — but for an employer trying to work out how much onboarding you need, it's some of the most useful information on the page.

The third is the negative result. Financial analysts sometimes flagged a deal that shouldn't proceed, a forecast that revealed a problem, a variance that led to a cost being cut. These get left off because they don't feel like wins in the traditional CV sense. They're often the strongest evidence of judgement on the whole document, because they show you were trusted to catch something, not just calculate something.

Finally, tool depth gets flattened. "Advanced Excel" is a phrase that has stopped meaning anything because everyone writes it. What differentiates candidates is naming the specific capability: array formulas, Power Query for data transformation, VBA for automation, or building a model with more than a handful of interlinked tabs and scenario toggles. If you can build a sensitivity table with data tables or Goal Seek without looking it up, say what you built it for, not that you can do it in the abstract.

What to actually do with this

Go through your last two or three roles and for each major responsibility, write down three things: the size of what you were working with, the specific model or report type, and what happened as a result. If you can't fill in one of those three for a bullet point, that's usually the sign it's too vague to survive a hiring manager's first scan — rewrite it or cut it.

Then check your qualifications section against the specific advert, not against a generic template: does it name CFA, CAIA, FRM, ACA/ACCA/CPA, or a specific software platform, and does your CV answer that exactly rather than approximately? A mismatch here is one of the most common reasons a financial analyst with the right underlying experience doesn't get a reply.

jobmarket.pro reads the advert in full, matches it against your actual experience, and writes the application from a single profile it can't invent experience into — which is the direct fix for a CV that's accurate but not landing.