Devops Engineer applicants have rated the interview process at Backbase with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 89.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Devops Engineer roles take an average of 21 days to get hired, when considering 3 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 Devops Engineer according to 3 Glassdoor interviews include:
One on one interview: 29%
Skills test: 29%
Presentation: 14%
Phone interview: 14%
Other: 14%
Here are the most commonly searched roles for interview reports -
Applied on Linkedin for the job. Recruiter online interview after few days. Then first high level tech and role related interview, second in depth tech interview, then manager interview, and offer afterwards.
Interview questions [1]
Question 1
questions about communication with team, about kubernetes and ci/cd
Relaxed style interview after an online coding test, lots of focus on digging into current experience, very open and honest about what the role will entail and whether it is something I would look for in a new company
Interview questions [1]
Question 1
Devops principles, how I would approach debugging an issue with Kubernetes in production, what type of impact I would like to make in the company
I applied online. I interviewed at Backbase (Amsterdam) in Jun 2023
Interview
Good technical interview with real-world scenarios and practical questions, no whiteboards or algorithms. Recruiter never got back with feedback, basically just ghosted me. It's like your only job, man, is it that hard writing an email to a person with a 'It is a no'? I have no idea why we need recruiters at all now, especially that many. First they stalk you, and then... ghost? How professional :) Would not recommend wasting time.
Interview questions [1]
Question 1
Based on what metrics would you scale your k8s clusters? What is workload identity?