Pretty arduous, felt like a bit of a waste of time in the Team's call interview process given I was pretty forthcoming about my experiences on my resume. It was listed as an entry level position when I applied but it definitely feels like they're looking for much more than that. The first interview rounds were just technical assessments that could be passed relatively easily. The big written questionnaire takes a while to complete but overall nothing of extreme difficulty. The coding assessment I felt was not that bad if you've practiced your leet code and whatnot. I then made it to the talking stage where they schedule 3 technical interviews for the role. I prepped and felt relatively confident going on but it almost felt like there was a disconnect between the skills I listed on my resume and what they had tested me for vs the actual interviews. Each interview was an hour long and was essentially just the interviewer grilling me for 55 minutes. I felt I did my best given my experience but there are some things that I would not be able to know unless I had another 2-3 years experience under my belt (I have about a year professional experience currently). Thus, these interviews felt like a waste of time given I had pretty clearly written out what I knew and what I've done. I would definitely not recommend interviewing unless a.) you've been contributing to Canonical open-source projects in the past or b.) you have at least 2-3 years of work experience under your belt relevant to system design, golang, and linux administration. I hoped that I could make my case based on how quickly I have been able to pick up new technologies and become a leading developer within my environment, but as I said earlier, the interviews are just you being grilled for almost the whole interview session with very little time to say anything about yourself. Definitely would not call this 'entry-level', seems to be more 'mid-level' expectations.