Endava Software Engineer Interview Questions
& Process

So, my interview journey had three main parts, and it felt pretty fair and organized. First off was an online assessment, which was a mix of MCQs, coding, and SQL. There were like 57 MCQs about tech stuff and general aptitude, then 2 coding problems that were more about just solving things logically, and finally 1 SQL question. The MCQs hit on programming basics and reasoning. The coding parts were easy-ish to medium, just checking if I knew loops, if/else, and basic data structures. The SQL thing was simple, just writing a query. After that, if you passed, you got a technical interview. This one dove into core tech, programming basics, how I approach problems, and questions about my past projects and resume. The interviewer was good, asked clear questions, and it was a good back-and-forth where I could explain my thinking. The last step was the HR interview. This was more chatty, asking about me, my career plans, what I'm good at, what I'm not so good at, and if I'm up for learning new things and changing things up. It was mostly about seeing if I'd fit in and could communicate well.

So, Endava's interview was pretty good overall. The recruiter was nice and got things set up quickly. First, there was an HR chat about my background, what I'm looking for, and why I applied. Then, two engineers talked to me about backend stuff, mainly Java and Spring Boot, and also system design and solving problems. It was tough but fair, and they made it pretty comfortable. The best part was how it felt like a team effort, not just a test. They were cool with talking through different ideas and wanted me to think out loud. They were checking not just what I knew, but how I communicate and handle stress. The last part was about fitting in with the team and hearing more about the projects. Everyone seemed really into their work and talked a lot about the team vibe and getting better.

The interview process with Endava started off pretty well. Ryan from hiring was responsive and got the first rounds set up fast. First up was a technical interview where I had to solve a coding challenge and add some functionality to their existing code. Then, I had a chat with the Head of Australia, which seemed like a good sign. But after that meeting, communication just stopped. No updates came through, and Ryan, who was so quick to reply before, just went silent. It's pretty annoying that a company this size can't even manage to send a simple update, win or lose. The lack of basic politeness and transparency really makes the hiring process look bad. Overall, a super disappointing experience. The technical parts were fine, but the total silence afterwards really left a bad taste. A quick email would have made a huge difference in keeping things professional.