The culture at Gusto has been crafted very well. Culture comes from the beginning of a company and the people that started it. I can tell today that those folks (Josh, Eddie, Tomer) are quite kind and have their heads on straight.
I feel confident in the direction of the company and about its longevity. Leadership is transparent about the decisions they make, and so I don't ever feel like I'm left in the dark about the way the organization is run.
I work on things that I believe have high positive impact for regular people that use the product. For example, one of my teammates is working on PPP loan forgiveness. We've also worked on making employee payments faster, thereby reducing the time money is tied up in the financial pipes and increasing the time it stays in employers' bank accounts.
Gusto has the same technical problems that any medium/large company has. A giant codebase, complex code, cruft, old practices, and a development experience that isn't fast. I don't think anything has been mismanaged for things to get to this point, technically. I'm also encouraged by the company's reaction to these problems. I see the organization moving in the right direction.
As I mentioned above, I really appreciate the transparency with which big organizational decisions are made. I like the focus on agility and experimentation that's been happening over the last year. Keep up the good work.
I first spoke with a recruiter and discussed my interests, experience, and available roles. Next, I completed a coding interview. I was on screen share with a developer and had to finish a task. Although it was not a particularly difficult task, I
I was asked to complete an online quiz, which is a terrible metric for finding candidates. The spectrum is far too broad; you might be asked to do bit manipulation in C and then describe how to float an element in CSS. There are probably about 10 pro
It was interesting. 5 phone screens and an "onsite" that consisted of two remote interviews from their Denver office with engineers in their SF office. Ended up not getting an offer; I'm pretty sure it was because I bombed my second-to-last questio
I first spoke with a recruiter and discussed my interests, experience, and available roles. Next, I completed a coding interview. I was on screen share with a developer and had to finish a task. Although it was not a particularly difficult task, I
I was asked to complete an online quiz, which is a terrible metric for finding candidates. The spectrum is far too broad; you might be asked to do bit manipulation in C and then describe how to float an element in CSS. There are probably about 10 pro
It was interesting. 5 phone screens and an "onsite" that consisted of two remote interviews from their Denver office with engineers in their SF office. Ended up not getting an offer; I'm pretty sure it was because I bombed my second-to-last questio