QA Engineer applicants have rated the interview process at Imperva with 4 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 58.5% positive. This is according to Glassdoor user ratings.
Candidates applying for QA Engineer roles take an average of 17 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Imperva overall takes an average of 19 days.
Common stages of the interview process at Imperva as a QA Engineer according to 4 Glassdoor interviews include:
One on one interview: 50%
Phone interview: 33%
Skills test: 17%
Here are the most commonly searched roles for interview reports -
First meeting with HR rep, then with technical team leader, then with manager.
In the interview each interviewer tries to figure if you are competent enought, team player, nice and honest. They ask you technical questions in the networking and security areas, talk about your experience, check if you are technical guy.
Interview questions [1]
Question 1
Networking, OS, DB, Logic questions. The isn't view takes an hour or so. It is fair.
I applied online. I interviewed at Imperva in Feb 2017
Interview
I met with Imperva's QA TL. He described the position and the type of person he needs to do the job - including extra hours, traveling abroad (3-4 times a year). A very standard an "all-around" QA engineer that will understand all the company's products and services.
Interview questions [2]
Question 1
I was given a network diagram and asked to explain several networking types of questions in relation to the diagram
Describe a bug you've encounter during your work experience that involves different servers, components, services and configurations and how you managed to point and find the bug's source and reason
I applied through a recruiter. The process took 2 weeks. I interviewed at Imperva (Tel Aviv-Yafo) in Apr 2015
Interview
HR Interview - Tough but fair.
Technical questions about switching, routing, problem solving, protocols and also one riddle.
It is a lot about getting a cultural fit as well as being technically strong and able to learn independently. The whole process was very quick and discreet and I appreciated it.
I applied through an employee referral. The process took 2 weeks. I interviewed at Imperva (Tel Aviv-Yafo) in Jan 2013
Interview
I came in through a friend deal - first went to a QA TM for a technical interview which went ok I thought (nailed the questions after some thought), but probably not OK enough. Then another interview with a Support TM, a job I like better, that went ok too and I went to HR, where I allegedly threw just a bit too much dirt on my then-employer, whom at that point I had been having issues with. They heard my wage expectation which judging from their glance must have been a tad higher than expected.
Shortly after that I was curtly dismissed over the phone. The process took about three weeks and two visits. They were fair, I'm guessing I didn't shine bright enough professionally and didn't strike HR either. A shame, their company and the people I met (including my friend of course) seemed to make a great place to work in.
Interview questions [1]
Question 1
I said I was strong at TCP/IP so they tried to tackle me with some troubleshooting of that. Questions like why a connection started with packet that has a wrongly NATted source IP (disguised in the data) wasn't getting through.