Once I was contacted by the technical recruiter, I had a phone screen with an engineering lead. This consisted of a couple of high-level technical questions, general work experience and personality questions, and time for me to ask questions.
After this phase, I had two rounds of technical interviews. In each one, we used CoderPad to share a coding environment while talking over the phone. Both interviewers were clear in their explanation of the problem they wanted me to solve and helpful in laying out their expectations for my communication and explanation of my thought process.
For the on-site, they flew me to Denver to see the office and meet the team I would be working with. This final interview step included:
Since I had competing offers, the hiring process needed to move quickly, which they were able to accommodate.
Within a week of the on-site interview, I talked to my recruiter about the final steps: background check, reference calls, and approval by the hiring committee.
From beginning to end, I have felt welcomed and included. Any questions that I had, no matter how impertinent, were answered as honestly as possible, and it was clear that they value their employees as people, not just tools.
To get through this interview process, I needed to know how to use trees and perform a DFS, how queues work, how to write DRY code, and how to figure out new concepts quickly.
The following metrics were computed from 8 interview experiences for the Gusto Software Engineer role in Denver, Colorado.
Gusto's interview process for their Software Engineer roles in Denver, Colorado is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Gusto's Software Engineer interview process in Denver, Colorado.