I had two initial rounds for a QA position, each lasting 45 minutes with two interviewers. One round focused solely on discussing my experience and scenario-based questions. The interviewer in this round did not seem very knowledgeable about conducting interviews. The second round was an assessment with an architect who was highly knowledgeable. They asked valid and well-structured questions, appreciated my responses, and made the interview process comfortable. The assessment included coding and technical problem-solving, and I believe it went exceptionally well—I’d rate it 10/10. The discussion round, however, was not as strong, so I would rate it around 7/10. One key takeaway: if you are strong in coding, be mindful not to overemphasize your expertise. The interviewers may not prioritize extensive coding skills for a QA role, as they might perceive it as a sign that you wouldn’t stay long in the position. Recruitment Process: The recruiters were not very responsive to emails, so don’t expect timely replies—if you send an email, be prepared for no response. It’s best to follow up once but not rely on email communication too much.