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 Jane Street 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 timed assessment covering probability, combinatorics, mental math, sequences, and logical reasoning. Questions are challenging and require both accuracy and speed. This is a highly selective filter.
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 Jane Street evaluates in Business Analyst interviews.
Use these 40 prompts to prepare clear examples. They support practice and are not a claim that every question is asked by Jane Street.
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 Jane Street's core values.
Jane Street is a community of deeply curious people who love solving hard problems. Demonstrate genuine love for mathematics, puzzles, and intellectual exploration beyond what is required.
Jane Street emphasizes collaborative thinking over individual brilliance. Show how you work through problems with others, share ideas openly, and build on teammates' contributions.
Practical tips to focus your preparation.
Probability is the foundation of Jane Street interviews. Be fluent in conditional probability, Bayes' theorem, expected value, variance, and common distributions. Practice solving novel probability problems — Jane Street creates new puzzles regularly, so memorization will not help.
Jane Street expects fast, accurate mental arithmetic. Practice daily with multiplication, division, percentages, and estimation. Learn techniques like difference of squares, anchoring, and chunking. Speed and accuracy both matter — interviewers time you informally.
Compare Business Analyst interviews across companies
One to two phone interviews focused on probability, expected value calculations, and mental math. You may encounter trading-style questions where you must quote prices and manage risk in hypothetical markets. Interviewers assess both your answers and your reasoning process.
A full-day on-site consisting of five to seven interviews and activities. Includes probability and math problems, a mock trading session, a behavioral interview, and lunch with the team. The trading simulation evaluates market-making intuition, risk management, and performance under pressure.
The interview panel reviews all rounds and discusses candidates thoroughly. Jane Street's hiring bar is extremely high and requires strong consensus. Successful candidates receive an offer with details on role and competitive compensation.
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.
Calculate E[max(X,Y)] by summing over all possible maximum values weighted by their probabilities. For each value k from 1 to 6, P(max = k) = P(both ≤ k) - P(both ≤ k-1) = (k/6)^2 - ((k-1)/6)^2. The answer is 161/36 ≈ 4.47. Show the systematic calculation clearly.
The probability of 5 heads in a row is (1/2)^5 = 1/32. Fair value is $100 * 1/32 = $3.125. But as a trader, you would bid below fair value and offer above. Discuss how you would set bid-ask spread based on edge requirements and risk.
Use the difference of squares: 37 * 43 = (40-3)(40+3) = 1600 - 9 = 1591. Jane Street expects rapid mental math. Practice techniques like difference of squares, breaking into components, and estimation for quick verification.
Use Bayes' theorem. P(double-headed | 10 heads) = P(10H | double) * P(double) / P(10H). P(10H) = 1 * (1/100) + (1/1024) * (99/100). Work through the calculation carefully. The answer is 1024/1123 ≈ 91.2%. Show your Bayesian reasoning step by step.
Think about adverse selection and the winner's curse. Your expected profit depends on when your bid gets hit versus when your ask gets lifted. A naive midpoint quote will lose money because you disproportionately trade when your estimate is wrong. Discuss how to widen spreads to account for adverse selection.
Apply the Kelly Criterion. Optimal fraction = (bp - q) / b where b=1, p=0.6, q=0.4. Kelly fraction = (1*0.6 - 0.4)/1 = 0.2 or 20% of bankroll per bet. Discuss why maximizing expected value is different from maximizing expected log wealth and the practical considerations of Kelly sizing.
Jane Street values intellectual honesty deeply. Choose a genuine example of being wrong, how you recognized it, and how you updated your thinking. Show that you are comfortable with being wrong and can change your mind when presented with evidence.
Structure your estimate: Chicago population (~2.7M), households (~1M), piano ownership rate (~5%), tuning frequency (1-2x per year), pianos per tuner per day, working days per year. Show clear assumptions and arithmetic. Jane Street cares more about your structured approach than the exact number.
Be authentic about what draws you to Jane Street — the intellectual culture, collaborative environment, problem-solving nature of trading, or specific aspects of market-making. Show you understand what Jane Street does and why it appeals to you beyond compensation.
Expected value per bet = 0.5 * 1.5 - 0.5 * 1 = 0.25 (positive). You should play. For bet sizing, apply Kelly: f* = (0.5 * 1.5 - 0.5) / 1.5 = 1/3 of bankroll. Discuss the difference between a positive-EV game and optimal sizing, and why overbetting can still lead to ruin.
Jane Street values people who are honest about what they know and do not know. Demonstrate comfort saying "I don't know" and show how you reason through uncertainty transparently.
Jane Street bridges theory and practice. Show that you can apply mathematical concepts to real-world problems and understand the practical limitations of theoretical models.
Jane Street invests heavily in teaching and expects everyone to be both a teacher and a learner. Demonstrate how you have helped others understand complex concepts and how you actively seek to learn from those around you.
Jane Street fosters an open culture where ideas are shared freely and hierarchy is minimal. Show that you communicate openly, welcome feedback, and contribute to a transparent working environment.
Even for non-trading roles, understanding market-making, bid-ask spreads, adverse selection, and risk management is valuable. For trading roles, deeply understand how to quote prices, manage inventory, and think about edge. The mock trading session is a critical component.
Jane Street cares as much about your reasoning process as your final answer. Practice verbalizing your thought process as you solve problems. Share your approach, state your assumptions, and work through calculations transparently. Silence is worse than a slightly wrong approach.
Jane Street deeply values intellectual honesty. If you do not know something, say so clearly and then reason through it. Never bluff — interviewers will probe and a false claim of knowledge is far worse than honest uncertainty. Show you can reason under uncertainty.
Many Jane Street questions involve game-theoretic reasoning, optimal decision-making under uncertainty, and risk management. Study the Kelly Criterion, auction theory, and information economics. Understanding these concepts helps you approach trading simulations and probability puzzles systematically.