Endava 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.

the recruiter screen involved going through the bullet points in the job description line by line, asking if I had experience with them. Specifically, they asked about my experience with JQL. I explained that it's a query language for JIRA, similar to SQL and Python, which I'm experienced with, and that JQL is easily learnable. The recruiter said they needed someone with 'expert JQL skills' and ended the call immediately, saying they would follow up if that changed. It's frustrating when recruiters don't understand the roles they're hiring for, asking only yes/no questions about requirements.

First up was the HR interview, just a chat about my background, why I want this job, and if I fit with the company vibe. Then, a technical interview digging into my coding, problem-solving, automation testing knowledge, OOP, and practical skills with SQL, Selenium, and Python. After that, a casual 'Nice to meet you' chat with someone from the team or a manager to see how I'd fit in, how I communicate, and what their daily grind is like. Finally, the offer interview to go over the details of the job offer, pay, start date, and how the onboarding works.

It started with my resume where I made sure to highlight my backend frameworks, databases, and APIs experience, plus a few projects. A few days after I sent it, I got an email saying they were interested in moving forward. Next up was a technical screening with a recruiter. They asked me about my background, my favorite programming languages (Python and Java are my strongest), and the kinds of databases I've used, such as PostgreSQL and MongoDB. The call was pretty easy, and I felt good about my answers. The recruiter said they'd let me know about the next steps in a few days, and they did.