Principal QA Engineer applicants have rated the interview process at Backbase with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 89.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Principal QA Engineer roles take an average of 10 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Backbase overall takes an average of 27 days.
Common stages of the interview process at Backbase as a Principal QA Engineer according to 5 Glassdoor interviews include:
One on one interview: 29%
Skills test: 21%
Presentation: 7%
Group panel interview: 7%
Background check: 7%
Personality test: 7%
Phone interview: 7%
Drug test: 7%
IQ intelligence test: 7%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1+ week. I interviewed at Backbase
Interview
Planned and organised process. Very well communicated about the schedule of interview. Interview panel has sound knowledge of the subject. Organization overview and job expectations were made very clear. Feedback was provided promptly and informed on the subsequent steps involved :)
Interview questions [1]
Question 1
Coding questions in java problem solving Test Automation questions
I applied online. I interviewed at Backbase (Hyderābād) in Oct 2022
Interview
Interview is conducted in four rounds: 1. Introduction call with recruiter 2. technical round with principal QA about technical capabilities 3. Managerial round with a senior manager on culture fit 4. HR round on salary part
Interview questions [1]
Question 1
Technical skills based on your resume, some questions about automation and a codility test
I applied through a recruiter. The process took 1 week. I interviewed at Backbase (Amsterdam) in Aug 2022
Interview
It was a clear process.Recruiter was helpful and communicated each steps with details and what was expected. During the interview it was more on programming side than the actual QA related things.