Real, anonymous reports from people who interviewed for Software Engineer at Practo, newest first and distilled into what to expect across the loop.
I went through a selection process that felt challenging and fairly DSA/SQL focused. It ran as three rounds, with an assessment that started things off, then a technical interview, and finally an HR/managerial discussion.
I went through a four-round selection process that started with an aptitude test. The first round was multiple-choice and meant to probe my logical and analytical thinking. After that, I moved to a coding-heavy phase where I had five Java coding questions to work through, and then a short group discussion that was only about half an hour, focused on communication and teamwork.
The interview process typically consists of multiple rounds, often starting with a coding assessment followed by technical interviews focused on data structures, algorithms, and sometimes database design, culminating in an HR discussion. Candidates should expect a structured flow that emphasizes technical skills and problem-solving abilities throughout the rounds.
Interviews heavily emphasize data structures and algorithms (DSA), object-oriented programming (OOP) concepts, and SQL/database knowledge, often requiring candidates to demonstrate a strong grasp of these fundamentals. Candidates should prepare for practical coding questions and theoretical discussions around these core topics.
Initial coding assessments often take place on platforms like HackerRank, featuring standard coding problems that assess logical and analytical thinking. Candidates should be ready to solve problems efficiently while articulating their thought processes clearly.
The HR round typically focuses on cultural fit, communication skills, and personal background, with discussions about compensation and future aspirations. Candidates should be prepared to articulate their experiences and how they align with the company's values.
Candidates often find the interview process challenging, with a high bar set for technical knowledge and problem-solving speed. It's important to maintain a strong understanding of fundamentals and be prepared for a rigorous evaluation of both coding skills and conceptual understanding.
Some candidates reported issues with communication during the interview process, including delays in feedback and follow-up. Candidates should be proactive in seeking updates and may need to be patient as the hiring process unfolds.