I was given a boilerplate codebase containing an implementation of a certain classes. The task was to extend it to compute and display the following metrics within a given timestamp range, based on existing event data:
All test cases had to be passed, and the solution was expected to be extensible for future metrics such as p90 latency.
The focus was on clean design, correctness, and extensibility rather than just making the tests pass.
The system design problem was similar to designing an InDrive-like platform, with one key difference:
We discussed core components such as driver discovery, pricing flow, matching logic, and scalability considerations.
Round 3: HR / Final Outcome
The feedback from the technical rounds was positive, and I was expecting the process to move forward. However, the HR round was never scheduled and later informed that hiring requirement is closed now.
Also later, I've been reach-out by different HR for the same role but ghosted again.
Overall, the interview rounds were interesting and well-designed, but the post-interview communication experience was disappointing.
Hope this helps others preparing for CRED interviews.