Infor logo
InforQA Engineer
Updated Jan 28, 2026

Infor QA Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for QA Engineer at Infor, newest first and distilled into what to expect across the loop.

Get your personalized Infor QA Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
6 months ago
Average Neutral Bengaluru

After a recruiter screening, I ended up going through a multi-round process that felt intentionally structured around both technical competence and fit. The early stage focused on my background and expectations—availability and how I thought about the role—plus some cultural fit and communication. From there I moved into technical interviews where the questions leaned heavily into QA work: testing approach, troubleshooting scenarios, and how I’d handle real-time situations. SQL and automation came up as well, along with manual testing fundamentals and scenario-based discussions.

Across the technical parts, I also had formats that tested more than just recall. There was a written exam that included things like building test cases, and I got puzzle-style questions along the way. In parallel, I was asked to connect the discussion back to my own project experience—what I’d actually done day to day, how I approached defect life cycle thinking, and what I knew about automation. The process then wrapped with an HR-style conversation that centered on communication, attitude, and alignment, sometimes with a managerial/higher-level step depending on how the earlier rounds landed.
> 1 year
Average Negative Taguig

My process took longer than I expected. I went through four total conversations: a recruiter touchpoint, two technical interviews (one of them was in person), and then a final interview. After that, I waited and waited for an update—about 2–3 months passed before anything came back, and by then I’d already accepted another offer.

The conversations themselves were straightforward. The questions didn’t feel like trick traps; they were more about checking whether I could communicate my thinking and connect it to the role. I remember one part feeling like a basic pre-interview question rather than a deep technical grilling. Still, the real strain ended up being the silence afterward. I also followed up once and didn’t get the response I was promised, and the timeline stretched from days to weeks to months.

Unlock every QA Engineer interview experience

Real QA Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Timeline

The interview process typically involves multiple rounds, starting with a recruiter screening followed by technical interviews and a final HR conversation. Candidates reported varying timelines, with some experiencing delays of several weeks to months before receiving feedback.

multi-roundrecruiter screeningtimeline

Technical Assessments

Candidates faced a mix of technical assessments, including written exams and panel interviews that focused on QA fundamentals, troubleshooting scenarios, and practical applications of testing strategies. Questions often required candidates to connect their experience to real-world QA challenges.

technical interviewswritten examQA fundamentals

Behavioral & Cultural Fit

Interviews included discussions on communication, teamwork, and cultural fit, often connecting back to candidates' previous experiences and how they approach their work. This aspect was emphasized in both HR and managerial conversations.

behavioral questionscultural fitcommunication

Diversity of Topics

Candidates reported a broad range of topics covered in interviews, including manual testing, SQL, automation, and software engineering principles. The challenge often lay in managing the breadth of knowledge required across these areas.

manual testingSQLautomation

Interview Atmosphere

The interview environment was generally described as friendly and approachable, with interviewers focused on understanding candidates' thought processes rather than just testing knowledge. This helped create a more comfortable experience for many candidates.

friendly atmosphereapproachablethought process

Outcome & Reflection

Despite a generally positive interview experience, many candidates did not receive offers, leading to reflections on the disconnect between interview quality and final outcomes. Some expressed frustration over the lengthy wait for feedback after the interviews.

no offerfeedback delayreflection