Software Engineer at Halodoc

How it went

What they would tell you

How to prepare

Round by round

1. 1

   Low-Level Design (LLD)120 min

   Problem: Log File Event Notification System The interviewer gave me a scenario where I had to design a log file notification system.

   • The system would process a continuous stream of log data, tagged by Info, Critical, Warning, and Blocker.
   • Users subscribe to specific log types, with a config/database storing subscription details. Each type has a threshold that defines when to send notifications. The key task was to ensure that if a certain number of critical events occurred within a specific duration, users would be notified. After sending the notification, the system would wait for a set period before notifying again. I discussed my approach in detail, focusing on event streams, thresholds, and notification timing.The interviewer was impressed by my structured approach and the solution’s efficiency.
2. 2

   DSA60 min

   This round was a mix of multiple coding questions, testing both my problem-solving and DSA skills. Questions: Min Stack I implemented two approaches,

   • Using two stacks: One for elements and the other for storing the minimum values.

   • Using a stack of pairs: Stack storing both the element and the minimum value at each step. Find Two Repeating Elements (GFG)

   • I started with a brute force approach using HashMap, followed by an XOR-based approach, but I couldn’t complete it due to time constraints. Shuffle Linked List

   • I had to rearrange the linked list in a specific pattern. For example, given a list like 1 -> 2 -> 3 -> 4 -> 5 -> 6, the output should be 1 -> 5 -> 3 -> 6 -> 2 -> 4. I was able to implement the solution successfully. The interviewer asked me to jump between questions, so the round felt a bit hectic. Even with limited time for optimizations, I was happy with my performance and received a hire recommendation.

   • Min-Stack
   • Find Two Repeating Elements
3. 3

   HLD60 min

   This round was about designing a system to solve a real-world problem. The task was to design a web scraper for Amazon products, including a price drop notification trigger for users. Key Discussed Points:

   • Web Scraping Techniques: We talked about using APIs, BeautifulSoup, Puppeteer, or Selenium for scraping data.
   • Database Design: I explained how to track products and user subscriptions efficiently.
   • Scalability: We discussed handling multiple users, dealing with rate limits, and using background processing to manage requests.
   • Notification System: I explained how I’d design the notification system, considering both real-time and batch processing. I was able to design the system and address scalability concerns well. The interviewer seemed satisfied and gave me a hire recommendation.
4. 4

   Hiring Manager60 min

   The final round was more of a general discussion about my current projects and system design experience. The conversation was smooth and non-technical, focused on understanding how I approach teamwork, problem-solving, and technical challenges. The interviewer asked standard HR questions like:

   • Why do you want to join Halodoc?
   • What motivates you in your work?
   • What’s your experience working in teams? The discussion was constructive, and we ended with positive feedback.

   I received an offer from Halodoc, but during the salary negotiations, they offered a lower package than expected, considering my performance in DSA and system design. Despite the offer being lower than anticipated, I was still excited about the role.

What came up