Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

6 stories

Likes earn the author +10 XP for the first 3 likes each day

GustoSoftware Engineer
Reported Apr 2026

Gusto Software Engineer coding round: hard LeetCode problem and sponsorship constraint

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…

RejectedHR Screen0
GustoSoftware Engineer
Reported Apr 2026

Gusto Software Engineer interview with repeated scheduling and communication issues

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…

RejectedHR Screen0
GustoSoftware EngineerSenior+
Mar 2026

A Repeat Design Question the Interviewer Couldn't Follow

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
GustoSoftware Engineer
Reported Nov 2025

Gusto Software Engineer interview with a Codesignal GCA-style assessment

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…

Online Assessment0
GustoSoftware Engineer
Reported Oct 2025

Gusto Software Engineer interview with timed LeetCode medium assessment

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…

Online Assessment0
GustoSoftware Engineer
Reported May 2025

Gusto Software Engineer interview, take-home and pair session

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…

OfferTake-home Project0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP