← BNP Paribas Interview Insights

BNP Paribas·Software Engineer·Technical Phone Screen·Intermediate

Intermediate
May 2026

Summary

Thirty-minute technical screen for a Quant Engineer role at BNP Paribas that moved fast and mixed resume walkthrough with live quant and stats questions. Not a casual chat, they wanted formula-level answers on the spot.

Questions Asked (4)

Q1

Define the options Greeks, focusing on delta, and compute the delta exposure for a sample portfolio.

Technical Trade-offsProduct Analytics & Metrics
Author's notes

This is the kind of question where you think you know it until someone asks you to actually put numbers on a portfolio.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clearly defining the Greeks and their role in risk management, then focus on delta as the sensitivity of an option's price to changes in the underlying asset. For the portfolio delta, explain that it is the sum of each position's delta, and walk through a simple example with a few options and stock positions, computing the total delta exposure.

Pro tip: Emphasize that delta is not static—it changes with the underlying price (gamma) and time (charm), so a software engineer must consider real-time recalculation and efficient data structures for large portfolios.

1. Define the Greeks

Briefly explain that the Greeks measure sensitivity of option prices to various factors: delta (underlying price), gamma (delta), vega (volatility), theta (time), rho (interest rates).

2. Focus on Delta

Define delta as the rate of change of option price with respect to the underlying price, ranging from 0 to 1 for calls and -1 to 0 for puts. Mention that delta also approximates the probability of expiring in-the-money.

3. Portfolio Delta Calculation

Explain that portfolio delta is the sum of deltas of individual positions, each weighted by the number of contracts and the contract multiplier (usually 100 for equity options).

4. Sample Portfolio Example

Construct a simple portfolio: e.g., long 10 call options with delta 0.6, short 5 put options with delta -0.4, and long 100 shares of stock (delta 1 per share). Compute total delta: (10*0.6*100) + (-5*-0.4*100) + (100*1) = 600 + 200 + 100 = 900.

5. Interpret and Discuss

Interpret the total delta: a delta of 900 means the portfolio gains $900 for a $1 increase in the underlying. Discuss implications for hedging and the need for dynamic recalculation.

Key Points to Mention

  • Delta measures the sensitivity of an option's price to a $1 change in the underlying asset.
  • Delta ranges from 0 to 1 for calls and -1 to 0 for puts; it is positive for long calls and negative for long puts.
  • Portfolio delta is the sum of individual position deltas, adjusted for contract size (typically 100 shares per option contract).
  • Delta hedging involves offsetting the portfolio delta to achieve neutrality.
  • Delta changes with the underlying price (gamma) and time to expiration, requiring real-time computation in trading systems.
  • For software engineers, efficient calculation of Greeks for large portfolios involves vectorized operations and incremental updates.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

State the standard linear regression assumptions and explain how you would detect violations of each.

Technical Trade-offsRoot Cause Analysis
Author's notes

Knew the list: linearity, error independence, constant variance, normality of residuals, no perfect multicollinearity.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by listing the five standard assumptions of linear regression (linearity, independence, homoscedasticity, normality of residuals, and no multicollinearity). For each, briefly explain the assumption and then describe common detection methods, such as residual plots, statistical tests, and variance inflation factors. Emphasize that in practice, you would prioritize checking assumptions that most affect your use case and consider robust alternatives if violations are severe.

Pro tip: Mention that while formal tests exist, visual diagnostics (e.g., residual vs. fitted plots) are often more practical and interpretable, especially in large datasets where tests may flag trivial violations. Also, note that some violations (like non-normality) matter less for prediction than for inference.

1. List the assumptions

Clearly state the five key assumptions: linearity, independence of errors, homoscedasticity, normality of errors, and no multicollinearity. Briefly define each in one sentence.

2. Explain detection for linearity and independence

For linearity, suggest plotting residuals vs. fitted values or each predictor; for independence, use Durbin-Watson test or plot residuals vs. order of collection.

3. Explain detection for homoscedasticity and normality

For homoscedasticity, use residual plots or Breusch-Pagan test; for normality, use Q-Q plots, histograms, or Shapiro-Wilk test on residuals.

4. Explain detection for multicollinearity

Compute Variance Inflation Factor (VIF) for each predictor; VIF > 5 or 10 indicates problematic multicollinearity. Also, correlation matrix can help.

5. Discuss implications and remedies

