
Halodoc Test Automation Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Halodoc.
Lead Software Development Engineer in Test
It's 5 to 6 rounds of interview. First round is domain, then coding round where candidate has to design a framework in 2 hrs, then DSPS round ( leet code medium), then hiring manager round and HR discussion
- Design Backend framework for open source project
Software Development Engineer in Test
Worst interview experience. If you value your time, avoid this company. They aren't really interviewing; they seem to be using candidates to learn about framework development. I was asked to build a framework within a two-hour window. I managed to complete it just a bit over the time limit. During the development, two interviewers repeatedly checked on my progress. Once finished, they wanted me to test it on a device. Following that, they inquired about the framework's flow. Then, a Java question was posed. I suspect the interviewer lacks expertise in framework development and is still learning, as they were looking up basic information on their laptop during the process. It felt like they had no intention of hiring, regardless of a candidate's skill, and were primarily focused on learning from the developed framework. My suggestion is to hire a freelancer for framework development and stop wasting candidates' time. Get a life.
- Can you walk me through the design and execution flow of the framework you built?
- Given two hours, can you create a framework?
- Please execute the developed framework on a physical device.
Software Development Engineer in Test
A recruitment agency got in touch with me for this company and that's how the process began. They arranged for a face-to-face interview. The first round involved building an automation framework and automating a scenario, all within a 2-hour timeframe. They kept checking in to see if I was done. I managed to build the framework and presented it. They seemed really impressed with it and asked me to send it over. Following that, in the second round, I was asked some programming questions and had to explain the program's execution flow. That went smoothly. Then, the HR person came and mentioned they'd update me later, which they never did. Even if the outcome was unfavorable for them (though it seemed unlikely given their reaction to the framework), they should have at least communicated. It felt like their intention wasn't to hire anyone, but rather to collect sample frameworks from all candidates and not actually hire.
- Can you merge and sort two arrays, one of size x and another of size x+y, and optimize your solution?
Halodoc Test Automation Engineer Interview Questions
Quoted word for word from Halodoc interview reports.
“What status code should be returned if the requested resource is not authorized?”
Read reports →“What are HTTP verbs and how are they used?”
Read reports →“How do you remove duplicate IDs in a column using SQL?”
Read reports →“Can you explain Java's finalize() method and the garbage collector?”
Read reports →“What is throughput and how can it be controlled in performance testing?”
Read report →“Can you write code for a binary tree to check if all parent nodes are less than their child nodes?”
Read report →“How would you perform addition in reverse fashion using a linked list, handling edge cases like different input lengths and final carry?”
Read report →“What are the possible test scenarios for a Payment API Endpoint?”
Read report →“Can you merge and sort two arrays, one of size x and another of size x+y, and optimize your solution?”
Read report →Formats, difficulty and experience
Across all 19 Halodoc interview reports.