5 exercises — choose the best-structured answer to FinOps Engineer interview questions covering cloud cost allocation, EC2 rightsizing, Savings Plans vs Reserved Instances, unit economics, and the FinOps Foundation maturity model.
Structure for FinOps interview answers
Quantify cost savings with specific percentages and dollar amounts
Reference FinOps Foundation maturity model phases (Crawl, Walk, Run)
Explain trade-offs between cost optimisation and performance/availability
Name the FinOps practitioner role and its cross-functional responsibilities
0 / 5 completed
1 / 5
The interviewer asks: "How would you design a cloud cost allocation strategy for an organisation with 50+ AWS accounts?" Which answer best demonstrates technical depth?
Option B is the strongest: it addresses tag governance enforcement (SCPs), names three concrete allocation models for shared services, distinguishes chargeback from showback with a maturity-based recommendation, adds operational tooling (Cost Anomaly Detection, Config rules for compliance), and closes with a reporting cadence. Option A and C describe basic tagging without governance or shared-service treatment. Option D oversimplifies — per-account billing doesn't solve shared service allocation. Structure: tag governance → allocation models → chargeback vs showback → automation → reporting cadence.
2 / 5
The interviewer asks: "What is your approach to rightsizing EC2 instances and how do you present the findings to engineering teams?" Which answer best demonstrates technical depth?
Option B is the strongest: it specifies the data collection window (14 days, weekly patterns), names the tooling (CloudWatch, Compute Optimizer), introduces a risk classification (low/medium/high based on p99 utilisation), describes the report structure, and emphasises co-ownership and staging validation. Option A names the wrong tool (Cost Optimizer is a made-up name — it's Compute Optimizer) and skips the partnering aspect. Option C identifies a signal (CPU <10%) but lacks the full workflow and risk framing. Option D defers to a third-party tool without demonstrating the analytical approach. Structure: collect utilisation data → run recommendations → classify by risk → present contextually → co-own the migration → track realised savings.
3 / 5
The interviewer asks: "When would you recommend Savings Plans over Reserved Instances, and vice versa?" Which answer best demonstrates technical depth?
Option B is the strongest: it quantifies the discounts (66% SP, 72% standard RI, 54% convertible RI), explains the flexibility trade-off mechanically (instance family changes and SP vs RI treatment), gives a concrete layered strategy, introduces coverage analysis as the decision driver, and addresses commitment risk with a phased term approach. Options A and D are directionally correct but lack the numerical specificity and layered strategy. Option C gets the EC2/RDS split right but doesn't explain why. Structure: define discount levels → explain flexibility mechanism → give layered strategy → run coverage analysis → model commitment risk.
4 / 5
The interviewer asks: "How do you calculate and communicate unit economics (cost per customer or cost per transaction) to product and engineering leadership?" Which answer best demonstrates technical depth?
Option B is the strongest: it explains unit selection methodology, separates fixed from variable costs, specifies the tooling (Grafana, Cost Explorer), emphasises the trend over time (not just a snapshot), and demonstrates how unit economics informs product and engineering decisions with a concrete ROI example. Options A and D describe the calculation but miss the fixed/variable separation and the decision-making application. Option C involves finance but lacks the engineering integration and dashboard approach. Structure: define the unit → tag and map costs → separate fixed vs variable → build trend dashboard → use for trade-off decisions → present in business reviews.
5 / 5
The interviewer asks: "Describe the FinOps Foundation maturity model and how you would move an organisation from Crawl to Run phase." Which answer best demonstrates technical depth?
Option B is the strongest: it defines each phase with specific deliverables (not just adjectives), names the FinOps FOCUS specification and Cloud Intelligence Dashboards, identifies the four enablers for progression, warns against the most common failure mode (skipping Walk), and introduces domain-level maturity assessment. Options A and C give the phase names but lack the specific deliverables and enablers. Option D is a general observation without technical content. Structure: define each phase with specific deliverables → name four enablers for progression → identify failure modes → introduce domain-level maturity assessment.