Recruiter call - trying to find the right team and fit.
Technical phone screen.
Onsite visit - takes up pretty much all day, includes 2 behavioral interviews, lunch, and 3 technical evaluations.
At the end of the on-site, I got positive feedback and was asked to wait a few days for the final result. However, after 3 weeks, I had to start an email chain to figure out the outcome. I was eventually rejected, citing the reason that they couldn't find the right team and fit. When I asked for more technical feedback, I was ghosted.
The interview organization was pretty smooth; however, there were instances where the recruiter consistently disappeared, didn't respond to emails, and missed meetings. So, overall, bittersweet.
All questions were relevant and useful. You should know ES6 methods, create a simple data structure, and be able to sort.
Speak out loud your thought process.
One problem-solving problem was given certain conditions. Ask questions and clarifications!
Code pairing session, which was fun and engaging.
The following metrics were computed from 82 interview experiences for the Gusto Software Engineer role in United States.
Gusto's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Gusto's Software Engineer interview process in United States.