Stripe interview questions

Showing 31–60 of 139 results

• Debug an HTTP Client That Hangs After a 307 Redirect With a Streamed Request BodyHard

  A debugging exercise on the Python HTTP library Requests: a POST whose body is a file-like stream hangs until it times out after the server answers 307 Temporary Redirect. It tests redirect semantics, Content-Length framing, how a stream behaves when a request is resent, and regression testing of the fix.

  StripeSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
• Debug wrong DOM attributes in unknown frameworkMedium

  This question evaluates a candidate's ability to debug frontend DOM attribute mismatches by understanding framework-specific attribute/prop reflection, template/JSX compilation, SSR/hydration differences, and build-toolchain interactions.

  StripeSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
• Describe adapting quickly to unfamiliar problemsMedium

  This question evaluates adaptability, rapid learning, prioritization, communication, and leadership under pressure as behavioral competencies in a software engineering context, and is categorized under Behavioral & Leadership.

  StripeSoftware EngineerBehavioral & LeadershipTechnical Screen
• Design a Count-Metrics Monitoring PlatformMedium

  Design a scalable count-metrics monitoring and alerting platform capable of tracking real-time event counts and rates, grouping by dimensional labels, handling duplicate/late events, and enforcing cardinality limits.

  StripeSoftware EngineerSystem DesignOnsite
• Design a Distributed Metrics CounterHard

  This question tests the ability to architect a highly available, scalable system for ingesting and aggregating high-throughput telemetry data while managing trade-offs between consistency and performance.

  StripeSoftware EngineerSystem DesignOnsite
• Design a Feature Flag Service with Percentage Rollouts and Allow/Block ListsHard

  System design question: design a feature flag service, similar in spirit to Amazon's Weblab, that lets teams turn features on or off, roll them out to a percentage of users, and force them on or off with allow and block lists. It probes where flag checks run, how users are assigned consistently, and how changes reach every service safely.

  StripeSoftware EngineerSystem DesignTechnical Screen
• Design a Fixed-Position Payment Command State MachineHard

  Design a fixed-position payment-command parser and state machine while preserving empty fields and clarifying approval, capture, cancellation, and retry semantics.

  StripeSoftware EngineerSoftware Engineering FundamentalsOnline Assessment
• Design a Merchant Ledger ServiceMedium

  This question tests your ability to design a distributed ledger system that ensures high transactional integrity, strict consistency for financial balances, and reliable idempotency in a high-concurrency environment.

  StripeSoftware EngineerSystem DesignOnsite
• Design a Scalable Idempotent Ledger ServiceMedium

  Design a high-throughput, fault-tolerant double-entry ledger service featuring immutable postings, strict write idempotency, and tunable balance freshness.

  StripeSoftware EngineerSystem DesignTechnical Screen
• Design a String-Rule Validator for Transaction RecordsMedium

  Specify transaction validation rules, parse them safely, evaluate name restrictions, and distinguish malformed input from ordinary rule rejection.

  StripeSoftware EngineerSoftware Engineering FundamentalsOnsite
• Design a Superhero Dispatch SystemMedium

  This question evaluates a candidate's ability to design reliable, distributed backend systems with emphasis on transactional correctness, concurrency control for single-winner acceptance races, geo-spatial querying for proximity matching, eventing/notification pipelines, and operational observability for mission-critical dispatch.

  StripeSoftware EngineerSystem DesignOnsite
• Design a leak-free time-split modelHard

  This question evaluates a Data Scientist's competency in time-aware predictive modeling, including label leakage prevention for late-arriving events, temporal cross-validation, feature engineering, model selection (logistic regression vs gradient-boosted trees), calibration and thresholding for costed actions.

  StripeData ScientistMachine LearningTechnical Screen
• Design a local activity counter serviceHard

  This question evaluates a candidate's skills in designing large-scale distributed systems, focusing on near-real-time ingestion and aggregation, idempotency/deduplication, time-windowed (tumbling and sliding) analytics, hot-key sharding, storage and backfill strategies, and operational concerns including monitoring and privacy.

  StripeSoftware EngineerSystem DesignTechnical Screen
• Design a model for subscription adoption predictionHard

  This question evaluates a candidate's ability to design and productionize a supervised machine-learning pipeline for predicting subscription adoption, testing competencies in labeling strategy, leakage identification and prevention, feature engineering from transactional and merchant metadata, model selection and calibration, evaluation with time-based validation, and post-deployment monitoring. It is commonly asked in the Machine Learning domain for Data Scientist roles because it assesses practical application and production-ready design along with conceptual understanding of time-based splits, class imbalance, performance metrics, and drift detection.

  StripeData ScientistMachine LearningOnline Assessment
• Design a subscription email scheduler with changes and renewalsMedium

  This question evaluates event-driven scheduling, deterministic time-based ordering, stateful account updates for plan changes and renewals, and algorithmic merging of notification streams in the Coding & Algorithms domain.

  StripeSoftware EngineerCoding & AlgorithmsTechnical Screen
