← Back to Dashboard

Stripe Interview Questions

Curated from verified interview reports. Spans Coding, Bug Squash, OA, Integration, and System Design rounds - each question shows how often it was reported and how confident the source match is.

15 real interview questions reported from Stripe Software Engineer interviews (Coding, Bug Squash, OA, System Design, Integration rounds): 10 medium, 5 hard. Each question shows its interview round and how often it was reported, and coding questions come with runnable tests.

Stripe Coding round questions (8)

  • Subscription Email Scheduler - Medium, reported 31×, free preview
    The most-reported Stripe coding question here: build a full send schedule for subscribe/reminder/expired emails from a list of subscriptions and an offset schedule.
  • BitFont Renderer - Medium, reported 10×, free preview
    A frequently reported Stripe coding screen (around 10 sightings): a bitmap-font renderer that lines up glyphs of differing widths and heights next to each other to form a single word bitmap aligned by row.
  • Store Closing-Time Penalty - Medium, reported 1×
    A store-hours reskin of the classic "minimum penalty" sliding-tally problem - pick the closing hour that minimizes lost sales while open and wasted staffing while closed.
  • Shipping Cost Calculator - Medium
    Compute international shipping charges in three layers - a per-country base price, a surcharge for extra weight, and a fragile multiplier that has to come last.
  • Transaction Fee Calculator - Medium, reported 7×
    Read transaction records from a CSV string and add up processing fees whose rates depend on the provider, the status and the region - only settled transactions are charged.
  • Account Balance Manager - Medium, reported 12×
    A variant of "Optimal Account Balancing" - settle every account to zero using the fewest transfers. Stripe explicitly does not require the truly-optimal count, just a working greedy.
  • RBAC Role Resolver - Hard
    Resolve permissions in a multi-tenant RBAC setup where grants flow down an account tree - a DENY found closer in the ancestor chain has to override any ALLOW inherited from farther up.
  • Sliding-Window Rate Limiter - Hard, reported 1×
    Build a rate limiter for an API gateway that counts each client's calls over a sliding window - fixed time buckets are the classic pitfall, since they allow a double-size burst across a bucket boundary.

Stripe Bug Squash round questions (2)

  • [Bug Squash] Redirect With a Consumed Stream - Hard, reported 5×
    A genuine Stripe debugging-round bug ported to TypeScript: when following a 307/308 redirect, the request body stream is sent again without rewinding its cursor, so the second request goes out empty.
  • [Bug Squash] Template Auto-Escape Bypass - Hard, reported 27×
    A reskin of Stripe’s real Mako-engine debug round: a template renderer that is supposed to HTML-escape interpolated values has a bug that leaves one interpolation form unescaped.

Stripe OA round questions (2)

  • Merchant Risk Scoring - Medium, reported 4×
    Stripe’s reported new-grad OA: monitor a live transaction stream per merchant, flag fraud once a per-category threshold is crossed, and correctly reverse a flag on dispute.
  • Card Range Fill - Medium, reported 1×
    Take sorted, non-overlapping card-number ranges that may have holes between them, and stretch each range's upper end so it reaches right up to where the following range starts.

Stripe System Design round questions (1)

  • Fraud Detection ML System - Hard, reported 1×
    Design an end-to-end, real-time fraud-detection ML system: ingestion, features, serving, the block/flag/approve decision flow, and fallbacks when the ML service is unavailable.

Stripe Integration round questions (2)

  • Bike Map - Medium, reported 46×
    The Stripe round reported more often than any other: take coordinate points supplied as JSON and use a real open-source mapping API to join them up and render a route or map.
  • Review Assignment with JGit - Medium, reported 1×
    Diff two branches with JGit, look up each changed file's owner in a CSV ownership mapping, and automatically pick the code reviewer who owns the most changes.