The interview first started off with a 30-question multiple-choice test. Each question was timed for 2 minutes and ranged from OS concepts to recursion.
Some questions were simple "explain why this code does not work," while others required filling in the line of code that would make it work.
Ultimately, the questions were used to test the candidate's range of knowledge. However, it was found to be rather unpleasant, questioning why a Full Stack Engineer would need to know the difference between concepts like the program counter and branch prediction.
The questions ranged across several different programming languages, including Ruby on Rails, JavaScript, Python, and C++.
Overall, I thought the interviewing questions were too broad to judge a potentially good candidate, which is why I'm a little disappointed in their interviewing methods. Either you knew the answer or you didn't. There was no time to deduce an answer with the limited time for each question.
Which of the following holds the next instruction address to be executed?
The following metrics were computed from 1 interview experience for the Gusto Full Stack Software Engineer role in United States.
Gusto's interview process for their Full Stack Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Gusto's Full Stack Software Engineer interview process in United States.