I recently interviewed at Bridge, which has since been acquired by Stripe. Sharing my interview experience here.
Coding 1:
You're given a list of objects, each looking something like:
{"key1": 10, "key2": 20}
All values are integers.
You're given a specific key, plus a requirement of MAX or MIN.
You need to find, among the objects in the list that contain this key, the one whose value for that key is the largest (or smallest), and return that object.
The problem itself isn't hard. During the process they discuss some input/edge cases with you, and also ask you to write test code.
Coding 2:
Implement a structure similar to a Java Iterator, mainly implementing:
hasNext()
next()
There's a follow-up after that: add a step parameter.
For example:
[1, 2, 3, 4, 5, 6]
If step = 2, calling next() repeatedly returns:
2, 4, 6
They keep asking about things like the iterator running out, different step values, invalid input, and so on, and ask you to write tests.
System Design:
Pretty standard system design. They discuss:
API design
Database selection
How the data is stored
Overall system architecture
Scalability
The interviewer keeps following up based on your design.
Behavioral:
About 25 minutes, mostly talking about past work experience, projects, how I collaborated with others, plus some behavioral questions. Pretty normal overall.
The final result was a reject.
Overall, my impression is that Bridge/Stripe's coding rounds aren't particularly LeetCode-flavored — the problems themselves aren't hard, they lean more toward practical coding.
Hope this helps anyone interviewing at Bridge later.
Discussion
Loading comments…