I applied online. The process took 2 weeks. I interviewed at EPAM Systems (Zurich) in Jan 2019
Interview
They have a pretty simple interview plan:
1st one is a simple and nice discussion with HR
2nd one is a technical related call with EPAM - team leader/manager
3rd one: you`re invited on-site for a "motivational interview"
I didn't like the 2nd one as a lot of questions were not having sense as you`ll see below. Or they were been trick questions. Who knows... And he was in such a rush that I felt always runned down by someone... His hungarian-english vocabulary was also a bit weird as you`ll see below in the interview questions. Anyway, next week I had (ironically), another interview with another big consultancy for the SAME client on the SAME project, and it was such a nice and relaxing interview... This one with EPAM, it felt bad, because he was just reading the questions from a piece of paper and checked the boxes with my answers...
7. You have 200 test cases. You need to do regression. But another 50 automated and 50 manual tests tops up. From these 100 new ones, 50% are with the highest importance. How many test cases would you include in the regression testing? Including the first 200 ones.
8. It’s Monday morning. You have to finish a lot of tests until Wednesday at 16:00 when the software will be released in production. You know it’s impossible to do all of them until then. What do you do?
15. One developer doesn’t agree with you, how do you handle it? He says the defect it’s not a defect, but it’s a feature. How do you handle this situation?
I applied online. The process took 2 weeks. I interviewed at EPAM Systems (Zurich) in Dec 2018
Interview
There are four interviews:
· One non-Technical call with HR: nice guy, but needs to work at his English grammar because he does a lot of mistakes
· One Technical related Skype call with EPAM Systems: A bit dissapointed - never had such a "robotic" interview. He never asked me about my past experience, jumped directly to the questions and felt like a Q&A robot check-list.
e.g. Have you done that? No, ok. Next, next, and so on. He was just checkin' the answers on a sheet of paper and there were 40-50 questions so around one hour and a half. What was a bit annoying is that I felt him always in a rush, so I felt that I had to rush with my answers.
And I also felt lied because at the end he said: "Ok, we'll see where you fit and come back to you in about 1-2 weeks". After that, after only three hours after the interview, the HR guy sent me a rejection e-mail. It's clear that the tehnical recruitor knew that I'm not a fit, but why lie to me that it'd last 1-2 weeks?
· One Call with the client
· One Motivational call
Interview questions [1]
Question 1
Things about testing domain: what is API testing/testing pyramid, static testing, test plan, functional and non-functional testing, agile questions, and few cpp questions: constructors, etc.
The interviewer was very friendly, the process consisted of bunch of questions about my previous experience and a code review excersise. Everything took around an hour and it was a pleasure to talk with such an interesting opponent