A complete application in a minute
Tailored resume and cover letter, ready to send.
Gusto is seeking a Senior Staff Software Engineer on the Agent & Partner Experiences team in San Francisco to be a technical leader shaping the platform. You’ll be hands-on in our complex Ruby on Rails codebase and coach others to deliver a high-quality developer experience.
You’ll bridge the API and AI worlds, design API contracts and agent-facing tools, and help developers embed payroll into their software.
Bar Raiser: You’ve spent time mentoring and raising the technical bar for the entire organization. Others look to you for guidance on how to tackle ambiguous problems and handle competing prioritiesTechnical Expertise: You are a Ruby and Rails expert. You have navigated massive Rails applications, worked with Ruby across multiple codebases, and are comfortable working at multiple layers of abstractionPlatform Thinker: You’ve designed and built platforms and public-facing APIs, and have a strong understanding of how to build for reliability and performance at scaleExperience: 12+ years of professional software development experience. You have been a technical owner for organization-wide engineering initiatives and have played a role in scaling engineering organizationsEffective Communicator: You think in terms of business priorities and know about how to orient your team around the right technical goals for the business as well as how to convey technical constraints and needs to business leadersPayroll domain experience: Payroll, tax or fintech experience is a real head start. It’s also learnable, and we’ll teach itAgent facing tooling: Experience designing interfaces consumed by a model - MCP servers, tool and function definitions or an integration path for AI providers. We care how you think about turning an API into a navigable tool surfaceGraphQL at scale: You’ve been a client of GraphQL - writing efficient queries, building the query construction and data mapping layer around them, and reasoning about performance when you don’t own the resolvers. You have enough schema fluency to influence the design of APIs other teams own