Reposted
Stripe · Phone screen → Onsite
In processStripe Seattle SWE Intern Logs, Limiter, Bikemap: 1 Experience
Software engineer · InternshipOct 2021
Shared by
Stripe Seattle 2022 SWE intern, October 2021: server-log shutdown screen, a five-calls-in-two-seconds rate limiter, and Bikemap; waitlisted.
At a glance
- Process (2021, see History): phone screen October 11 → onsite October 21 → waitlist November 1 (H01).
- Practise first: Server Shutdown Penalty and the customer-name rate limiter.
Coverage: one Stripe 2022 software engineering intern candidate in Seattle; October 2021. It is more than three years old, so it sits in History.
History (before Nov 2023)
H01: Shutdowns, rate limits and Bikemap
Interview dates: October 11–21, 2021 · Role: 2022 Software Engineering Intern, Seattle · Result: waitlisted November 1
- Phone screen: score a proposed shutdown time (shutdown penalty), find the best shutdown time, and process valid
BEGIN/ENDblocks (log extraction). - Onsite coding: a customer-name rate limiter using the system clock, allowing five calls in two seconds; tests written and run, no concurrency follow-up.
- Integration: Bikemap: parse JSON, make an HTTP request and return an image; three of five parts done.
Common questions
What is the Stripe intern rate limiter?
Report H01: allow five calls per customer name in two seconds using the system clock.
Keep practicing
- customer-name rate limiter and Bikemap: the onsite tasks from report H01.
- Stripe coding question bank and Stripe project coding question bank (sign-in needed).
- Stripe interview guide and Stripe hiring insights: stages, practice problems and recent hiring signals.
- Experience feed: more interview reports from other companies and roles.
Sources: Anywhere useful interview info can be found.
0 total reactions. Your reactions: none.
0 comments
Comments
0No comments yet — be the first to share what you know.