Gusto

Our engineering teams operate on weekly cycles. A typical team consists of 3-5 engineers, a product manager, and a designer. Testing and code reviews are a must for any branch to be merged into development. Kicking off a build to deploy code to production is as simple as entering a Slack command, and we’re deploying multiple times every day. We give kudos anytime someone submits a pull request that deletes more code than added.

Being precise at a huge scale — We are processing close to $20 billion in payroll and processing payments annually. We can't afford to make any mistakes at that scale and have built bank grade software to do this.

Elegantly abstracting complex and ever-changing government systems — It's not easy to accurately build a payroll system that works well in all fifty states and thousands of local tax agencies, especially when they don't always have good APIs. The same goes for dealing with big health insurance carriers. Building a system that is extendable and scalable can be challenging but rewarding.

Keeping our customer's information safe — Gusto is entrusted with a huge amount of customer PII (personally identifiable information) and PHI (protected health information). We store SSNs, EINs, bank account numbers, salaries, home addresses and more. Making sure we're safely handling this information while being able to ship code continuously and quickly is a unique technical challenge for us.

Making infrastructure better — We're currently decoupling our code base to make it more service orientated and making it have well defined interfaces. If you enjoy thinking about infrastructure, now is a great time to join.