Interview experiences · Gusto
Gusto Software Engineer coding round: hard LeetCode problem and sponsorship constraint
RejectedHR screen → Tech screen
I started with the recruiter and first stage, then moved on to a coding round. The problem felt closer to the hard end of LeetCode than to an easy exercise. I first solved it with a brute-force approach, and after I showed that I understood the core logic, the interviewer pushed me toward an optimal method. I reached an efficient solution and passed the relevant test coverage, so I left feeling t…
I started with the recruiter and first stage, then moved on to a coding round. The problem felt closer to the hard end of LeetCode than to an easy exercise. I first solved it with a brute-force approach, and after I showed that I understood the core logic, the interviewer pushed me toward an optimal method. I reached an efficient solution and passed the relevant test coverage, so I left feeling that I'd handled the technical part well.
Even with that performance, I didn't receive an offer. The rejection came quickly. One explanation I heard later pointed more toward non-technical constraints than my ability, specifically sponsorship. The coding bar seemed genuinely high, but clearing that technical hurdle didn't necessarily lead to a hire.
Location: San Francisco, CA. Overall feedback: Positive. Offer status: No offer.
Comments
Nothing here yet.
Join in on CSWork →