Software Engineer

About Us

Fieldguide is establishing a new state of trust for global commerce and capital markets by automating and streamlining the work of assurance and audit practitioners — specifically in cybersecurity, privacy, and financial audits. We build software for the people who enable trust between businesses.

We're based in San Francisco, CA, and we're backed by Goldman Sachs Alternatives, Bessemer Venture Partners, 8VC, Floodgate, Y Combinator, and more. Over 50 of the top 100 accounting and consulting firms trust Fieldguide to power mission-critical work.

Role Summary

This role owns quality and automation for large enterprise deployments. You'll work closely with customers and our internal engineering team to develop a world-class QA Function that’s built from an agent-first lens.

We're building our quality and automation capacity around agentic tooling, and this role sits at the center of that: using agents to take on the repetitive work of finding, reproducing, and resolving issues, strengthening our internal testing, and keeping our SaaS and PaaS environments consistent. You'll also work directly with the customer on how issues get reported and resolved, and own the reporting that shows where quality is heading.

We're hiring across all levels. Depending on your experience and what you're looking to own, you may join executing against this scope, owning the customer's quality experience end to end, or setting quality and automation standards across Engineering. We'll calibrate seniority during interviews based on scope and demonstrated experience.

What You'll Own

• Keep environments consistent across our SaaS and PaaS deployments, so behavior a customer sees in one place matches everywhere else and configuration drift doesn't become a defect

• Build our automation capacity for handling bugs using agentic tooling including triage, reproduction, and routing that runs without a human in the middle

• Use agentic tools to resolve bugs yourself, shipping fixes rather than filing tickets and waiting

• Run bug bashes on new features before they're released, and make the practice repeatable enough that other teams adopt it

• Own bug reporting and communication: severity-weighted trends, hotspots, and a clear read on where quality is heading that engineering leadership and the customer both trust

• Work closely with the customer to integrate deeply with their processes and improve how they report issues, validate fixes, and decide something is ready for customers

• Improve our internal automated testing: coverage where it pays, CI signal people believe, and less flake