INTERVIEW GUIDE

Amazon Financial Analyst Interview: Questions & Process

Amazon's Financial Analyst interview blends FP&A fundamentals (variance analysis, forecasting, free cash flow) with the same 16 Leadership Principles that drive every Amazon loop. Expect to defend numbers, build a simple business case, and answer LP behavioral questions, often with light SQL or Excel involved. The process is a recruiter screen, a hiring-manager call, then a 4-5 round loop.

The interview process

1. Recruiter screen — ~30 min call

Tests: background, why finance at Amazon, comfort with data, and logistics

2. Hiring manager screen — 45 min

Tests: your finance fundamentals, how you think about metrics, and an opening Leadership Principles question

3. Technical / FP&A rounds — 2 rounds, 45-60 min each

Tests: variance analysis, forecasting, building a business case, NPV/free-cash-flow reasoning, and sometimes light SQL or an Excel walkthrough

4. Behavioral (Leadership Principles) — woven through every round

Tests: STAR stories graded against LPs like Dive Deep, Ownership, Insist on the Highest Standards, and Earn Trust

5. Bar raiser — 45-60 min

Tests: an objective interviewer from outside the team probing both your analytical judgment and your LP stories

Questions you're likely to get

Technical

Actual spend came in 12% over forecast this quarter. Walk me through how you'd find the drivers.
Why does Amazon emphasize free cash flow over net income? How are they different?
How would you build a monthly operating expense forecast for a new fulfillment center?
Walk me through a simple NPV analysis. What discount rate would you use and why?
How do the three financial statements connect? If depreciation rises by $10, what happens to each?
What's the difference between fixed and variable costs, and why does it matter for a contribution-margin decision?

Role-specific

A business partner wants to launch a program you think is unprofitable. How do you push back with data?
What metrics would you put on a weekly business review for a retail category?
You find a discrepancy between two reports the night before a review. What do you do?

Behavioral

Tell me about a time you dug into the details of a dataset and found something others missed. (Dive Deep)
Describe a time you owned a deliverable end to end under a tight deadline. (Ownership; Deliver Results)
Tell me about a time you disagreed with a business partner and how you handled it. (Have Backbone; Disagree and Commit)
Give an example of when you raised the quality bar on a report or process. (Insist on the Highest Standards)
Tell me about a mistake you made in an analysis. How did you handle it? (Earn Trust)

How to answer (worked examples)

Actuals came in 12% over forecast — how do you find the drivers?

Show a structured variance approach. Break the 12% into price vs. volume vs. mix, then by cost category and business unit, until you isolate the few line items that explain most of the gap. Quantify each contributor, separate one-time from recurring, and close with a recommendation and a control to prevent recurrence. Amazon's Dive Deep LP rewards the analyst who decomposes the number instead of narrating it.

Why does Amazon emphasize free cash flow over net income?

Define both crisply: net income is accrual-based and includes non-cash items; free cash flow is operating cash flow minus capex, i.e., the cash the business actually generates after reinvestment. Explain that FCF is harder to manipulate and better reflects the ability to fund growth — which is why Amazon has long anchored on it. Bonus: mention how heavy capex (warehouses, AWS) makes the distinction material.

Tell me about a time you dug into the details and found something others missed.

STAR mapped to Dive Deep and Earn Trust. Situation: a report or forecast everyone trusted. Task: why you double-checked. Action: the specific reconciliation, query, or sanity check that surfaced the issue. Result: the corrected decision and the dollars or risk avoided. End with the process change you put in place so it wouldn't recur.

What Amazon looks for

Strong FP&A fundamentals: variance analysis, forecasting, and the cash-vs-accrual distinction
Comfort with large datasets — you reason from the numbers, not vibes (light SQL/Excel is a plus)
Business judgment: you connect financial analysis to an operating decision
LP alignment, especially Dive Deep, Ownership, and Insist on the Highest Standards, with metrics in your Result
Backbone to challenge a business partner respectfully with data
Red flag: shaky on how the three statements connect, or behavioral answers with no quantified outcome

FAQ

Is the Amazon Financial Analyst interview technical or behavioral?

Both, heavily. You'll get FP&A and accounting fundamentals plus modeling reasoning, but the Leadership Principles run through every round and can decide the outcome. Prepare equally for both.

Do I need to know SQL?

It helps. Amazon finance teams work with large datasets, and many roles value (sometimes expect) basic SQL to self-serve data. It's rarely a hard coding round, but being able to pull and check your own numbers is a real edge.

How much modeling will they ask?

Expect reasoning over a build: variance bridges, simple forecasts, NPV/payback logic, and contribution margin. Deep three-statement modeling is more an IB-style ask; here it's applied FP&A judgment.

How important are the Leadership Principles for a finance role?

Just as important as for engineers. Prepare 6-8 STAR stories tagged to LPs like Dive Deep, Ownership, and Earn Trust, each with a quantified result.

How long does the process take?

Typically 3-6 weeks from screen to offer, with the debrief and decision usually within days of the loop.

Practice defending your numbers out loud

It's one thing to know variance analysis — it's another to walk a skeptical interviewer through it while also landing a Dive Deep story. Rehearse the FP&A questions and the Leadership Principles answers out loud with OfferLoop's realtime voice coach before your Amazon loop.

Practice this interview out loud →

All Amazon interviews →Amazon Software Engineer interview →Amazon Data Analyst interview →Amazon Data Scientist interview →Amazon Data Engineer interview →

OfferLoop is an independent interview-practice tool and is not affiliated with, endorsed by, or sponsored by Amazon. All company names and trademarks are the property of their respective owners.

Interview formats vary by team, level and year, and this guide is compiled from general knowledge of publicly discussed hiring processes — treat it as preparation material, not an official description of Amazon's current process.