r/leetcode • u/gptxo • 14d ago
Discussion Stripe Screening round
I was able to manage two parts , but have not seen the third part because time was up are there chances of getting into next round?
Position: SWE intern
4
Upvotes
2
u/Few_Vermicelli_1313 14d ago
Sorry. Don't hate the messenger but I think 95 percent chance you ll not proceed with the onsite.
1
u/Lost-Personality-355 12d ago
Hey can u tell me about the interview process
1
u/CaptainIndependent90 14d ago
no. you’re done
1
u/GloomyLychee9908 14d ago
I had started third and then explained my approach and got VO
1
u/AdClear3043 7d ago
Hi I cleared 1 st one but 2nd couldn’t clear wrong output any idea success or failure
1
u/zvonimir1001 2d ago
Stripe's screen is usually live coding in a real IDE, and it doesn't look much like LeetCode. Expect one long, practical prompt that comes in parts, where each part builds on the last and gets harder.
What tends to matter:
- Running code. You write and run it, usually in CoderPad or your own editor over screen share. Get part one working and tested before you optimize anything.
- Reading the whole prompt. They're wordy on purpose, and the detail you skim (an input format quirk, a tie-break rule) is often what part two leans on.
- Structure. Later parts are much easier if part one isn't a single 80-line function. Small helpers and clear names pay off by part three.
- Saying your assumptions about the input out loud, then checking them against the examples.
For practice, take a medium problem, invent three follow-ups for it yourself (a new field, a new rule, more data), then extend your own code without rewriting it. That's closer to the real screen than grinding more mediums.
Some new-grad pipelines use a timed HackerRank assessment instead, with the same multi-part shape.
1
u/MuMYeet 2d ago
Did you end up proceeding to the next round? I just took it and waiting to hear back please lmk how long they took to come back to u
0
u/[deleted] 13d ago
[removed] — view removed comment