Summary
I interviewed with Mahindra Logistics for an SDE - Java role in Gurgaon, going through three rounds including DSA and two System Design rounds, solving both DSA problems and designing a notification system, but struggling with a ride booking platform design. I was ultimately rejected.
Full Experience
Hi LeetCoders,
This is my interview experience post with the Mahindra Logistics, got rejected!
Company: Mahindra Logistics Location: Gurgaon Role: SDE - Java
How did I get the opportunity? HR approached me directly, via a phone call!
Round 1: DSA Round Interviewer: One year experienced SDE I
Asked two LeetCode medium questions, solved both of them.
Round 2: High Level Design Interviewer: Engineering Manager
Asked some questions related to my work experience and skills, and a few questions on the working of Kafka. Thereafter, asked to design a notification system supporting multiple channels and scaling upto 1M QPS.
Designed a good notification system, supporitng multiple channels using message queue, load balancers etc.
Round 3: High Level Design Interviewer: Head of Engineering
Asked some questions related to my work experience, and a few questions on the architecture of Kafka. Thereafter, asked to design a ride booking platform like Uber which I failed to design properly.
I started with the very basic features thinking that I will make the design evolve to a Uber scale platform (Top-Down Approach). But the interviewer kept forcing for a complete data or DB design (or ER diagram) first (Bottom-Up Approach).
Round 3 wasn't a good interview, not bad even. Got to know that some interviewers prefer bottom-up approach as it helps them judge a candidate in the very first minutes of the interview. Bottom-up is not for begineers, as it requires lots of system and domain knowledge before-hand.
Although I am not looking for a switch, got some interview experience.
Good luck for your upcoming interviews!
Interview Questions (4)
Design a notification system supporting multiple channels and scaling upto 1M QPS.
design a ride booking platform like Uber which I failed to design properly. I started with the very basic features thinking that I will make the design evolve to a Uber scale platform (Top-Down Approach). But the interviewer kept forcing for a complete data or DB design (or ER diagram) first (Bottom-Up Approach).