Great company, great team, minimal growing pains
Great company, great team, minimal growing pains
People are great, and the team is tightly focused. The company is growing really fast and doing exciting, impactful things. I expected my enthusiasm to die down after the first month or so, but it has been kept up by the team, the product, and the customers' love for what we build.
There isn't always a clear escalation structure. The company is growing really fast, which is sometimes a challenge for existing processes. There is not a good boardgame group here (yet)!
Don't lose touch with the "rank and file"! You've done well so far, but it's going to slip in the coming months as we grow.
Was this helpful?
Gusto Interview Questions
Gusto Interview Experiences
Software Engineer
Process starts with a general phone screen with a recruiter checking for general interest and some technical background. Next is a technical phone screen using codepad. The questions aren't generally hard; you just need to be prepared if you haven't
Software Engineer
Gusto's recruiter reached out to me, and the process was pretty standard after that: a recruiter call, a technical phone screen, and then an onsite. In the phone interview, the problem was challenging, as there was a lot of business logic to impleme
Software Engineer
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 proce
Software Engineer
San Francisco, California, United StatesDecember 1, 2019Process starts with a general phone screen with a recruiter checking for general interest and some technical background. Next is a technical phone screen using codepad. The questions aren't generally hard; you just need to be prepared if you haven't
Software Engineer
San Francisco, California, United StatesJune 1, 2019Gusto's recruiter reached out to me, and the process was pretty standard after that: a recruiter call, a technical phone screen, and then an onsite. In the phone interview, the problem was challenging, as there was a lot of business logic to impleme
Software Engineer
San Francisco, California, United StatesApril 1, 2018Initial 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 proce
