3 ms·
I use Gusto and like it for it's simplicity. It makes a complicated part of running a company much smoother. That said, I'm very curious what exactly all those
by smt88 8y ago
I use Gusto and like it for it's simplicity. It makes a complicated part of running a company much smoother.
That said, I'm very curious what exactly all those engineers are doing every day. What's the most meaty part? Payroll? Dealing with govt? Keeping the servers up?
I think unexpected scaling pains are one of the most interesting and unsolved issues with being a CTO and would love to hear more about that at Gusto.
- edawerd 8y agoI can certainly share some of the meatier areas that engineers at Gusto work on. - Calculating payroll and filing quarterly and annual forms are very complicated tasks that (a) is different in every state and (b) changes frequently as federal, state, and local tax laws change. Doing payroll in 50 states is similar to doing payroll in 50 different countries - Benefits is similar to Payroll in the sense that it's also very different in each state. The business logic is complex and a significant amount of engineering work goes into simplifying it for us customers - Because we move billions of dollars per month through the banking system, we have a lot of the same technical challenges as a Stripe, Square, Paypal, Venmo, etc. We have a dedicated FinTech, Payments, and Risk teams for this. - Security is super important to us, since we have a lot of PII/PHI and financial informaiton - Gusto is about 600 employees today and we invest in lots of internal tools for non-engineering functions, an enterprise data warehouse, and security. - We are also looking into what the future of payroll looks like. A personal goal of mine is to rid the world of the concept of a "payday". Why shouldn't employees get paid whenever they want for the work that they did? https://techcrunch.com/2018/06/21/gusto-flexible-pay/ https://techcrunch.com/2018/06/21/gusto-flexible-pay/ - Technical debt: When you grow as fast as Gusto does, you inevitably accrue technical debt and it's important that we carve our engineering resources to keep that low. There's a lot more in there, but hopefully it gives you a sense of how 100 engineers can add up pretty quickly!
- itronitron 8y ago>> rid the world of the concept of a "payday" you might face some ingrained cultural barriers with this as the higher-status the job the more infrequent/delayed the payday... day-laborers are paid at the end of the day, many blue-collar jobs are paid weekly or bi-weekly, and white-collar jobs are typically paid monthly
- lmeyerov 8y agoWe use gusto across multiple jurisdictions where tax laws change every year and our bookkeeper our employees put them through funny circumstances. I've been impressed by how many problems they've made invisible (just notify us) or we sent over and they handled. Cannot say the same about other folks we use here (ex: zenefits caused multiple lapses in coverage).
- dpcheng2003 8y agoI used to be a PM at Gusto so I can add to Eddie's answer. As Eddie mentioned, it's non-trivial to keep the existing applications running as well as they do. That being said, a non-trivial amount of time/resources is spent making an already amazing product that much better. For example, my friends just launched a new product that lets you pick your payday (https://techcrunch.com/2018/06/21/gusto-flexible-pay/ https://techcrunch.com/2018/06/21/gusto-flexible-pay/). To get this to work, there's a lot of data science involved to make sure you're not exposing Gusto to financial risk (it's effectively lending money). Since taxes are withheld with every paycheck, the payment flows associated with flexible pay become incredibly challenging. They're an amazing team. Go Eddie!