Staff Fullstack Software Engineer

Staff Fullstack Software Engineer (Onebrief)

Join Onebrief to tackle complex technical challenges and help shape the future of the platform. You will set technical direction, coordinate cross-squad strategy, and mentor engineers across teams in a high-growth B2B SaaS environment.

Responsibilities

• Define and drive technical strategy across multiple teams, identifying systemic gaps and proposing architectural directions.
• Establish and evolve engineering standards, including the use of AI-assisted development tools and code review practices.
• Mentor and elevate engineers across teams through high-quality code reviews, RFCs, and participation in technical discussions.
• Focus on high-leverage work and guide efforts where impact is highest.

Requirements

• 12+ years of software engineering experience with technical ownership spanning teams (not only projects).
• Demonstrated ability to set architectural direction at the org/platform level.
• Strong communication skills, including writing RFCs to achieve alignment and making trade-offs clear to non-technical stakeholders.
• Ability to make progress in ambiguity and bring others along.
• Comfort operating in complex technical and organizational problems.
• Fluency across the full stack with depth to navigate between frontend architecture and infrastructure trade-offs.
• Strong understanding of distributed systems, API design, and data modeling, including cloud-native infrastructure at scale.
• Active and sophisticated use of AI coding tools, with thoughtful, system-level reasoning about how they affect building, review, and code reasoning.
• Experience building in a squad/rotation-based model (or the instincts to thrive in one).

Nice-to-haves

• Experience in mission-critical or high-compliance domains (e.g., FedRAMP, SOC2, DoD).
• Experience with authentication and identity infrastructure at scale (e.g., OIDC, SAML, federated identity).
• Prior experience scaling a high-growth B2B SaaS through inflection points.
• Familiarity with event-driven architectures and async-first system trade-offs.