Taro Logo

Software Engineer Interview Experience - United States

February 1, 2022
Negative ExperienceNo Offer

Process

I had an initial technical interview over the phone using CoderPad. The call was an hour long. I imagine it went well since they wanted to follow up with more interviews.

I then had five more interviews. Five. A total of six for the whole process. Each one was at least an hour long.

  • The second interview consisted of HR-type questions to find out how you jive with their "company values."
  • The third was more conversational, where I was asked about my work experience.
  • The fourth was another CoderPad exercise, similar to the first. I thought I did well on this.
  • The fifth was another CoderPad exercise. I had this one after a full day of work and got tripped up on the problem, even though over the weekend I went back to the problem on my own and figured it out.
  • The last interview was a design interview on a Miro board. This tests your architecture and design skills. I thought I did well on this.

The recruiter gave me a relatively quick rejection but did not give me any feedback. They even said not to ask for feedback.

This seems antithetical to one of their values: "Share openly, question respectfully, and once a decision is made, commit fully." I can't get better if you don't share with me why you didn't hire me.

While I don't see the need to have three CoderPad exercises when one would suffice, the problems were relevant to their domain, so they weren't just randomly picked off of LeetCode.

Everyone I spoke to was nice and treated me with respect.

Six to seven hours is a lot of one person's time. They could easily trim their process down to three interviews:

  1. A conversational one about experience.
  2. A "make sure you know how to code" interview.
  3. A design interview.

From talking to folks, it sounds like they're aware that they are a feature factory, but they want to move away from that style of work. They have a Rails monolith that they are currently wrestling with.

Questions

Calculate the taxable amount for a salary, taking different tax brackets into account.

Distribute income to a number of recipients evenly and don't overpay anyone.

Design a social polling app.

Was this helpful?

Interview Statistics

The following metrics were computed from 82 interview experiences for the Gusto Software Engineer role in United States.

Success Rate

24%
Pass Rate

Gusto's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive44%
Neutral15%
Negative41%

Candidates reported having mixed feelings for Gusto's Software Engineer interview process in United States.

Gusto Work Experiences