A very unfair interview process. During the pairing stage, I was asked to add two small changes into the project that they give you. I asked about priorities and scope throughout the pairing session, as I wanted to show architectural decisions and code testability, but it wasn't until the last 10 minutes that the interviewer said I should drop that and focus on having a working example of the requirement. It is the role of the interviewer to find out how I work, not lead me into areas I would overspend time on which I wouldn't be marked on.

• Initial interview with a recruiter.
• A technical discussion: past projects, how I worked in a team.
• Pair programming: They give you an exercise beforehand and ask you to solve a problem.
• System design / behavioral interview: I didn't make it to this stage.

Tell me about the toughest challenge you faced.