I was referred by a friend who already works at tyro. The recruiter was based out of New Zealand and it was a little hard to communicate to him as he did not pick up calls usually, but he was overall very nice to talk to. He explained the process well and accommodated the dates as per my availability. I went through the first "pairing interview" round where I was told that the interviewer is new to conducting interviews and he has recently been "trained" for pairing interviews. At the start of the round he was expecting me to be ready with an IDE setup and any language of my choice already so that I can share screen and work on it which wasn't told to me beforehand. I had to use the interview time to quickly setup my system. I checked with other friends and they said they were not required to do that and were given a codebase already setup with required configurations. Not sure if it was my interviewer who was new and didn't know or a new requirement which was missed to be communicated to me. But fortunately it did not take too long for me and interviewer was a little accomodating too. The interview started fine and I was asked to solve a small leetcode kind of problem in any language of my choice, I chose JS. Due to my previous experience of pairing interviews I followed a TDD approach by writing tests and then making them pass by the easiest implementation possible and then optimising it. After a couple of days when I did not hear back I checked back with the recruiter and he said he did not get a chance to talk to the interviewer and get the feedback which was weird because I think if the interviewer is not supposed to give his/her feedback right after the interview (even if it means in a written form) then it might get impacted by external factors and skews the result. Thats my opinion anyway. The feedback came in via email since the recruiter was "too busy" and I was rejected with the comment saying that I was not able to put design patterns in practice when problem got complex and added too many conditionals. I do not completely agree with that because - it was a pairing interview which is more about the communication and collaboration. Yes, you obviously need to look at coding standard but when you are following TDD you always start with easiest approach to solve a problem and then optimise it. I did not even partially complete the solution yet so no point optimising it then. Thats called premature optimisation which someone would do just to show off their skills and if they already know the actual solution of that problem.

Recruiter reached out through LinkedIn. Subsequent discussions on Zoom. Pretty standard interview process. - Recruiter round -> General discussion why Tyro, current role and a brief about interview process - Pair Programming with one of their engineer - Management Round - HR discussion