Briefly mention what to do if violations are found: transformations, robust standard errors, removing predictors, or using alternative models. This shows practical understanding.

Key Points to Mention

  • Linearity: residual vs. fitted plot should show no pattern; consider adding polynomial terms if violated.
  • Independence: Durbin-Watson statistic around 2 indicates no autocorrelation; values <1 or >3 suggest issues.
  • Homoscedasticity: Breusch-Pagan test or plot residuals vs. fitted; fan shape indicates heteroscedasticity.
  • Normality: Q-Q plot should follow diagonal; Shapiro-Wilk test for small samples; less critical for large samples due to CLT.
  • Multicollinearity: VIF > 5 or 10; condition index; remove or combine correlated predictors.
  • Practical approach: prioritize assumptions based on goal (prediction vs. inference) and use robust methods when needed.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q3

Solve a short probability or statistics problem presented during the resume discussion.

Algorithms & Data StructuresTechnical Trade-offs
Author's notes

These came interleaved with resume questions which threw me off a bit.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

First, clarify the problem to ensure you understand the scenario and assumptions. Then, outline your solution step-by-step, explaining the reasoning and any formulas used. Finally, compute the answer and briefly discuss its implications or potential edge cases.

Pro tip: Verbalize your thought process clearly and check if the interviewer wants a quick estimate or an exact calculation. If time permits, mention how you would validate the result with a simulation or alternative method.

1. Clarify the problem

Ask questions to confirm the problem statement, assumptions, and what exactly is being asked. Ensure you understand terms like independence, distribution, and sample size.

2. Outline the approach

State the probability or statistical concepts you'll use (e.g., conditional probability, Bayes' theorem, expected value) and why they apply. Sketch a step-by-step plan.

3. Perform calculations

Carry out the math carefully, explaining each step. If numbers are complex, consider simplifying or using approximations, but note that you're doing so.

4. Interpret and sanity-check

Interpret the result in the context of the problem and check if it makes sense (e.g., probability between 0 and 1). Mention any assumptions that could affect the answer.

5. Discuss extensions or applications

If relevant, relate the problem to real-world scenarios or software engineering contexts, such as A/B testing, system reliability, or algorithm analysis.

Key Points to Mention

  • Clearly define events and random variables
  • State assumptions (e.g., independence, identical distribution)
  • Use appropriate formulas (e.g., Bayes' theorem, binomial distribution)
  • Show intermediate steps to demonstrate reasoning
  • Sanity-check the result (e.g., probability bounds, expected value range)
  • Connect to practical applications in software engineering

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q4

Walk through a relevant project on your resume and answer follow-up technical questions tied to it.

Technical Trade-offsRoot Cause Analysis
Author's notes

Standard resume walkthrough but the follow-ups were sharp.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a project that showcases both technical depth and business impact, ideally one involving trade-offs or root cause analysis. Structure your walkthrough using a clear narrative: context, problem, your specific actions, technical decisions, and measurable results. Be prepared to dive deep into any technical detail, explaining your reasoning and alternatives considered.

Pro tip: Proactively mention a trade-off you made and why, then briefly note what you would do differently now. This shows self-awareness and growth, which interviewers at banks like BNP Paribas value highly.

1. Set the Context

Briefly describe the project's purpose, your role, the team size, and the business domain. Keep it concise to leave time for technical depth.

2. Define the Problem

Explain the specific technical challenge or goal, such as performance bottlenecks, scalability issues, or integration complexity. Highlight why it mattered to the business.

3. Detail Your Actions

Walk through the steps you took, focusing on your individual contributions. Describe the technologies used and the rationale behind your choices.

4. Discuss Trade-offs and Root Cause Analysis

Explain any key decisions where you weighed alternatives, and if applicable, how you diagnosed and resolved a critical issue. Show your analytical process.

5. Quantify Results and Reflect

Share measurable outcomes (e.g., reduced latency by 30%, increased throughput). Reflect on lessons learned and how you would improve the solution today.

Key Points to Mention

  • Specific technologies and architectures used (e.g., microservices, databases, cloud services)
  • Trade-offs considered (e.g., consistency vs. availability, performance vs. cost, build vs. buy)
  • Root cause analysis techniques (e.g., 5 Whys, fishbone diagram, log analysis, profiling)
  • Your individual contributions versus team efforts
  • Quantifiable impact on business metrics (e.g., revenue, user experience, operational efficiency)
  • Lessons learned and how you applied them to future projects

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.