Software Engineer; Frontend; Access Management

About Cerby

At Cerby , security is everyone's business.
Cerby extends your security perimeter to include your disconnected applications, providing identity automation and eliminating manual processes. It's one of the biggest blind spots in enterprise security, and we're the team closing it. If you want to work alongside the team solving one of the hardest, most overlooked problems in security, you're in the right place.
Founded in 2020, Cerby is backed by leading investors and trusted by enterprises across the globe.

At Cerby, software engineers are at the heart of driving technology and product innovation. As the Staff Software Engineer for frontend on the Access Management team, you set the technical direction for the surfaces our customers touch every day and you are accountable for the decisions that outlive any single project.

In this role, you will collaborate with cross-functional teams while owning the quality, scalability, and security of the platform. You will help lead and drive a security-first engineering culture, enhance the product's user experience, and maintain high standards of software delivery. You are also expected to embrace AI as a core part of how we work, actively exploring and incorporating AI tools and practices into your daily development workflow to improve team efficiency and accelerate impact.

• Set Technical Direction: Own the multi-quarter architectural roadmap for the team’s frontend. Decide what we build, what we buy, what we deprecate, and what we deliberately leave alone - and write down the reasoning so the next engineer inherits the decision, not just the code.
• Own Frontend Security: Threat-model anything that touches credentials or session state, and treat third-party dependencies as part of the attack surface, from client-side risks through to CVE patching.
• Raise the Engineering Bar: Define and enforce the standards - architecture review, testing strategy, performance budgets, accessibility, code review norms - and make them stick through tooling and automation rather than good intentions.
• Lead AI Adoption as a Discipline: Establish how the team uses AI in day-to-day development - where it accelerates real work, how output gets reviewed, what guardrails apply to security-sensitive code. Use AI to accelerate documentation (runbooks, ADRs, onboarding guides, post-mortems) so the team spends its time on the deep technical conversations that actually transfer expertise. Share learnings openly, including the failures.
• Own Production Quality: Instrument the frontend with well-designed telemetry and observability - metrics, traces, structured logs - so that regressions in performance, reliability, and user experience are caught by data rather than by customers.
• Finish Migrations: Lead framework upgrades, refactors, and deprecations from proposal through to the last call site removed, with measurable outcomes. Staff engineers are the reason a migration completes instead of leaving the codebase in two states forever.
• Remote
  
  Collaboration:
  
  Operate effectively in a remote-first environment, defaulting to written, asynchronous, high-signal communication across time zones.

• Experience:
• 8+ years of professional software engineering experience, with deep focus on building and scaling SaaS applications.
• Prior experience at Staff, Principal, or equivalent scope - technical leadership of an area without direct reports.
• Track record of leading multi-quarter architectural efforts to completion, with outcomes you can describe concretely.
• Prior experience developing and maintaining distributed applications.
• Experience mentoring senior engineers and conducting security-first code reviews.
• Technical Expertise:
• Experience with React and Type Script, including building and scaling Single Page Applications for high-performance production use.
• Experience designing, consuming, and optimizing REST APIs with efficient data fetching, caching, and invalidation strategies.
• Experience owning a design system or component library end to end - API design for components, versioning, adoption, and deprecation across consuming teams.
• Experience with tooling at scale: workspace management (PNPM or equivalent), build orchestration, dependency graphs, and release/versioning strategy.
• Deep knowledge of frontend security best practices and the ability to threat-model a feature before it is built.
• Testing strategy, not just test…