Q2 Software Interview Questions
& Process

The interview process is exhaustive, here are the rounds: - HackerRank : Consists of 3 dsa questions, along with java fundamental MCQ Questions, Selenium related questions etc. - Tech Rounds : One with Indian panel and one with US Panel : Expect deep dive to your background, dsa questions again here as well. - Culture and tech round : With US Panel - Techno Managerial Round : Basic tech and manegerial questions My personal Experience : All are elimination rounds, all rounds went well, at the end the manager said "You are answering more like a manual QA rather than Automation QA". The irony is all the previous rounds were only based on automation and coding and tech architecture. Don't bother giving interviews here because if the manager doesn't like you in the 20-30 mins then even though you are the strongest techie, you wont be selected. Dont know what precedent they are setting by hiring such managers in India.

The interview process started off great. The recruiter and engineering manager were transparent and forthcoming about the process and looked forward to next steps with me meeting the team in-person for the final stage of the interview process. Unfortunately, this is where communication stopped. I didn't hear back and received no email about rejection, next steps, etc... I followed up with the recruiter asking about my status and he was shocked I didn't receive the email invitation about next hiring steps. I said this was no problem and understood that these things happen. The recruiter said if it would be ok for them to follow-up with text because of the email problems and I said yes. Then I was ghosted.

This took about 2 months to complete, and I heard back about a week after applying. The process involved 4 rounds: first, I spoke with a recruiter, then the hiring manager, followed by a meeting with two team members, and finally, an interview with an external employee who acted as a 'bar raiser'.

The Q2 Software hiring journey usually kicks off with an online test covering aptitude, coding, and SQL skills. If you do well, you'll have a technical interview diving into Java, SQL, OOPs, and questions about your past projects. After that, there's a round with a manager or functional lead to check out your problem-solving, how you communicate, and how you'd handle real situations. The last step is typically a chat with a director or senior leader about why you want the job, if you'd fit in, and your future plans. For some jobs, there might be a quick HR chat about joining dates and what we expect from you.