Great — here's a structured overview to help you succeed, especially if you're applying for a QA Engineer, Platform Test Engineer, or similar technical role.
Initial HR/Recruiter Screening
General background
Current/expected salary
Notice period
Job role fit
Technical Rounds (1–3 rounds)
Core testing skills (automation, platform knowledge)
Scripting (Python/Shell, etc.)
Networking basics (TCP/IP, VLANs, etc.)
Hands-on experience with tools (e.g., Jenkins, Git, REST APIs)
Interview questions [1]
Question 1
Initial HR/Recruiter Screening
General background
Current/expected salary
Notice period
Job role fit
Technical Rounds (1–3 rounds)
Core testing skills (automation, platform knowledge)
Scripting (Python/Shell, etc.)
Networking basics (TCP/IP, VLANs, etc.)
Hands-on experience with tools (e.g., Jenkins, Git, REST APIs)
They care about your skills, rather than your background. They have a template which they provide and you got to fill that, everyone is provided a unique number. You are instructed not to disclose any of your personal details in the due course of your interview.
The interview process was two rounds. The first round was a behavioral interview. Straightforward questions, like tell me about the most technically challenging project you have worked on. The second round was a system design interview.
3 technical rounds of 35-45 mins each for a 5 years experience JS fullstack.
1. Project currently working on + design patterns employed and resume based questions in details to check the depth.
2. System design interview - asked me to mention an approach to design a microservice for retail client. Followed up by questions on why I've chosen a particular tech stack and questions on how to tackle certain situations in real word on such services (inventory + payments etc).
3. DS based test - question was bit easy.