Scheduling:

Interview was scheduled over the phone, but there was no confirmation, no official emails, and no venue details provided. I had to confirm this on the day of the interview.

Process:

The manager was supposed to show up but didn't for some reason, and you had to wait. To cut to the chase, the test lead came up and started with testing questions, all bookish ones (and expected bookish answers). They asked for your projects and work done but didn't grasp anything even after breaking it down to bits and pieces. Way to lead ;) It was an average round. They failed to explain what the role was about.

Round 2:

This was a technical round about Java and related topics. It felt more like a coaching session than an interview. If you want to learn something totally new that you haven't figured out yet, you need to attend this round. Kudos to the interviewer

HR:

The HR representative beat around the bush with a very vague description of the job profile. They described it as a lead role, but the designation clearly stated engineer, and there was already an existing lead on the team. This seemed fishy to me. It was clear that they didn't have any clear answers to these questions.

Bookish software testing, agile methodologies questions, Java and Selenium questions.