Real, anonymous reports from people who interviewed for Software Engineer at YASH Technologies, newest first and distilled into what to expect across the loop.
My interview was on the difficult side and very domain-focused. SAP was the domain, and ABAP was the key skill area, so the questions weren’t just generic coding—they were tied closely to how SAP-related work connects to database fundamentals. The questions mostly came from database concepts and SQL.
My process ended up being quick and fairly segmented. I had a first round that I cleared, then I moved into a client round. Before that client-facing round, there was a screening interview that helped filter things in between. The timing stood out to me: the first round was about 30 minutes, the next one was around 15 minutes, and then the client round stretched longer—about an hour.
Candidates typically go through two technical rounds, with the first focusing on basic programming concepts and the second delving deeper into practical applications and problem-solving. Expect questions on core technologies relevant to your experience, such as Java, Spring Boot, and SQL.
Interviews often emphasize domain-specific knowledge, particularly in SAP and ABAP, requiring candidates to demonstrate familiarity with relevant database concepts and SQL. Be prepared for questions that connect technical skills to the specific domain of the role.
After technical assessments, candidates typically face a managerial round that focuses on project experience and problem-solving approaches. This round assesses how well candidates can articulate their past experiences and connect them to the role's requirements.
The interview process is generally structured and segmented, moving from technical screenings to managerial discussions, often with clear timelines and expectations. Candidates appreciate the organized flow, which helps ease the overall experience.
While many candidates report a positive experience with communication during the interview process, some express frustration over delays and lack of feedback post-interview. It’s important to remain proactive in following up if communication seems lacking.
Candidates describe the overall difficulty as average to difficult, with an emphasis on foundational knowledge and practical application. Prepare by reviewing core concepts and real-world applications relevant to the technologies and projects you’ve worked on.