Real, anonymous reports from people who interviewed for QA Engineer at Informatica, newest first and distilled into what to expect across the loop.
After an initial screening test, where I faced coding questions, the process moved into a technical interview. That technical stage used a BDD-style framework, and I remember being asked about comparing objects in a program. The whole interview session lasted about an hour. The interviewer’s approach felt decent and the discussion stayed on track, but I didn’t end up getting any feedback afterward, which was the part that lingered.
My interview experience leaned heavily into simpler, test-like questions rather than deep implementation. I went through a short sequence that included logic puzzles and basic SQL/Linux type questions, plus a handful of OOP and data-structure basics. One session also felt very theory-oriented with no real implementation, and the interviewer’s demeanor threw me off—there was a sense of disinterest and that it wasn’t being handled like a serious evaluation. Even though the difficulty was on the easier side, it didn’t feel reassuring. Afterward, there was no meaningful feedback, and that made it hard to feel good about how the process was run.
The interview process typically consists of multiple rounds, including an initial screening, technical interviews focusing on programming fundamentals and problem-solving, followed by managerial and HR discussions. Candidates should prepare for a comprehensive evaluation across these stages, which may span several hours or even multiple days.
Candidates can expect a mix of coding questions, logic puzzles, and theoretical concepts, with varying difficulty levels throughout the technical rounds. It's essential to be prepared for both practical coding tasks and theoretical discussions on topics like OOP, data structures, and database management.
Interviews often include behavioral questions and scenario-based discussions to assess candidates' problem-solving abilities and cultural fit. Candidates should be ready to articulate their experiences and how they handle real-world situations in a team environment.
The difficulty of questions can fluctuate based on candidate responses, making it important to remain adaptable and composed throughout the interview. Candidates should be prepared for both basic and advanced inquiries, as the interviewers may probe deeper based on initial answers.
Candidates often report a lack of feedback after interviews, which can lead to uncertainty about their performance. It's advisable to seek clarification and express interest in receiving feedback to better understand areas for improvement.
The interview process can be lengthy, with candidates experiencing extended wait times between rounds and a potentially drawn-out offer process. It's important to be patient and prepared for a timeline that may take several weeks to complete.