I had a pretty strange interview experience and wanted to see if anyone else has experienced something similar.
The first round was described as a pair-programming / Test-Driven Development exercise. The task was very simple: take an amount, such as 1200, divide it across 12 months, and make sure the resulting values were correct.
I followed the TDD approach from their preparation guide: wrote the tests first, made them fail, implemented the solution, and then refactored. I completed the functionality and the tests were passing, but I was still rejected after the round.
I'm trying to understand what they were actually evaluating beyond simply getting the implementation and tests correct. Has anyone gone through this interview and knows what they specifically look for in the TDD/pair-programming round?
Discussion
Loading comments…