Sr. Software Engineer at BloomBerg
- Difficulty
- Process took
- 2-3 Weeks
- Rounds
- 3
- Format
- Remote
- Applied via
- Company Website
How it went
- I didn’t move forward, the process was incredibly educational. Hopefully, sharing these problems and my approach helps future candidates prepare for similar technical challenges.
What they would tell you
- I didn’t move forward, the process was incredibly educational. Hopefully, sharing these problems and my approach helps future candidates prepare for similar technical challenges.
How to prepare
- Be ready for hard variants of known problems, and practice adapting standard patterns to new constraints.
Round by round
- 1
Coding Round 160 min
Conceptually similar to the Gas Station problem, but more difficult, interviewer asked multiple follow-up questions to test my understanding of the concepts and edge cases
- 2
Coding Round 260 min
This round included two challenging problems Modified Sum of Two Integers
-
Restrictions: Cannot use addition operator, loops, or bitwise operations
-
I used recursion, modulo, and integer division, guided by hints from the interviewer
-
Discussion focused heavily on edge cases, recursion depth, and alternative approaches LFU Cache
-
Implemented a Least Frequently Used cache with O(1) operations for get and put
-
- 3
System Design Round90 min
The final round was a system design
- Problem: Design a web application to support user onboarding, password reset, requests for company information, and IT help requests.
- Key constraints: Highly sensitive financial data, independent deployments, and authenticated/validated requests.
- Discussion points included:
- Database trade-offs: SQL vs NoSQL, ACID vs CAP considerations
- Load balancing and caching strategies
- Blue/green deployments and API gateways
- Cloud vs on-premise deployments
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.