OVERVIEW I interviewed for the software engineering position on the 'starcraft' team, specifically working on packaging linux applications. This position predominately used Python. Each step took 1 - 2 weeks to hear back from them, and they offer no feedback for each step. I will outline the steps below. ROUND 1 - ONLINE ALGORITHM ASSESSMENT They send you a link to a coding platform where you just complete your typical algorithm question. I think they give you ~30 min per question if I remember. I was given 2, the first question required familiarity with Python's datetime library, I managed to solve this one. The second question was quite difficult, you had to parse a string into a 2D array and then answer a question, I didn't manage to solve the second question. ROUND 2 - PSYCHOMETRIC ASSESSMENT You are given a link to quite a time consuming test which took me a couple of hours. You answer weird questions such as 'Jack is taller than Bob, who is shorter?'. You are graded on accuracy and time to complete each question. I believe they secretly just use this test to weed out people who aren't good at English comprehension. ROUND 3 - QUESTION AND ANSWER ESSAY You receive a questionnaire and have to provide a response for each question. This round took me a couple of hours to fill out the whole questionnaire. For example 'Do you have any experience with packaging software, if so please elaborate', and 'where you a goo student in high school'. ROUND 4 - VIRTUAL INTERVIEW You interview with 2 software devs, each being ~45 - 60 minutes I think. They literally just ask you trivia like questions to do with Linux. If you search 'top linux questions' on Google you will get a good idea of what kind of questions they will ask. Also the devs that I spoke to seemed quite junior, nothing against that as I am also junior/mid level, however that was still a little bit of a surprise. Overall they seemed quite nice. ROUND 5 - TAKE HOME ASSIGNMENT This was the final round I made it to. This round took me 5 hours total from start to finish. I had to make a command line application that made a simple get request to an online repo they provide, then you just parse the data you receive. The parsing is the only algorithmic part of the challenge because they want you to count how many times a particular thing appears, the rest of it is not too bad if you're familiar with Python. Ultimately they also want you to zip up your solution and send to them which is fairly trivial if you're developing on Linux, in my case a Linux virtual machine. Overall I actually quite enjoyed this round, it was kind of fun to do a challenge that wasn't you typical algorithm question and if your familiar with Python it shouldn't take too long. FINAL After completing each round it takes ~1-2 weeks to hear back from them. 2 weeks after completing round 5 I got rejected with no feedback.