The first part of the process was a remote pair-programming session using CoderPad. This was followed later by a remote one-on-one session, where we discussed my background and choices leading up to the interview. Another remote pair-programming session then took place.

After that, I was invited to their offices for on-site interviews. These consisted of a technical deep-dive talk, a design/problem-solving session, and an on-site pair-programming session.

All pair-programming sessions were conducted using the programming language of my choice.

In the design/problem-solving session, I paired with the interviewer to design a web service. Given an initial set of requirements, we developed a high-level design of the service, asking questions back and forth. As we worked through solving the problem, additional requirements were introduced to add complexity, and we built upon the design to accommodate them.

In the pair-programming sessions, I was allowed to use the programming language of my choice and to consult online resources. The problems did not involve regurgitating algorithms or requiring prior knowledge. Instead, they were simpler problems that were either more related to the role (any necessary domain knowledge was explained during the interview) or were more engaging problems one wouldn't normally solve professionally day-to-day.

Additional requirements and complexities were also introduced as I progressed through the problems. One of the problems I encountered was: given a string, return an array of strings based on certain rules. During the pair-programming sessions, I was also asked to articulate my thought process to the interviewer.