Interview experiences · Gusto
Gusto Software Engineer interview with repeated scheduling and communication issues
RejectedHR screen
My biggest problem wasn't the technical difficulty. It was the process itself, especially how scheduling and communication kept falling apart. I had several recruiter interactions go sideways: calls where nobody joined, last-minute reschedules where I was stood up again, and follow-ups that never produced a clear answer. At one point, I even received a generic rejection email without any meaningf…
My biggest problem wasn't the technical difficulty. It was the process itself, especially how scheduling and communication kept falling apart. I had several recruiter interactions go sideways: calls where nobody joined, last-minute reschedules where I was stood up again, and follow-ups that never produced a clear answer. At one point, I even received a generic rejection email without any meaningful detail after the recruiter had already seemed unreliable.
When I finally connected for a recruiter screen, the conversation was pretty standard. Even then, the wrap-up felt thin. They said they'd coordinate with the hiring team and get back to me, but the updates didn't arrive when expected. I followed up a couple of times, and the lack of responsiveness made it hard to trust that my application was in the right queue. Eventually, I found out my resume might have been screened quickly because it wasn't clear enough what tech stack I'd used in past roles.
By the end, I wasn't offered a role, and honestly, I left feeling strung along. Everyone I spoke with was pleasant in the moment, but the missed calls, silence, and vague messaging made the experience frustrating.
Location: San Francisco, CA. Overall feedback: Negative. Offer status: No offer.
Comments
Nothing here yet.
Join in on CSWork →