-First there is a standard introductory call with the head of talent. I was given a broad summary of the role, the company and the team and gave a summary of my experience and skills. - Then the first of two pair programming sessions was a one hour exercise with a lead developer involving a simple task with a heavy focus on TDD. The main intent here seemed to be to assess my raw aptitude at coding as well as how I work in a pair. The ability to work well in a pair seems to be highly desirable to this team. There were not many high level design or architecture questions at this stage, just low level coding questions. - The second pair programming session was on a real issue from the team's backlog with a senior developer and took around 2 hours. This started with asking me questions about my background both personally and professionally and telling me a bit more about the team before getting stuck in to the task. We were adding a new attribute to a RESTful API resource, again this was approached using TDD. Throughout the task I was asked various standard questions about enterprise development such as database design (relational vs noSQL), microservices, REST, application frameworks etc. Overall it was a very refreshing interview compared to a dry technical question and answer format. I was given a good opportunity to show of my skills and experience while also gaining an understanding of how their development teams operates.