Avoid, unless it is your only option
Avoid, unless it is your only option
A respectful environment for people from different cultures and backgrounds. English classes if you don't speak it well. The pay is okay if you're an engineer.
Non-existent QA processes for features, so when something explodes, the PM comes running and demands the issues to be fixed. But there are no acceptance criteria, staging environment, or well-written Jira tickets.
The senior engineering staff has this strange practice of blocking your PRs with 'best practices' suggestions, just to never go back to it if you have more questions. Also, they will treat you as if you were an expert on the codebase, usually lecturing you about not using 'legacy stuff' without prior context.
The tech debt is astronomical, but they insist on using technologies that probably won't solve the use case.
It is expected for you to publish on average 10 PRs per month to keep you in the performance green zone. Why 10? No one knows. Should I deliver 10 even if I'm new to the company? Yes. Can anyone explain to me why this is failing? Guess what, nobody knows, or senior staff is not willing to help.
The onboarding for engineering is non-existent. They have treated me with respect, but beyond that, I think it is one of the worst companies I've worked for.
If you do Ruby on Rails, of course, you can get something far better.
Expect overwork.
Your culture is super bureaucratic, and the management of the laptop borders on Orwellian practices. You can do better.
Additional Ratings
Was this helpful?
Gusto Interview Questions
Gusto Interview Experiences
Software Engineer
Initial recruiter phone call followed by a technical phone screen. The question was a simple data parsing to extract/aggregate JSON data. The interview was friendly and wrapped up with closing questions. I received a rejection email a week later, wit
Software Engineer
I was surprised by how cumbersome this interview process was. It involved several rounds, on top of a take-home project. It's really rigorous for a company that isn't FAANG level. Honestly, a take-home and a discussion of it are enough technical si
Software Engineer
Medium difficulty, or easier if you look up the Q&A's beforehand. One interviewer was late and had the nerve to mark off points for time. So, I did not get the job.
Software Engineer
New York, New York, United StatesJune 1, 2025Initial recruiter phone call followed by a technical phone screen. The question was a simple data parsing to extract/aggregate JSON data. The interview was friendly and wrapped up with closing questions. I received a rejection email a week later, wit
Software Engineer
United StatesMarch 1, 2025I was surprised by how cumbersome this interview process was. It involved several rounds, on top of a take-home project. It's really rigorous for a company that isn't FAANG level. Honestly, a take-home and a discussion of it are enough technical si
Software Engineer
New York, New York, United StatesJanuary 1, 2025Medium difficulty, or easier if you look up the Q&A's beforehand. One interviewer was late and had the nerve to mark off points for time. So, I did not get the job.
