Perguntas de entrevista de vagas de Agile Java Developer da empresa Sky

They sent a simple technical exercise, which was easy to resolve. Use TDD. In the actual interview it was a pair programming exercise but really I was the one coding, my "partner" was not doing much. Another person was the "product owner". During this pair programming exercise, I tried to involve my partner but he did not really seem interested, and just steered me away from every single one of my suggestions. It appeared that they were expecting very specific answers and implementations and did not welcome any flexibility in the approach. I somewhat expected this from another glassdoor review but did not expect the pair programming exercise to be this bad. Afterwards there was a HR-style interview with the Head of Development (very nice guy) and one of the lead developers (also very nice guy). This interview was enjoyable and they asked standard questions like "what is agile to you" and "tell me about your favourite project". The office was really nice, everyone was casually dressed, and everyone genuinely seems really nice.

Got contacted by an in-house recruiter via email who saw my CV online and she sent me a small Java test to do. A week on and no feedback from the test I got invited to attend a face to face (final round), so I guess I did OK. The final round consisted of a pair test which was two guys sitting next to me, slightly confused as apparently collaboration isn't part of it, I always thought the point of pair programming is that you can bounce off ideas rather than going and just coding something. Second part was a very much untechnical interview with 3 people, I think the manager and 2 other devs. They asked mostly just about my last 2 roles and also asked me to draw an example of my work which with policies in place I don't feel like you can give too much away. I didn't pass the interview as I needed too much prompting with the sit down test and came across too un-technical with my explanation of my work although I wasn't asked about specifics about technologies used. I think coming to the office was an eye opener and speaking to developers there also made me put this role at the bottom of my list below other roles I'm interviewing for but each to their own.