Stripe's AI programming exercise: what candidates report
Stripe's onsite now includes an "AI programming exercise": a multi-part problem in HackerRank with an AI assistant built in. Stripe hasn't published a description of the round, so this guide is built from candidate reports. We note where they agree and where they don't.
What Stripe says officially
Nothing specific, as of 1 November 2026. We searched stripe.com and found no page describing an AI round in Stripe's engineering interviews. Treat every detail below as reported, not confirmed.
The format candidates describe
A widely shared June 2026 post on r/leetcode summed up reports from several candidates:
- It runs in HackerRank with a built-in AI chat, described as "kind of like a lightweight Cursor". It can read the README, propose a plan, write code, add tests and debug.
- The problem has several parts. A detailed README sets out the spec. Early parts are straightforward, and later parts add more complex logic on top of earlier ones.
- Time is tight. The coding portion was reported as about 30 minutes, so writing everything by hand may not finish.
- The AI isn't reliable. Candidates said it can over-engineer, miss edge cases or assume things that aren't in the README.
A second candidate who took both Stripe's and Meta's AI rounds described the same setup: AI models provided inside HackerRank and a harder problem than a classic round (r/leetcode). The model on offer may not be the one you use every day. A candidate at another company that used HackerRank's AI interview said the plan mode was slow and the interviewer suggested agent mode instead.
What seems to be scored
The reports agree that the round tests whether you can use AI "without turning your brain off":
- understanding the spec yourself before the AI writes code
- reviewing the plan and the generated code, not just running it
- writing your own tests and edge cases
- explaining your reasoning under time pressure
The top reply put it as treating the AI "like a junior dev they need to manage, not like a magic wand".
The other practical rounds
Candidates also describe two other hands-on rounds at Stripe, and some intern loops pair the AI exercise with one of them (r/interviews):
- Bug Bash, also called Bug Squash. Find and fix bugs in an existing codebase. Several replies said you may have to work out the test command yourself, for example from package.json.
- Integration. Build against an API inside an existing project.
How to prepare
- Read specs fast. Take a long README and turn it into a checklist in five minutes. Then ask an AI to summarise it and compare against your list.
- Plan for later parts. Each part builds on the last, so keep the code easy to extend rather than hard-coding part one.
- Test each part before moving on. Write a few of your own cases for the edges the README mentions.
- Review every diff. Look for assumptions the README doesn't support. That's the failure candidates report most.
- For Bug Bash, practice finding the test command, then fix one failing path at a time and narrate your reasoning.
- Try a different model. Practice with an assistant you don't normally use, so the interview isn't the first time.
See also how to use the AI without hurting your score and which companies allow AI.
Sources
- r/leetcode: Stripe's new AI programming exercise interview (June 2026, summary of candidate reports)
- r/leetcode: Stripe and Meta new AI interview experience (July 2026)
- r/interviews: Stripe SWE interview prep: Bug Bash, Integration and AI rounds (June 2026)