Three stages: - Screen by an external vendor: 1 hour covering a breadth that I really appreciated that it is being covered. That's for them to prevent folks who didn't even prepare from taking their engineers' time... good practice for the interviewee too. - The technical onsite: The interviewers are great to work with, and I really liked that all questions were relevant to the role. You interview with the team for which you're considered, so this helps a lot. - A round with your management chain: A great opportunity to talk to your director, VP, CTO, and even the CEO (5 mins if he has time). Loved this part!

I was not at all impressed. I solved an IQ problem that was fairly simple and then had to build Cork from GitHub. It took a day of sorting out build problems before I got it to build. I then found an alternative called CloudCompare with an installer. Then came the "coding test", which seems designed to find reasons to reject PhDs with twenty years of software/hardware experience, since I cannot imagine NASA giving Stephen Hawking a "coding test" to prove he can write FORTRAN or C++. I was given two hours to solve two problems on Testdome. I solved them and tried to submit the solution, only to receive an error message that I was "not allowed" to include a C++ "main" function containing my tests. I emailed the code to Roblox (which compiled, ran and gave correct results in Visual Studio) and then sent a follow-up email with an optimised version (under the assumption that they value people who take the trouble to improve on what they can achieve with someone standing over them with a bullwhip and a stopwatch). Shortly thereafter came the standard "no-reply@xyz.com" email to announce I was "not suited", which I now take to mean "We are a sweatshop, not NASA, go away", since I seem to get it whenever I am interviewed by known sweatshops such as Amazon. It is a shame, since the high level discussion was more interesting than the "Prove you'd make a good hacker" part of the interview process. I love discussing how you can apply physics to problems in Computer Science, because I would rather join a company that hires PhDs to solve problems hackers can't. Having worked for hackers who ruin your skills, I don't want to work for more hackers. The only thing I can say in fairness is that I took quite a while to get around to the coding test. This was down to the fact that I have some lousy flatmates who were keeping me awake at night and I do not really like "coding tests", especially when I am too tired to think properly. This said, either they want PhDs or they want coding-grunts who love sitting coding tests because they hate jobs that involve mathematics.