It’s been two years since we gave the world a look at a “normal day” as a Gusto engineer [https://engineering.gusto.com/a-day-in-the-life/]. Since then the org has grown nearly three-fold and matured as an organization.
In this final part of the series, we will take a closer look at how to actually bring an experiment to life as a full-fledged feature. If you think the hard work is complete once the project is defined, think again!
I embarked on a mission with fellow Gusto engineer Alyssa Hester to find and complete an experiment solely focused on customer outcomes. In this first post of this series, we’ll talk about how Alyssa and I found an outcome-based experiment and defined a realistic minimum lovable product (MLP).
photo by https://www.pexels.com/@cqf-avocat-188397Over the past few months, multiple teams at Gusto have been rallying behind initiatives that help businesses navigate the uncertainties brought by the Coronavirus pandemic. Among these projects is the Paycheck Protection
My team recently embarked on a journey toward unbundling our part of Gusto’s monolithic Ruby on Rails app. A monolithic app is a single application that contains code across many domains. The boundaries are unclear. The domains
How to Onboard Your Own Engineering Teammates Hurray! That engineer that you interviewed a few weeks ago just signed and your manager asked you to help onboard them. You’re not the new hire’s manager, but you
Two engineers who moved to New York City as part of the landing team share about the office launch and what’s ahead.
Rebranding your company can be fun, but people rarely talk about the engineering work needed to bring a new design to life. Here are a few lessons the engineering team learned during Gusto’s most recent rebrand.
