RepostedStripe logo

Stripe · Phone screen → Onsite

In process

Stripe New Grad SWE Interviews: 17 Experiences (Part 1 of 2)

Software engineer · New GradBachelor's degreeSep 2026
Shared by

Stripe new grad SWE reports, Feb–Oct 2026: 8 candidates on multipart OAs and screens, Bikemap integration, Mako debugging and offers.

At a glance

Coverage: 8 Stripe engineering candidates (entries 02–06 and 11–13): mostly SWE and SDE new grads, plus one L2 SWE (06). Locations named: AMER and the United States. Report dates February to October 2026; interview dates are labeled where given. Six team-screen reports once numbered here (01, 07–10 and 14) are covered in the Stripe new grad team-screen reports.

In this series

  • Part 1 (current): entries 02–06 and 11–13, the newer timelines from February to October 2026, including two offers.
  • Part 2: entries 16, 18–20 and 23–26 from November 2025 to February 2026 (shipping cost, fraud levels, structured records, an MLE loop), plus one SDE merchant-link report with level not given.

What came up

Almost every report here describes one problem that grows part by part. Counts are out of the 8 reports in this part, and one candidate can sit in several rows.

Topic Reports Last seen
Multipart coding 6 of 8 Oct 2026
Payment, fee and subscription rules 4 of 8 Aug 2026
API and repository integration 3 of 8 Feb 2026
Repository debugging 3 of 8 Feb 2026
AI-assisted coding 1 of 8 Aug 2026
System design 1 of 8 Aug 2026
Behavioral discussion 1 of 8 Feb 2026

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Email Subscription Scheduler 2 Jan 2026
Invoice / Payment Reconciliation 1 Aug 2026 (report date)
Bank transactions (onsite coding) 1 Feb 2026 (report date)
Transaction Fee Calculator, Parts 1–2 1 Jan 2026
Transaction Fee Calculator, Volume Discounts 1 Jan 2026
payment phone problem (3 parts) 1 Dec 2025

AI Coding

Question Reports Last seen
Evaluate Ordered Action Rules 1 Aug 2026 (report date)

Project Coding

Question Reports Last seen
Complete a Bikemap Route and JSON Integration 3 Jan 2026
Mako debugging (practice) 3 Jan 2026

Behavioral (BQ)

Question Reports Last seen
Why Stripe? 1 Feb 2026 (report date)
Where do you see yourself in two years? 1 Feb 2026

8 detailed candidate timelines, loops, and screens

Report 01 (reported October 2026, SWE New Grad, AMER: a team screen with parts left unfinished) is also covered in the Stripe new grad team-screen reports as entry 01.


02: A four-part OA

Report date: October 24, 2026 · Role: SWE New Grad · Result: No offer (overall)

  1. The candidate applied online. The OA was one question in four parts, each harder than the last.
  2. They did not share the task, timer, language, score or later rounds, so the no-offer label does not say how the OA went.

03: A referral that ended in a signed offer

OA report: September 13, 2026 · Updates: October 18 and October 27–28, 2026 · Role: New grad SWE, 2027 start · Location: United States · Result: Offer signed

  1. The candidate applied around September 2–3 with a friend's referral and took the OA on September 4, passing every test case.
  2. The first-round invite came about two and a half weeks after the OA.
  3. The invite from virtual onsite to the hiring-manager round came two days after the onsite. On October 18 they had finished the manager round about a week earlier and were waiting.
  4. On October 27 they reported signing the offer, to start after a May graduation, with a choice of San Francisco or Seattle. No technical question was shared.

04: A team-screen invite after three weeks

Report date: October 28, 2026 · Later posts: October 29–31 · Role: SWE New Grad · Region: AMER · Status: Team screen upcoming

  1. The invite came about three weeks after the OA.
  2. The technical exercise was described to them as 45 minutes.
  3. Their later posts were still about preparing; no screen result, OA question, score or OA date was given.

05: AI-assisted coding and a design round

Report date: August 30, 2026 · Role: Full-time SWE New Grad · Status: Not shared

  1. Two phone rounds: coding and system design.
  2. The coding round used HackerRank's AI assistant for Evaluate Ordered Action Rules. Part one applied rules in order, such as BLOCK if fraud_flag and ACCEPT if trusted_partner; part two added comparisons and AND / OR. Processing stopped at the first rule that matched.
  3. The setup and the assistant's speed were harder for them than the rule logic, and they wondered whether their light use of the AI was enough.
  4. They felt the design round went well. The final outcome was not shared.

