Taro Logo

Software Engineer Interview Experience

August 1, 2015
Negative ExperienceNo Offer

Process

They contacted me and set up an interview. The first interview was with an engineer lead, and he talked more than I did. A little weird, but it's fine.

In the second interview, an engineer asked me to implement reduce() in Ruby. I was not very familiar with the scripting language, and he was not good at explaining the concept and was very impatient. In my opinion, if I understood the way scripting languages work, the interview would have been pretty easy. But there was a learning curve, and with all those new terms, I didn't grasp the concept very quickly. There were a couple of questions, and he expected me to provide the correct answer in seconds. Otherwise, he told me the answer without letting me try to figure it out. The interview was supposed to be one hour, but he told me all the answers and finished it in 30 minutes.

I wouldn't want to work with someone impatient. Everyone needs some time to learn.

If it is for an engineer position, the interview is in Ruby, and you have no choice! I did brush up a little on Ruby beforehand; however, I found it very distracting to use a new language. I paid a lot of attention to the syntax but forgot about the logical edge cases.

In sum, the interview was very informal.

Questions

Why do you want to work for ZenPayroll?

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