Cigniti Inc. Qa Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Cigniti Inc..
Cigniti Inc.
QA Engineer
Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding Technical Behavioral
The process was good and easy. It started with discussing prior experience and roles/responsibilities, and included one coding problem. Next, there were automation scripting questions. Overall, it was a 25-minute session and seemed easy if you prepare well for the role.
Confirmed questions3 questions
- Can you tell me about your prior experience and roles and responsibilities?
- Here's a coding problem for you.
- Let's talk about automation scripting questions.
Cigniti Inc.
QA Engineer
Entry Easy Negative experience No offer 1 round
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Technical Behavioral
The HR person was very polite and professional. The L1 interviewer, Sanjana, seemed to lack soft skills training and professionalism, as she didn't even introduce herself. Cigniti's practice of requiring only the candidate to have video on during calls is unusual and unprofessional. The L1 panel member seemed inexperienced, with 6-7 years of experience interviewing a candidate with over 10 years of experience, which raises questions about Cigniti's assessment process. Cigniti should ensure a more experienced panel member is present for interviews. It was disappointing to be interviewed by someone unfamiliar with Agile development practices, including test-dev integration and automation script creation/maintenance. The experience would have been better with a more experienced interviewer from Cigniti.
Confirmed questions8 questions
- Could you tell me about the types of testing and technologies you have experience with?
- What would be your approach to testing a registration page?
- How would you test a scenario with nested dropdowns?
Cigniti Inc.
QA Analyst
Mid Average Negative experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Behavioral Technical
I was contacted by their recruiter Arjun and we verbally agreed to a daily rate. I then proceeded through 3 interview stages with different managers, all of which I passed. However, Arjun then significantly reduced the initially agreed rate. After I expressed my disappointment in his unprofessional behavior, he went to negotiate an acceptable rate, which was still lower than what was advertised and initially agreed upon before the interviews. He then came back with an even worse offer: a 6-month fixed-term contract at a rate below the market rate for a permanent position. My advice is to avoid this company and not waste your time.
Confirmed questions1 question
- What are some common questions for a Manual QA role?
Cigniti Inc. Qa Engineer Interview Questions
Quoted word for word from Cigniti Inc. interview reports.
“What is the difference between a test strategy and a test plan?”
Read reports →“What is the difference between system testing and end-to-end testing?”
Read reports →“What's the difference between a corrective action and a preventive action?”
Read reports →“What are some different response codes used in APIs?”
Read reports →“Write a locator given sample code.”
Read report →“What is the procedure for updating a request within an API?”
Read report →“Can you explain what PATCH is in the context of APIs?”
Read report →“Can you define query parameters and path parameters?”
Read report →“What is cross-browser testing, and what aspects do you typically test during it?”
Read report →Formats, difficulty and experience
Across all 13 Cigniti Inc. interview reports.