As featured in
Built by a hiring manager who's conducted 1,000+ interviews at Google, Amazon, Nvidia, and Adobe.
Built by a hiring manager who's conducted 1,000+ interviews at Google, Amazon, Nvidia, and Adobe.
Practice the real Business Analyst questions Goldman Sachs asks, out loud, and get your interview readiness score. Everything you need to prepare is below.
Free to start, no credit card. Interview formats vary by team, level, and location — use this guide as preparation, not a guaranteed sequence.
A practical preparation outline based on commonly reported stages. Your actual process may differ.
A recorded video interview with structured behavioral and motivational questions. Goldman uses AI-assisted evaluation alongside human review. Candidates typically have 2-3 minutes per question with limited retakes.
Key frameworks and strategies for Business Analyst interviews.
Structure answers with Situation, Task, Action, Result. Describe the business problem (20%), your requirements gathering and analysis approach (35%), solutions designed with stakeholder collaboration (25%), and quantified business impact (20%). Show systems thinking.
The skill areas Goldman Sachs evaluates in Business Analyst interviews.
Use these 42 prompts to prepare clear examples. They support practice and are not a claim that every question is asked by Goldman Sachs.
Discuss stakeholder interviews with open-ended questions, workshops, observation, document review, and surveys. Use techniques like Five Whys for root cause analysis. Create requirement traceability matrix, validate with stakeholders, identify dependencies, and document assumptions. Cover eliciting functional vs non-functional requirements.
Align your answers with Goldman Sachs's core values.
Goldman puts client interests first in everything it does. Demonstrate how you have prioritized serving others' needs and creating value for stakeholders above personal interests.
Goldman's reputation depends on uncompromising integrity. Show examples of ethical decision-making, transparency, and maintaining trust in high-stakes professional situations.
Practical tips to focus your preparation.
Goldman expects strong technical proficiency regardless of division. Know DCF, LBO, comparable company analysis, and precedent transactions inside and out. Practice explaining complex concepts clearly and concisely — interviewers assess both knowledge and communication.
Follow financial markets daily. Know what major indices are doing, understand recent M&A deals, and have informed views on macroeconomic trends. Goldman wants people who are genuinely passionate about finance, not just well-prepared for interviews.
Compare Business Analyst interviews across companies
One to two phone or virtual interviews with Associates or Vice Presidents. Technical questions cover valuation, accounting, and market knowledge. Behavioral questions assess teamwork, leadership, and motivation for finance.
Four to six back-to-back interviews with professionals ranging from Vice Presidents to Managing Directors. Each interview is approximately 30 minutes and combines technical deep-dives with behavioral assessment. This is the defining round of Goldman's process.
The interview panel discusses candidates after Superday. Goldman typically communicates decisions within one to two weeks. Offers often come with a phone call from a senior team member.
Phone Screen (30 min): BA experience, methodology knowledge, communication style Case Study Round (60 min): Requirements gathering, process analysis, solution design Technical Round (45 min): Documentation, data analysis, technical understanding Stakeholder Round (45 min): Conflict resolution, negotiation, change management Final Round (30-45 min): Culture fit, business acumen, career aspirations
Revarta is purpose-built for the rounds that actually decide Business Analyst hiring. Five things candidates we work with say make the difference:
Behavioral signal extraction. Business Analyst interviews test how you navigated stakeholder requirements vs technical reality, scope changes, and conflicting priorities across business units. Revarta's coaching layer surfaces the question behind the question for each theme, so you understand what the interviewer is really testing.
Voice practice with delivery feedback. Tone, pacing, filler words, answer duration — the non-verbal half of the interview. Practicing out loud with honest feedback builds the muscle memory that holds when the real interview starts.
Hiring-manager-grade feedback. Revarta is built by a former Google, Amazon, and Adobe hiring manager who has run 1,000+ real interviews. Feedback is calibrated to what Business Analyst interviewers actually assess — not the agreeable "great answer!" defaults that ChatGPT and most AI tools give you.
Story Builder for your specific experience. The Story Builder layer helps you mine your résumé and project work for the moments that map to Business Analyst-specific behavioral themes. Most candidates leave half their best stories on the table — Revarta finds them.
Cross-session progress tracking. Track your readiness across Business Analyst-relevant behavioral themes. Not "are you getting more comfortable" but "are you actually improving."
Related: Interview Coach vs. Interview Copilot · Free Interview Prep Tools — No Signup · Try Revarta free.
Listen to understand underlying needs and constraints, facilitate discussion to find common ground, prioritize based on business value/urgency, escalate to decision-makers with data, document trade-offs. Show diplomatic negotiation skills and focus on business outcomes over individual preferences.
Functional describes what system should do (user logs in, generates report). Non-functional describes how system should perform (response time < 2 seconds, 99.9% uptime, security standards). Discuss testing approaches for each and why non-functional requirements are often overlooked.
Use "As a [role], I want [feature], so that [benefit]" format. Good acceptance criteria are specific, measurable, achievable, relevant, and testable (SMART). Include edge cases, error scenarios, and success metrics. Discuss INVEST principles for user stories.
Use STAR method. Show impact assessment (scope, timeline, cost), stakeholder communication, updating documentation, managing expectations, and ensuring team alignment. Discuss change control process and balancing flexibility with project stability.
Validate through prototypes/mockups, user acceptance testing, stakeholder reviews, traceability to business goals, and pilot programs. Discuss root cause analysis to ensure solving right problem. Cover measuring success metrics post-implementation.
Document current state (as-is process map), identify pain points through data and stakeholder feedback, analyze bottlenecks and waste, design future state (to-be process), calculate ROI, create implementation plan. Use frameworks like Lean, Six Sigma, or value stream mapping.
Discuss BPMN (Business Process Model and Notation) or flowcharts. Identify start/end points, activities, decision points, actors, and systems involved. Cover swim lanes for different departments/roles. Show understanding of different diagram types (high-level vs detailed, as-is vs to-be).
Document current state capabilities, define desired future state based on requirements, identify gaps in people/process/technology, prioritize gaps by impact and effort, develop action plan. Discuss root cause analysis and linking gaps to business objectives.
Define KPIs upfront - cycle time, error rate, cost per transaction, customer satisfaction, employee productivity. Establish baseline before changes, track during implementation, compare post-implementation. Discuss leading vs lagging indicators and balanced scorecard approach.
Analyze process maps, review data (wait times, queue lengths), conduct time studies, gather feedback from process participants. Use tools like value stream mapping, fishbone diagrams, Pareto analysis. Discuss Theory of Constraints and focusing on biggest bottleneck first.
Define business question, identify data sources, clean and validate data, perform exploratory analysis, apply statistical methods, visualize findings, derive insights, make recommendations. Discuss tools (Excel, SQL, Tableau) and ensuring data quality.
Understand executive information needs and decision-making, use clear hierarchy with KPIs prominent, provide context with trends and benchmarks, minimal clutter, interactive drill-downs, automated data refresh. Discuss design principles (minimal ink-to-data ratio, pre-attentive attributes).
Validate data sources, check for duplicates and nulls, cross-reference with known figures, use data profiling, document assumptions, implement data quality rules, reconcile across systems. Discuss impact of bad data on decisions and building trust in analysis.
Correlation shows association between variables, causation means one causes the other. Establish causality through controlled experiments, A/B testing, regression with controls, time-lagged analysis, or natural experiments. Give examples of spurious correlations.
Break down high-level requirements into detailed functional specs, create wireframes/mockups for UI, define data models, specify business rules, document integration points, provide use cases and user flows. Discuss collaboration with architects/developers and technical feasibility assessment.
Understand data flows between systems, map data fields, define integration architecture (API, ETL, messaging), address data transformation needs, handle error scenarios, ensure data consistency. Discuss real-time vs batch, and involving IT teams early.
Use case describes system behavior from user perspective. Include actor (bank customer), preconditions (valid card, sufficient funds), main flow (steps), alternative flows (insufficient funds, wrong PIN), postconditions (balance updated). Discuss when to use use cases vs user stories.
Create decision matrix with criteria (cost, timeline, technical feasibility, scalability, user experience, risk), score each option, involve stakeholders in weighting criteria, perform cost-benefit analysis, consider implementation complexity. Document rationale for recommendation.
BA facilitates refinement sessions, writes user stories with acceptance criteria, clarifies requirements during sprint, validates deliverables, gathers feedback. Discuss difference from traditional waterfall BA role, working in sprints, and continuous collaboration with team.
Document clear baseline scope, implement change control process, assess impact of changes (time, cost, quality), communicate trade-offs to stakeholders, prioritize changes, maintain requirements traceability. Show understanding of balancing flexibility with control.
Identify risks through brainstorming and lessons learned, assess probability and impact, prioritize with risk matrix, develop mitigation strategies, assign owners, monitor regularly. Discuss types of risks (technical, resource, dependency, business) and contingency planning.
Identify all costs (development, implementation, training, maintenance), quantify benefits (revenue increase, cost savings, efficiency gains), calculate ROI or NPV, consider timeframe and payback period, account for intangibles. Present with sensitivity analysis for assumptions.
Waterfall is sequential (requirements → design → build → test), Agile is iterative with incremental delivery. Use Waterfall for stable requirements, regulatory environments, fixed scope. Use Agile for evolving requirements, rapid delivery, user feedback loops. Discuss hybrid approaches.
Mention certifications (CBAP, PMI-PBA), professional organizations (IIBA), conferences, online courses, reading (BA Times, PM blogs), networking with peers, applying new techniques on projects. Show commitment to continuous learning.
Use STAR method with quantified impact. Show how you uncovered hidden issue through data analysis or requirements validation, presented findings with evidence, influenced stakeholders, and achieved measurable result. Demonstrate business acumen and value-add of BA role.
Analyze picking/packing process flow, identify bottlenecks using data (cycle time, error rates), benchmark against best practices, recommend automation opportunities, design improved workflow. Discuss Amazon's customer obsession and operational excellence principles.
Research seller pain points, conduct stakeholder interviews, define user stories with acceptance criteria, prioritize by impact, create mockups for key flows, specify integration with existing systems. Show understanding of two-sided marketplace dynamics.
Interview diverse user personas (remote workers, hybrid teams, enterprise admins), understand current workflow and pain points, analyze competitor features, create user stories, define success metrics. Discuss accessibility and enterprise security requirements.
Review metrics (CTR, conversion rate, CPC, Quality Score), segment by campaign/keyword/geography, identify underperforming areas, recommend bid adjustments, ad copy tests, keyword optimization. Discuss attribution and measurement challenges at Google scale.
Demonstrate thorough understanding of free cash flow projections, WACC calculation (cost of equity via CAPM, cost of debt, capital structure weights), and terminal value methods (Gordon Growth vs. Exit Multiple). Be prepared for follow-up questions on sensitivity analysis.
Equity Value = Enterprise Value - Net Debt. Share price = Equity Value / Shares Outstanding = ($500M - $100M) / 10M = $40. Be prepared for follow-ups about including preferred stock, minority interests, or adjusting for cash.
Goldman expects genuine market awareness. Choose a current event you have followed closely. Present a structured view covering what happened, why it matters, different perspectives, and your informed opinion. Show you follow markets because you are genuinely interested, not just for interviews.
Be specific about what draws you to Goldman — its deal flow, culture, specific divisions, or people you have met. Generic prestige answers will not differentiate you. Show genuine understanding of what the day-to-day work involves.
Cover the key LBO mechanics — sources and uses of funds, debt structure, operating assumptions, debt paydown schedule, and returns analysis. Explain ideal LBO characteristics: stable cash flows, strong assets, efficiency opportunities, and clear exit strategy.
Bond prices fall (inverse relationship), equities may decline (higher discount rates, tighter financial conditions), and the dollar typically strengthens (higher yields attract capital). Show nuanced thinking about second-order effects and current market conditions.
Banking is an intense environment. Show that you can maintain quality and composure under pressure. Focus on your prioritization approach, how you managed energy and focus, and the quality of the outcome despite the pressure.
Standard DCF is challenging for pre-revenue companies. Discuss risk-adjusted NPV (rNPV) for the drug pipeline, probability-weighted scenarios by clinical trial phase, comparable transaction analysis, and sum-of-the-parts valuation. Show awareness of the unique challenges in biotech valuation.
Choose a stock you have genuinely researched. Structure your pitch: company overview, investment thesis (why now), key catalysts, valuation analysis, and risk factors. Show conviction but also awareness of what could go wrong. Goldman values well-reasoned contrarian thinking.
Show emotional intelligence and professional maturity. Explain how you expressed your perspective respectfully, listened to their viewpoint, and worked toward a resolution. Goldman values people who can disagree constructively while maintaining strong relationships.
This tests your ability to simplify complex concepts. Use a relatable analogy — like a toy shop that earns money. Show you can communicate finance to non-experts, a key Goldman skill.
This classic Goldman puzzle tests logical reasoning. Think systematically — you need 7 races minimum. Walk through your logic step by step, showing structured problem-solving.
Goldman is built on meritocratic principles where the best ideas and hardest workers advance. Demonstrate your drive for excellence and willingness to be evaluated purely on performance and contribution.
Goldman operates through collaborative teamwork across divisions and geographies. Show how you have contributed to team success, supported colleagues, and built strong working relationships.
Goldman's partnership structure means everyone has a stake in the firm's success. Demonstrate long-term thinking, ownership mentality, and willingness to invest in the institution beyond your immediate role.
Goldman demands excellence in every deliverable and interaction. Show your commitment to the highest professional standards, attention to detail, and continuous pursuit of improvement.
Superday involves four to six consecutive interviews. Practice maintaining energy, enthusiasm, and sharpness across multiple sessions. Each interviewer evaluates independently, so treat every interview as your first. Stay hydrated and manage your energy carefully.
Goldman's HireVue video interview is often the first screening. Practice answering questions on camera with clear structure, natural delivery, and professional presentation. Record yourself to identify distracting habits and improve your on-camera presence.
Almost every Goldman interview includes a stock pitch or market discussion. Prepare two to three well-researched investment ideas with clear theses, catalysts, and risk analysis. Show genuine analytical rigor, not just headline-level knowledge.
Goldman interviewers can quickly distinguish between candidates who are passionate about finance and those attracted primarily by prestige. Read financial news voraciously, understand deal dynamics, and be able to discuss markets conversationally and knowledgeably.