PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/Analytics & Experimentation/Optiver

Design and backtest a trading strategy

Last updated: Mar 29, 2026

Quick Overview

This question evaluates a candidate's ability to design and rigorously evaluate a minute-level mean-reversion trading strategy, encompassing quantitative finance competencies such as signal construction, risk controls, position sizing, transaction-cost modeling, reproducible backtesting, and statistical validation; it belongs to the Analytics & Experimentation category within financial time-series and backtesting. It is commonly asked because it tests both practical implementation skills (reproducible backtests and walk-forward validation) and conceptual understanding (overfitting, data-snooping, and statistical significance testing), requiring a mix of practical application and conceptual statistical reasoning.

  • hard
  • Optiver
  • Analytics & Experimentation
  • Software Engineer

Design and backtest a trading strategy

Company: Optiver

Role: Software Engineer

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Technical Screen

Given minute-level OHLCV data for a single equity over 180 trading days, design and backtest a simple mean-reversion strategy: Specify entry/exit rules, risk controls, position sizing, transaction costs, and slippage; implement a reproducible backtest that outputs PnL, win rate, average trade, max drawdown, volatility, Sharpe ratio, and turnover; perform a hold-out or walk-forward validation to assess robustness; discuss overfitting risks and use an appropriate statistical test (e.g., bootstrap or reality-check) to evaluate whether performance is statistically significant.

Quick Answer: This question evaluates a candidate's ability to design and rigorously evaluate a minute-level mean-reversion trading strategy, encompassing quantitative finance competencies such as signal construction, risk controls, position sizing, transaction-cost modeling, reproducible backtesting, and statistical validation; it belongs to the Analytics & Experimentation category within financial time-series and backtesting. It is commonly asked because it tests both practical implementation skills (reproducible backtests and walk-forward validation) and conceptual understanding (overfitting, data-snooping, and statistical significance testing), requiring a mix of practical application and conceptual statistical reasoning.

Related Interview Questions

  • Simulate return-weighted rebalancing strategy - Optiver (medium)
Optiver logo
Optiver
Aug 13, 2025, 12:00 AM
Software Engineer
Technical Screen
Analytics & Experimentation
6
0

Minute-Level Mean-Reversion Strategy: Design, Backtest, Validation, and Significance

Context

You are given minute-level OHLCV data (open, high, low, close, volume) for a single equity over 180 regular trading days. Assume the data are split-adjusted and cover regular trading hours (no overnight trading).

Task

Design and implement a simple mean-reversion strategy and evaluate it rigorously.

  1. Specify the complete strategy specification:
    • Entry/exit rules based on a mean-reversion signal.
    • Risk controls (e.g., time stop, stop-loss, daily stop, position caps, no-trade windows).
    • Position sizing (e.g., volatility targeting) with explicit formulas/parameters.
    • Transaction costs and slippage model.
  2. Implement a reproducible backtest that outputs at minimum:
    • Total and per-day PnL, win rate, average trade PnL, max drawdown, realized volatility, Sharpe ratio, and turnover.
  3. Perform out-of-sample validation using a hold-out split or walk-forward (rolling) validation. If you tune parameters, do so only on in-sample windows and freeze them for the test windows.
  4. Discuss overfitting risks and apply a suitable statistical test (e.g., bootstrap-based White’s Reality Check or similar) to assess whether performance is statistically significant given data-snooping.

Deliver a clear, step-by-step solution with code or pseudocode, including assumptions and guardrails to avoid look-ahead and survivorship biases.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More Analytics & Experimentation•More Optiver•More Software Engineer•Optiver Software Engineer•Optiver Analytics & Experimentation•Software Engineer Analytics & Experimentation
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.