Gusto Software Engineer interview questions

Initial Phone call. Technical call. Onsite. Pretty typical, the questions are also relatively easy - nothing that's really hard on the leetcode scale. The one thing you definitely need to do is to vocalize and explain every part of your thought process. The great thing was after I got rejected, they offered to tell me the team's feedback over a phone call. They even went into feedback of some of the specific parts of the interview. Not a lot of companies will do this, so I definitely give them huge props for this.

In short, this was the most personal and accomodating interview process I've ever experienced. Gusto treats people with such respect and hospitality it is hard to believe. They have invested so much thought and effort into taking care of people. I would highly recommend Gusto to anyone. An existing Gusto engineer recommended me for the position via an email introduction. I then had a few emails and phone calls assessing feasibility. After this, I was directed to a recruiter who assisted me throughout the rest of the process. The recruiter always followed up right away after my scheduled meetings to assess my experience, provide answers to my questions, and setup next steps. I had two separate one-hour remote interviews consisting of some conversation and a coding challenge via coder pad. One interview included a common algorithm and one included an interesting algorithm I had not seen before. At some point, I had also spoken to the Engineering Manager in more detail about the company and role. I was then flown to Denver, CO for some final onsite interviews. This was half a day of office tours, code challenges, and culture discussions.