• Design a target‑user prediction systemHard

  This question evaluates skills in temporal label definition and leakage prevention, time‑bounded feature engineering (recency/frequency and content affinity), uplift and incremental effect estimation, model selection under class imbalance and budgeted outreach, offline metric design, calibration, fairness constraints, and production validation and monitoring. Common in Machine Learning/Data Science interviews, it is asked to gauge both conceptual understanding of causal and validation issues and practical application skills for deploying a ranked outreach model under capacity constraints, including appropriate cross‑validation and thresholding to map predictive scores to business outcomes.

  StripeData ScientistMachine LearningTechnical Screen
• Design an Idempotent Double-Entry LedgerMedium

  Design a highly reliable, idempotent double-entry ledger system that guarantees strict consistency, append-only immutability, and supports high-concurrency writes on hot accounts.

  StripeSoftware EngineerSystem DesignTechnical Screen
• Design an idempotent SQL ETL for late dataMedium

  This question evaluates practical skills in idempotent ETL design, deduplication by natural keys, handling late-arriving and out-of-order records, upsert/merge strategies, and SQL-based aggregation for daily metrics.

  StripeData ScientistData Manipulation (SQL/Python)Technical Screen
• Design and power an A/B testHard

  This question evaluates a data scientist's competency in experimentation design, including metrics selection and guardrails, statistical power and sample-size calculation, sequential monitoring and ramp strategies, operational checks for randomization and contamination, and choosing credible quasi-experimental alternatives.

  StripeData ScientistAnalytics & ExperimentationTechnical Screen
• Design ledger and bikemap integrationHard

  This question evaluates competency in designing strongly consistent financial ledgers and integrating an external routing service, testing data modeling, distributed transactions, linearizability and idempotency, scalability, security, API design, and observability in the System Design domain.

  StripeSoftware EngineerSystem DesignOnsite
• Design metrics and write SQL for a caseMedium

  This question evaluates the ability to define time‑bounded, attributable conversion metrics and to implement joins, aggregations, and diagnostic checks in SQL to measure marketing outreach impact.

  StripeData ScientistData Manipulation (SQL/Python)Technical Screen
• Design payment fraud detectionMedium

  This question evaluates a candidate's ability to design end-to-end machine learning systems for payment fraud detection, covering competencies in labeling, imbalanced learning, feature engineering across users/merchants/cards/devices/IPs and graph relationships, model selection, online serving, latency and feature freshness, monitoring, experimentation, and adversarial robustness. As an ML System Design problem for a Machine Learning Engineer role, it is commonly asked to probe trade-offs between fraud loss, false positives, user friction and latency and requires both conceptual understanding and practical application of production ML concerns such as evaluation metrics, thresholding, retraining, and operational constraints.

  StripeMachine Learning EngineerML System DesignTechnical Screen
• Design payment-to-invoice matcher with prioritiesMedium

  This question evaluates parsing and data modeling skills, deterministic matching algorithms with prioritization and tie-breaking, handling monetary values as integer cents, and the ability to design comprehensive test suites for edge cases.

  StripeSoftware EngineerData Manipulation (SQL/Python)Technical Screen
• Discuss challenging project examplesMedium

  Discuss challenging project examples evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

  StripeSoftware EngineerBehavioral & LeadershipOnsite
• Discuss compensation expectations and flexibilityMedium

  This Behavioral & Leadership interview question evaluates communication, negotiation, and compensation self-awareness for a Software Engineer by requesting a detailed breakdown of base salary, bonus, equity and benefits.

  StripeSoftware EngineerBehavioral & LeadershipHR Screen
• Discuss mentorship experience and outcomesMedium

  This question evaluates mentorship, leadership, coaching, and impact-measurement skills in a software engineering context, focusing on quantifying mentee outcomes, managing scope across experience levels, and articulating lessons from challenging cases.

  StripeSoftware EngineerBehavioral & LeadershipHR Screen
• Discuss self-intro, location, pay, motivationMedium

  This Stripe Software Engineer technical-screen question covers the opening conversation: a 60–90 second self-introduction, why-Stripe motivation and alignment, location and remote/time-zone preferences, compensation expectations with rationale, and the questions you should ask about team projects and org stability. It evaluates communication, self-presentation, logistical fit, and compensation transparency rather than coding skill.

  StripeSoftware EngineerBehavioral & LeadershipTechnical Screen
• Draw a Hiking Trail from GeoJSON with Markers and Color BandsMedium

  Parse a hiking trail out of a GeoJSON LineString, build the request payload for a map-snapshot API, save the returned PNG, and add start/finish markers plus alternating-color bands along the route.

  StripeSoftware EngineerSoftware Engineering FundamentalsOnsite
• EV Charger Registry with Haversine Nearest-Station RoutingMedium

  Build an in-memory EV charging station registry with status tracking, a haversine distance function, and nearest-online-station routing with deterministic tie-breaks. Tests clean API design, careful spherical math, and corner-case handling.

  StripeSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
• Evaluate Ordered Accept/Block Transaction Rules with AND, OR and ParenthesesMedium

  A three-part Python exercise, solved with an in-editor AI assistant, that evaluates an ordered list of accept or block rules against a transaction. Conditions grow from string equality to Boolean fields, AND and OR, and parentheses, testing tokenizing quoted values, operator precedence, first-match semantics and careful review of AI-written code.

  StripeSoftware EngineerSoftware Engineering FundamentalsOnsite