Gusto Software Engineer interview, take-home and pair session

Gusto·Software Engineer·Reported May 2025
Take-home ProjectOtherOfferMedium

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 were shaped a lot like LeetCode problems. I also felt tension around the rules. The guides suggested that I could look things up, but some interviewers didn't allow it during the exercises.

The strangest part was a final working session advertised as pair programming. Instead of collaborating on a messy problem, the conversation became more adversarial. The interviewer quickly corrected me or steered me away when I made minor mistakes, while calling out edge cases immediately.

I completed the work and felt that my solutions were moving in the right direction. Overall, though, the process left me feeling that it wasn't as collaborative or forgiving as it had been presented. I ended up re

Location: United States. Overall feedback: Negative. Offer status: Got offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Gusto
Role
Software Engineer
Rounds
Take-home Project → Other
Outcome
Offer
Difficulty
Medium
Date
Reported May 2025

Real Gusto interview experiences

First-hand reports from Gusto candidates — the rounds, the questions they were asked, and how it went.

All 6 Gusto interview experiences