real interview stories, told over a cup of tea ♡
Gusto Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
5 results
- Gusto Software Engineer coding round: hard LeetCode problem and sponsorship constraintGusto · Software Engineer · HR Screen · Apr 2026Rejected
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…
- Gusto Software Engineer interview with repeated scheduling and communication issuesGusto · Software Engineer · HR Screen · Apr 2026Rejected
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…
- Gusto Software Engineer interview with a Codesignal GCA-style assessmentGusto · Software Engineer · Online Assessment · Nov 2025
After I applied, I moved forward only after completing a Codesignal GCA-style assessment that wasn’t automatic. Once I passed, I had two technical rounds with LeetCode-style questions drawn from the company’s tagged topics. The rounds felt sequential and fairly structured. I solved each problem, reviewed my approach, and moved to the next step after clearing the previous one. After the technical…
- Gusto Software Engineer interview with timed LeetCode medium assessmentGusto · Software Engineer · Online Assessment · Oct 2025
The process felt straightforward and predictable. After applying, I completed an online assessment, followed by a technical interview focused on a LeetCode medium problem. The process then moved toward an offer decision. The online assessment was the difficult part. One question was relatively easy, but after that I essentially had to produce a perfect coding solution without debugging, all withi…
- Gusto Software Engineer interview, take-home and pair sessionGusto · Software Engineer · Take-home Project · May 2025Offer
My process felt rigorous and time-heavy. It stood out because it involved more than a single technical screen, with multiple signals being collected. I was surprised by how much effort the interview required overall, including a take-home component, follow-up work, and extended technical work that didn't feel proportional to the compensation. The questions were framed as "real work," but they wer…
