Question 1
Difficulty: medium
Can you walk me through how you would value a plain vanilla interest rate swap and identify the key inputs you would need?
Sample answer
To value a plain vanilla interest rate swap, I would first break it into the two legs: the fixed leg and the floating leg. The value is the present value of each leg’s expected cash flows, discounted using the appropriate curve, usually an OIS discount curve depending on the collateral terms. For the fixed leg, I would calculate the fixed coupon payments using the agreed swap rate and discount them back to today. For the floating leg, I would project future floating payments using the relevant forward curve, then discount those cash flows as well. The swap’s fair value is the difference between the two legs. Key inputs include notional amount, fixed rate, payment schedule, day count convention, reset dates, discount curve, forward curve, and any collateral or credit adjustments if applicable. I’d also check whether the trade has any irregular features, because those can change the valuation method significantly.
Question 2
Difficulty: medium
Describe a time you found a pricing or data issue in a derivatives report. How did you handle it?
Sample answer
In a previous role, I noticed an unexplained movement in the daily P&L for a book with equity options. At first glance, the change seemed consistent with market movement, but the sensitivity breakdown did not line up with the actual price move in the underlying. I went back to the source data and found that one of the volatility surface inputs had not refreshed correctly overnight, so the model was using stale implied volatilities for part of the book. I escalated it to the market data team, documented the impacted positions, and reran the report using the corrected surface. I also checked whether the issue had affected prior days to make sure it was isolated. What I learned from that situation is that strong derivatives analysis is not just about running models, but also about challenging outputs when something looks off. I try to be disciplined about data quality and always trace results back to the inputs.
Question 3
Difficulty: medium
How do delta, gamma, vega, and theta help you understand the risk in an options portfolio?
Sample answer
Delta, gamma, vega, and theta are the core sensitivities I use to understand how an options portfolio may behave under different market conditions. Delta tells me how much the option price should change for a small move in the underlying, so it helps with directional exposure. Gamma shows how quickly that delta itself changes, which matters because a portfolio can become more sensitive as the market moves. Vega measures sensitivity to implied volatility, and that is especially important in options books where volatility can be just as important as direction. Theta tells me the effect of time decay, which is critical because even a profitable position can lose value simply as expiration approaches. In practice, I look at these Greeks together rather than in isolation. A portfolio with low delta can still carry meaningful risk if it has high gamma or vega exposure. That combined view helps me explain risk clearly to traders and control teams.
Question 4
Difficulty: easy
How would you explain a complicated derivatives exposure to a non-technical stakeholder, such as finance or senior management?
Sample answer
I would focus on the business impact first and keep the explanation tied to a few clear drivers. For example, instead of starting with model terminology, I would say whether the position is exposed to interest rates, equity moves, volatility, or time decay, and then explain what kind of market move would increase or reduce value. If the stakeholder needs more detail, I would translate the technical terms into plain language. For instance, I might say, “This book benefits if rates rise modestly, but it becomes more sensitive if rates move sharply,” rather than discussing curve shifts and convexity immediately. I also think it helps to use visuals, simple scenarios, and sensitivity tables, because non-technical audiences usually understand risk better when they can see the impact in dollars. My goal is always to make the exposure understandable enough that decision-makers can act confidently without needing the full model logic in the room.
Question 5
Difficulty: hard
What steps would you take to investigate a large unexplained P&L move in a derivatives book?
Sample answer
I would start by separating the P&L move into the main drivers: market movement, new trades, carry and roll-down, model changes, and any data or booking issues. The first question I ask is whether the move is real or whether it’s driven by an operational issue. Then I would compare the portfolio’s Greeks and market moves against the actual P&L to see if the result is consistent with expected sensitivities. If the move still looks unusual, I’d check pricing inputs, curve construction, volatility surfaces, and any amendments to trade terms. I would also confirm that all trades were booked correctly and that there were no timing mismatches between front office and risk systems. If needed, I would rerun the valuation using independent data or a second source to isolate the problem. The key is to work systematically, document every step, and keep both the trader and control teams informed while the investigation is in progress.
Question 6
Difficulty: medium
Tell me about a time you had to work under tight deadlines to deliver market risk or valuation analysis. How did you stay accurate?
Sample answer
In a previous role, I had to support a month-end close while also responding to several ad hoc valuation queries from trading. The pressure was high because the reporting deadline was fixed, and any mistake would affect both internal numbers and management reporting. I stayed accurate by breaking the work into priorities: first, I completed the core valuation checks that affected the official close; then I handled the ad hoc items in order of impact. I used a checklist for every major report to make sure I did not miss curve updates, trade population changes, or valuation overrides. I also made a habit of reconciling key outputs against the prior day and against independent market data so I could spot anything unusual quickly. When time is limited, I think discipline matters more than speed alone. I prefer to create a clear workflow, communicate early if something may slip, and avoid guessing when the numbers don’t make sense.
Question 7
Difficulty: medium
What is the difference between a forward rate agreement, a future, and an interest rate swap?
Sample answer
A forward rate agreement, or FRA, is an over-the-counter contract where two parties agree on an interest rate for a future period on a notional amount. It settles in cash based on the difference between the agreed rate and the market rate. An interest rate future is similar in the sense that it gives exposure to future interest rates, but it is exchange-traded, standardized, and marked to market daily, which reduces counterparty risk but also introduces margin requirements. An interest rate swap is broader and usually longer dated. In a plain vanilla swap, one party pays fixed and receives floating, or vice versa, over multiple periods. So the FRA is a single-period contract, the future is standardized and exchange-traded, and the swap is a customized OTC agreement with multiple cash flows. Understanding those distinctions matters because the valuation, margining, liquidity, and risk management treatment can all be quite different across the three products.
Question 8
Difficulty: hard
How do you approach model validation or sanity checking for a derivatives pricing model?
Sample answer
I approach model validation by asking whether the model is mathematically sound, market-consistent, and fit for the product it is pricing. First, I review the assumptions: discounting methodology, volatility treatment, correlation inputs, and any simplifications in the payoff structure. Then I test the model against known cases, such as instruments with closed-form solutions or market benchmarks. If a model prices standard instruments reasonably but behaves strangely under small parameter changes, that is a red flag. I also look at sensitivity output to make sure the Greeks move in a logical way. Beyond the mathematics, I check whether the model is appropriate for the desk’s actual trading activity. A model can be elegant and still be a poor fit if it misses features that matter in the market, like early exercise or smile effects. I think the best validation mindset is skeptical but practical: the goal is not just to confirm the model works in theory, but to understand where it may fail in real trading conditions.
Question 9
Difficulty: medium
Describe a situation where you had to challenge a trader, risk manager, or senior colleague about a valuation assumption. How did you handle it?
Sample answer
I once questioned a valuation assumption on a structured option book where the trader wanted to use a more aggressive volatility input than the one supported by the broader market. Rather than framing it as a disagreement, I started by asking what market evidence supported the adjustment and whether the trade had any unique features that justified a premium. I then compared the proposed assumption against recent comparable trades, surface levels, and the desk’s historical methodology. My concern was that the assumption would make the position look better than it really was, which could affect both reporting and risk decisions. I presented the analysis calmly, with supporting data, and suggested an alternative that was more consistent with observed market behavior. The trader did not love the answer initially, but we were able to align on a defensible input. That experience reinforced for me that challenging assumptions is part of the job, as long as you do it respectfully and back it up with evidence.
Question 10
Difficulty: easy
Why do you want to work as a Derivatives Analyst, and what strengths would you bring to the role?
Sample answer
I’m interested in the role because it sits at the intersection of markets, analysis, and precision, which is exactly where I do my best work. Derivatives are complex, but they are also very practical, because the numbers directly affect trading, risk, and financial reporting decisions. I enjoy roles where I can dig into pricing behavior, understand how market variables interact, and turn that into information people can use. My main strengths are analytical rigor, strong attention to detail, and the ability to stay calm when a result does not make sense at first. I also communicate well with both technical and non-technical teams, which I think is important in this role because derivatives analysis often requires coordination across front office, risk, operations, and finance. I try to be proactive rather than reactive, so I’m always looking for data issues, model weaknesses, or process improvements before they become bigger problems. That combination is what I would bring to the team.
