I have been working as a test automation engineer for almost three years. I found the job ad on LinkedIn and applied.

Then, I was contacted by a recruiter at King.com and had a phone conversation regarding my background, salary expectations, and some normal interview questions, like 'Why did you choose us?'

Next, we scheduled a face-to-face interview with the same recruiter, plus one developer and a senior test automation engineer. This was the first interview, and they asked about my technical background and experience, but no tricky programming or testing questions.

I passed this step and, as the second step, received a technical test by email with one week to implement a solution. The technical test was rather easy and, I guess, meant to test both coding and testing skills. I implemented a solution in two days, which was accepted, and I made it to the final round of interviews.

The final round involved an interview with five employees! First, I interviewed with two QA heads simultaneously. They asked plenty of tricky questions regarding testing and automation. Then, I had interviews with a scrum master, a product owner, and a developer, with different technical questions.

After three days, I got feedback that I was too junior for the role, as I lacked knowledge in C++ and Flash. This was really unexpected, as nowhere in the job description were any requirements for C++ or Flash skills mentioned. Also, they knew from my CV that I didn't have C++ or Flash competence, but rather good competence in Java, testing, and automation, and I thought that's what they expected for this role. I would expect to get this feedback earlier instead of taking hours off from work to go to their interviews!

But anyway, besides this, the interview process was okay and professional. The work environment looked too populated, with many people sitting in a small office, but they said they are moving to a bigger office soon.

One good thing with working at King.com seems to be that you have the option to choose your computer.

How do you test a mobile game that changes state when you close and open it again?