Growth Engineering is all about growing the user base. Of course, to grow a user base, the product quality is important, but there should also be some effort (lots of effort, actually), to persuade the user to try using the product in the first place.
Many security teams operate like QA teams of yore. Testing was mostly absorbed into standard engineering practice - security is next.
At Gusto, teams have a lot of autonomy on how they work. Teams can define their own processes. Over the past year, my team has developed a somewhat unconventional method that has resulted in better productivity, outcomes, and team happiness.
How does a payroll engineering organization give the green light for a basal change to their tax system when the consequences reach many domains, features, and teams? With a decision matrix we were able to break down our options, clearly compare solutions, and find a path forward.
-------------------------------------------------------------------------------- Hello! My name is Jordan and I’m a software engineer on our Design Systems team at Gusto. Since joining Design Systems I’ve found it super helpful to use VSCode especially when working with React and
Introduction Today we will be looking at the Gusto Guice Shop CTF event. This event uses the OWASP Juice Shop [https://github.com/juice-shop/juice-shop]vulnerable web application to learn how to identify and exploit common web application
My two months as a designer and takeaways from a cross-functional rotation - including why it might be right for you Image by Peter Tarka [https://www.behance.net/gallery/93834339/Illustrations/modules/542177733] How it started I’
