The first step was an absurdly large written interview. Almost every question was vague, broad, phrased weirdly, unproductively similar to previous questions, and often with lack of basic grammar. Esentially, you're given a low effort request to cover everything that may ever be relevant at least twice. You can either give an overly summarized, general and useless answer or spend a number of hours trying to respond meaningfully. I did the latter. I made the mistake of sending the recruiting engineer emails, instead of submitting through the link. My emails were ignored for a while, and then I was asked to use the link instead. That was on a friday before a weekend that was also a holiday. On Sunday morning, I got an email, from the same person, stating that, due to my apparent uninterest, my application will be closed. I wrote full 8 pages of responses.
Interview questions [1]
Question 1
"Outside of class, what were your interests and where did you spend your time?"
It's an extremely long process that includes standardized tests, take home assignments, and several rounds of interviews. It was at least 5 rounds long and you interview across different teams.
I applied through other source. I interviewed at Canonical (London, England)
Interview
They have a really long, tiring interview process. The first round was a written interview where I had to answer like 15 questions. Then a coding interview with 1 hour time that I could do anytime for 2 weeks. Then I had to take a personality test and they totally ghosted me.
The first round is a bunch of questions like 30 or so where you have to describe your expierence, personal and academical information. Then there is a asynch technical interview and a psychology test.
Top companies for "Compensation and Benefits" near you