Stripe SWE Intern AI Coding Round: 10 Experiences

Shared by janebeingjane ·
Company
Stripe
Reports
10 interview reports
Level
Internship
Stages
Onsite

Stripe SWE intern AI coding round, 2026: a 45- or 60-minute session guiding an AI assistant through a multi-part task, from 10 candidate reports.

At a glance

  • Process: a virtual onsite with an AI coding session and a separate API integration interview, then a manager chat (03, 05, 06, 10). The AI session ran 45 minutes (05) or 60 minutes (06, 09), in HackerRank with a built-in agent in two reports (08, 09).
  • Asked recently: a task in three or five parts, often resembling the earlier screen (01, 07, 08), with explaining or reviewing the generated code in 6 of 10 reports. No report published the task itself.
  • Difficulty: candidates 03 and 05 found the AI round the hardest part. Completion varied: 3 of 3 parts (04), 4 of 5 (06), about 1.5 of 3 (02), 1 part (09).
  • Outcomes: 03 had an offer and declined it; 05, 06 and 09 were rejected; the rest were waiting when they posted.

Coverage: Software engineering interns; AI-assisted and AI-enabled programming rounds. Ten candidate accounts published or updated between July and October 2026, including Australia, the United States and Indian recruiting contexts.

What came up

The round is a conversation around working code: candidates described guiding the assistant, explaining its output and keeping up as the task grew.

What the accounts mentioned Reports
Explaining decisions, reviewing generated code or identifying its problems 6 of 10
An AI task described in parts 5 of 10
Testing or edge-case work in the AI round 3 of 10
An explicitly stated 45- or 60-minute AI session 3 of 10
The AI round explicitly taking place in HackerRank 2 of 10
A lengthy prompt or a task longer than the earlier screen 2 of 10

One candidate can appear in several rows. These counts describe what the accounts mentioned; an unmentioned detail may still have been part of the interview.

10 candidate reports

01: A README-based task, without an existing codebase

Completed-loop replies: October 26, 2026. A summer-intern candidate said the task came with a README and resembled the earlier team screen with AI added. They warned about over-engineering and recommended stating requirements directly. A separate post from the same candidate confirmed that they had completed the manager interview and were awaiting the decision.

02: Careful review, about half the AI task completed

Completed-VO update: October 26, 2026; exact interview date unreported. This candidate described proposing their own approach, discussing ambiguity and edge cases, and reviewing generated code while explaining it. They reached about 1.5 of three AI parts, completed all five integration parts and received a manager invitation within a day. Their original October 1 post had been a preparation question; the later update supplied the completed-round account.

03: The AI round felt harder than the other coding

Report date: October 23, 2026 · Location: Cambridge, Massachusetts. This intern described a coding interview, an onsite with coding and AI sessions, then a manager chat. They found the AI session challenging. The review was marked as a declined offer, without a disclosed task or completion count.

04: Three AI parts completed, manager decision pending

Report date: October 20, 2026. The candidate finished three of three AI parts quickly and felt the interviewer was pleased. Integration was shakier: roughly 2.5 of five parts, with an API request problem consuming time and pseudocode offered for the rest. The post asked whether they would reach the manager interview; no final result was supplied.

05: A 45-minute, five-part AI interview

Report date: October 18, 2026 · Context: a BTech internship recruiting process. The AI session followed a separate 45-minute integration interview and a 30-minute break. The candidate said LLM use was unrestricted in their AI session, but they had to explain the choices made during the interaction. They initially underestimated the round and later considered it the hardest. They passed the onsite and eventually updated the post to say they were rejected.

06: Four of five AI tasks, then rejection after the manager chat

Interview date: October 2, 2026 · Report date: October 28, 2026. This candidate described two 60-minute onsite sessions, completing five of five integration parts and four of five parts in an AI-related engineering exercise. They advanced to the final manager conversation. According to the feedback they reported receiving, that conversation was the main reason for the eventual rejection. They did not explain the assistant setup or publish the AI task. In an October 29 reply within the integration discussion, they said Google search was permitted but AI was not.

07: A longer task, with emphasis on prompting and explanation

Report date: October 1, 2026. A different candidate in the October discussion described the AI task as similar to the previous screen but longer. They said the work centered on prompting and explaining generated code. Their later advice was to explain functions at a useful level and use the assistant to create and run tests.

08: HackerRank, AI guidance and code inspection

Completed-VO update: September 18, 2026 · Interview period: September. The candidate described two onsite rounds. The AI session took place entirely in HackerRank and involved guiding the assistant through a task resembling the phone screen while identifying code issues. The other session used a GitHub repository and external APIs. No concrete AI prompt or final outcome was shared.

09: The long specification became the obstacle

Interview period: late May to mid-July 2026 · Location: Sydney. The AI session lasted 60 minutes and used an agent inside HackerRank. The candidate struggled to break down a lengthy specification and finished one part. They later emphasized checking generated code and writing regression tests. The final result was a rejection; their belief that the AI round caused it was their own interpretation.

10: A reasonable feeling about the AI round, with no result yet

Interview period: July 2026 · Report date: July 12 · Location: Australia. This intern completed all three integration tasks, felt reasonably good about the AI coding session and had finished the manager interview. They were waiting for the recruiter to return with a decision. The account did not disclose the AI task or its number of parts.

Common questions

How long is the Stripe intern AI coding round?

45 minutes in report 05 and 60 minutes in reports 06 and 09. Known task sizes were three parts (02, 04) and five parts (05, 06).

Can you use AI in the Stripe integration round?

Not in the reports that say: candidate 09 could use an embedded agent in the AI session but not generative AI in integration, and candidate 06 said Google search was allowed there but AI was not.

What does Stripe look for in the AI coding round?

Candidates said the work centered on prompting and explaining the generated code (07), reviewing it and finding its problems (02, 08), and handling edge cases (02); candidate 06 was told the manager chat, not the AI round, decided their rejection.

Keep practicing

AI coding rounds at other companies

More companies with AI rounds on FastPrep:

Across companies: 2026 AI Coding OAs at 15 Companies: 32 Reported Problems and 2025–2026 AI Coding Phone Screens and Onsites at 43 Companies: 76 Reported Problems.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.