Standard meeting with principal engineer, home technical task, pair programming session, behavioural/culture meeting. Friendly recruiter, friendly principal engineer. Less friendly interviewers (principal, lead, devops) during the pair programming stage. We spent a majority of the time in the pair programming session going back and forth over needless trivial questions. Despite giving suitable answers, I was met with blank stares and demeaning responses - especially when I asked them to elaborate on what exactly they desired from my answers. You could feel the smugness of the lead engineer who did nearly all of the talking, even when he gave me an incorrect term that I asked him to define (as if I was stupid for not knowing what his incorrect term meant). At one point I was aggressively cut off whilst answering a simple question. Ultimately, it felt like the lead engineer had something to prove, the devops engineer didn't want to be there in the first place, and the principal engineer didn't want to get involved. After wasting 45 minutes of my time, we had spent barely a few minutes actually on my submission. Ironically, if they let me actually go through my work, I would have been able to demonstrate a great breadth of knowledge in their desired areas - it was all in the notes.

4-stage interview process - informal chat with the head of engineering, technical test, code review on the test with 3 engineers, and then a final chat with the CTO. The interview process was conducted relatively quickly from start to finish it took about 2 weeks. I felt very comfortable talking with the team at Yulife all of whom seemed very knowledgeable and professional. The technical test was relatively straight forward and it was a pleasure talking with the team about what I had done and why. I also really enjoyed my catch with with the CTO who seemed like a lovely guy and someone I could work with.