06: An L2 reconciliation interview

Report date: August 10, 2026 · Role: L2 SWE · Result: Candidate felt it went well

  1. The candidate finished all three parts of Invoice / Payment Reconciliation.

Report 07 (reported June 2026, SWE New Grad, Canada: a three-part screen, then a rejection) is also covered in the Stripe new grad team-screen reports as entry 02.

Report 08 (reported April 2026, SWE New Grad, United States: four CSV requirements in an online editor) is also covered in the Stripe new grad team-screen reports as entry 03.

Report 09 (reported March 2026, SDE New Grad, India: two questions in 45 minutes) is also covered in the Stripe new grad team-screen reports as entry 04.

Report 10 (reported February 2026, SWE New Grad: a three-part phone screen, then why Stripe) is also covered in the Stripe new grad team-screen reports as entry 05.


11: A payment screen, then bank transactions

Report date: February 10, 2026 · Phone screen: Before Christmas 2025 · Role: Full-time SWE New Grad · Result: Rejected after the onsite

  1. Phone: a payment problem, 3 of 3 parts done.
  2. Virtual onsite: bank-transaction coding 3 of 3, Mako debugging (practice) about 2 of 3, and Bikemap JSON Integration about 3.5 of 5.
  3. A hiring-manager chat followed, and the rejection came about a week later.

12: A 2025 phone screen and a 2026 onsite

Report date: February 20, 2026 · Phone screen: November 18, 2025 · Role: 2026 New Grad SDE · Result: Still waiting

  1. The OA invite came in October 2025. The first interview was rescheduled or missed four times before the phone round on November 18.
  2. The January 20, 2026 virtual onsite had three rounds: two of three parts of Email Subscription Scheduler, about 3.5 parts of Bikemap JSON Integration, and two parts of Mako debugging (practice).
  3. The hiring-manager invite came January 28 and the chat was February 9. About ten working days later there was still no answer.

13: A fee-calculator screen and an offer

Phone screen: January 12, 2026 · Report date: February 14, 2026 · Role: Full-time SDE New Grad · Result: Offer on February 13

  1. The OA came in December 2025.
  2. The phone screen covered Status Gate and Regional Rates, then Merchant Volume Discounts. They did not say how many parts they finished.
  3. The January 28 virtual onsite, in Python: Email Subscription Scheduler 3 of 3, Bikemap integration about 3.5 of 5, and Mako debugging (practice) 2 of 3.
  4. The February 9 hiring-manager round covered their resume, why Stripe and where they saw themselves in two years.

Report 14 (reported February 2026, SWE New Grad, United States: two screen parts, then an offer) is also covered in the Stripe new grad team-screen reports as entry 06.


Patterns across the reports

  1. The same three onsite rounds. Entries 11, 12 and 13 each had a coding round, Bikemap integration (about 3.5 parts in each) and Mako debugging (2 of 3 in 11 and 13, two parts in 12).
  2. Unfinished onsite parts are not always fatal. None of the three reported finishing Bikemap; 13 still got an offer, 11 was rejected and 12 was waiting.
  3. A manager chat closes the loop. Entries 03, 11, 12 and 13 all had a hiring-manager round after the onsite.

Common questions

How long is the Stripe new grad team screen?

Entry 04 was told the exercise was 45 minutes. The Stripe new grad team-screen reports have more timings, from 45 minutes to an hour.

Do you have to finish every part in the Stripe screen?

Not always. In the onsite, entry 13 got an offer without finishing the Bikemap or Mako rounds. For the team screen, see the Stripe new grad team-screen reports: one interviewer said finishing every part was not expected, and one candidate advanced after two parts.

What rounds are in the Stripe new grad virtual onsite?

Coding, an integration round (Bikemap) and a debugging round (Mako), then a hiring-manager chat (entries 11–13).

How long does Stripe take after the OA?

Entry 03 got a first-round invite about two and a half weeks after the OA, and entry 04 about three weeks.

Does Stripe allow AI in the new grad coding round?

One report (05) used HackerRank's AI assistant in a coding round; no other report here mentions it.

Keep practicing

In this series: Part 1 (current) · Part 2

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

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