Stripe's SWE intern posting and recent candidate reports, read together: cohorts, pay, interview rounds, the AI question, return offers and a prep plan.
If you searched "working at Stripe reddit", you probably want four answers before you apply for a software engineering internship: what the job is, what it pays, what the interview looks like, and whether it leads to a full-time offer. Stripe's own posting answers the first two: 12- or 16-week winter or summer cohorts, production work on a real team, and a posted annual US base of $123,500. Reports from new grad and other software engineer candidates answer the third: a multi-part online assessment, then practical rounds (integration, bug squash and, in some 2026 reports, an AI coding round) instead of LeetCode puzzles. On the fourth, Stripe says conversion is selective and not guaranteed.
If this is your first engineering internship search, our step-by-step guide to the software engineer interview process explains the rounds most employers use and how intern loops differ from experienced-hire loops.
What Stripe's posting and careers pages say
The US posting, "Software Engineer, Intern (Summer or Winter)", was live on Stripe's careers site in October 2026. The useful details are spread across the description and the application form:
- Question — What Stripe says
- Length and timing — Cohorts of 12 or 16 weeks: Winter (January to April) or Summer (May to September). Summer start dates are shared closer to the program.
- Where — San Francisco, Seattle or New York for the US posting. Separate intern postings exist for Toronto, Dublin, London, Bucharest, Singapore and Bengaluru, plus a Summer 2027 high school SWE internship in Seattle and San Francisco.
- The work — "Operate as a real member of the team you join," write software "used in production", and give and receive code review. Recent projects named include fraud controls, safer payouts and checkout setup.
- Languages — "We work mostly in Ruby, Java, Javascript, Go, and Scala," and Stripe says new languages can be learned if the fundamentals are there.
- AI tools — A minimum requirement: the ability to use AI tools to speed up development while reviewing and validating everything they produce.
- Pay — "The annual US base salary range for this role is $123,500 - $123,500." Other benefits "may include" equity, 401(k), medical, dental and vision.
- Office — Most office-assigned Stripes are expected in the office, or with users, at least 50% of each month; some teams require more.
- Return offer — Interns are held to the same bar as every Stripe; offers depend on performance and business need, and conversion is "selective".
Two notes on that table. First, the pay line is a single annual figure. If it is prorated over a 12-week cohort, it comes to roughly $28,500 before tax, but the posting does not explain how intern pay is prorated or mention housing, so confirm both with your recruiter. Second, the posting says plainly that "our internship program is competitive and the expectations are high." Stripe is not describing a rotation program with a toy project. You join a team, ship to production and are judged on it.
The application form is worth reading before you fill it in. SAT or ACT score, GPA and transcript are all optional fields, although Stripe's emerging talent page says GPA is considered. Beyond the usual contact, resume and work-authorization fields, the form also requires your cohort choice (with a separate question on whether you could take the other cohort, which Stripe says "will not negatively impact your application"), three office preferences, and whether you have an active offer deadline from another process. If you have one, say so with the date. Interview scheduling for internships "typically aligns with local academic calendars," and Stripe recommends applying "as early as possible".
The interview, as candidates report it
Public write-ups specific to the Stripe SWE intern loop are scarce. The detailed 2026 reports on PracHub and Simplify come from new grad and other software engineer candidates, so treat them as the closest evidence and ask your recruiter which rounds your loop includes. Across those reports, the order is consistent:
- Stage — What candidates describe
- Online assessment — One long, multi-part problem. Simplify describes a 60-minute task parsing transaction logs; an October 2026 PracHub report describes a four-part "split tender" problem charging gift cards before a credit card, then adding expiry dates, ZIP-code surcharges and refunds as store credit.
- Technical screen — interviewing.io says Stripe does not ask LeetCode questions and that on the phone screen you can use whatever tool you are most comfortable with.
- Virtual onsite — Integration (build against an API from its docs; PracHub reports name a bike-map task and payment reconciliation), bug squash (find bugs in an unfamiliar open-source repo, such as the Python libraries Requests or Mako), and in at least two 2026 reports an AI coding round.
- Hiring manager / behavioral — Judged against Stripe's operating principles. Simplify describes a candidate who passed the coding rounds and was rejected here after answering without Stripe-specific preparation.
Timelines vary. One referred new grad on PracHub received the online assessment on September 4 and a decision on October 15. Simplify's documented new grad timeline ran from a September assessment to a December onsite, with weeks of silence between stages, and notes that silence did not always mean rejection.
What this means for preparation: none of these rounds rewards a memorised algorithm. Each one hands you realistic, incomplete material (a long spec, someone else's code, an API's docs) and watches how you work through it. Aced, a prep site, says ending the general coding round with working code is the strongest signal you can give and that a clear diagnosis often counts for more than a finished fix in bug bash. That shifts practice time away from puzzle lists and towards reading.
The AI question: the sources disagree
This is where the public record is most confusing, and it matters for how you practise.
- interviewing.io states that AI use in Stripe interviews is strictly prohibited.
- Aced says the integration round allows docs and web search but not AI coding assistants.
- At least two 2026 PracHub reports list an "AI Coding" round. In one, the candidate used a Claude Opus model and talked the interviewer through the work, but said they struggled to follow the AI-written code; the recruiter's feedback later pointed to the debug and integration rounds instead.
- The intern posting itself makes AI fluency a minimum requirement, with the condition that you review and validate the output.
One reading that fits all four is that AI is allowed only in a round built for it, but that is an inference: the reports are unverified and none is from an intern loop. Practical answer: ask your recruiter which rounds, if any, allow AI, and practise for both cases. Do the assessment, bug squash and integration drills with no AI at all. Separately, practise building something small with an AI assistant while explaining every line it writes, because the one detailed report suggests the weak point is code you cannot explain.
What working there looks like, from public evidence
Public, first-hand accounts from Stripe interns are thin, so here is what can be sourced:
- Stripe's description of itself. The culture page lists six operating principles (users first, craft, urgency and focus, egoless collaboration, curiosity, and talent) and says "you'll work outside your domain." It also notes that "most Stripes don't come from finance," which is useful if payments is new to you.
- Support. The emerging talent page says early career hires get a manager accountable for their development and a mentor, plus an annual education stipend.
- One intern's review. A former Stripe SWE intern in Seattle, reviewing on Taro in November 2025, rated the internship 4.0 and named ownership of projects and good amenities as pros, with the caveat that work-life balance "can be team dependent; not every intern had the same experience." That is one review, not a pattern, but team variation is the right thing to ask about in your team-matching or hiring manager conversation.
- The expectation of independence. interviewing.io describes Stripe as giving people wide freedom but expecting delivery, and says it is "not for everyone": people who want rigid structure and explicit instructions may not thrive.
If the intern-specific gap bothers you, ask your recruiter to connect you with a current or former intern on the team you are matched with. It is a reasonable request, and their answer will tell you more than any forum thread.
What to do now
A four-week plan, built from the rounds above:
- This week: apply and set up. Apply early, name any offer deadline on the form, and choose one interview language you are fast in. Python is a reasonable choice: the bug squash repos named in these reports are mostly Python libraries, with a Java option. Draft a 60-second answer to "why Stripe" tied to one operating principle and something you built.
- Week 1-2: the multi-part format. Solve one long, multi-part problem a day against a timer: read every visible part before coding, store money as integer cents, and run the given examples after each part. Rigid code written fast for part one tends to cost you later parts.
- Week 2-3: integration and bug squash. Write a script against a public API that paginates, retries on failure and sends an idempotent POST (Stripe's API docs are a good model). Then clone an open-source Python library you have never read and fix an open issue in 45 minutes. Test your editor and debugger before the real interview: one PracHub candidate lost about 15 minutes to a debugger that would not start, and called that round the one that sank them.
- Week 3-4: behavioral. Write four to six true stories covering impact, a mistake, a disagreement and learning something unfamiliar, and say them aloud until each runs about two minutes.
For the behavioral rehearsal, Verve's AI mock interview has an AI recruiter ask questions from a question bank you choose, and gives you a scored report afterwards. For the full round-by-round question list, see our guide to Stripe interview questions; for the recruiter call, our HR screening questions; and to prepare your own questions for the hiring manager, the questions-to-ask generator.
Sources
- US SWE intern posting (cohorts, locations, responsibilities, recent projects, languages, AI tools requirement, "competitive and the expectations are high", $123,500 annual US base, benefits, 50% in-office expectation), opened 2026-10-22: https://stripe.com/careers/listing/software-engineer-intern-summer-or-winter/8128745
- Same posting's application form (12 or 16 week Winter/Summer cohorts, second-cohort question, three location preferences, required offer-deadline question, optional SAT/ACT, GPA and transcript, cover letter optional), opened 2026-10-22: https://boards-api.greenhouse.io/v1/boards/stripe/jobs/8128745?questions=true
- Stripe's other intern postings by location (Toronto, Dublin, London, Bucharest, Singapore, Bengaluru) and the Summer 2027 high school SWE internship in Seattle and San Francisco, opened 2026-10-22: https://boards-api.greenhouse.io/v1/boards/stripe/jobs
- Emerging talent page (interns mostly in engineering, scheduling aligned with academic calendars, apply early, GPA considered, manager and mentor, education stipend, conversion "selective" and not guaranteed, same bar): https://stripe.com/careers/emerging-talent
- Operating principles, "you'll work outside your domain", "most Stripes don't come from finance": https://stripe.com/jobs/culture
- Not LeetCode-style, choice of tool, bug bash, integrations, behavioral against operating principles, AI "strictly prohibited", freedom with expected delivery, "not for everyone": https://interviewing.io/stripe-interview-questions
- Working code as strongest signal, diagnosis over fix in bug bash, integration allows docs and web search but not AI coding assistants: https://www.aced.io/guides/stripe-software-engineer-interview
- New grad 2027 loop (60-minute log-parsing assessment, reconciliation with pagination and idempotency, hiring manager rejection, September to December timeline, silence not always rejection): https://simplify.jobs/blog/stripe-new-grad-swe-job
- Split tender online assessment (gift cards, expiry, ZIP surcharges, refunds as store credit, integer cents): https://prachub.com/interview-experiences/stripe-new-grad-software-engineer-interview-experience-four-part-split-tender-online-assessment
- Referred new grad timeline (OA September 4, rejection October 15), AI Coding round, Bikemap and Payment Reconciliation integration, Mako, Requests and Colander bug squash: https://prachub.com/interview-experiences/stripe-new-grad-software-engineer-interview-experience-passed-the-tech-screen-rejected-after-the-vo-ai-coding-integration-bugsquash
- AI Coding round with a Claude (Opus) model, difficulty following AI-written code, debugger that would not run (about 15 minutes), debug and integration cited in the rejection: https://prachub.com/interview-experiences/stripe-software-engineer-interview-experience-ai-coding-reconciliation-and-a-debugger-that-would-not-run
- Stripe intern review (Seattle, November 2025, 4.0, "team dependent"): https://www.jointaro.com/interviews/companies/stripe/work-experiences/software-engineerinternship-seattle-wa-november-4-2025-4-da46e391/
- Verve mock interview (AI recruiter, question banks including custom questions, scored report): https://docs.vervecopilot.com/features/mock-interview
Ryan
CEO of Verve AI









