Security Software Engineer

Requirements

  • 3+ years of software engineering experience
  • ,
  • You've built and shipped systems at scale, not just advised on them
  • ,
  • You own implementation end-to-end, from design to delivery
  • ,
  • Clear communicator who can work across teams without losing technical depth
  • ,
  • (Desirable) Proficient in Ruby on Rails
  • ,
  • (Desirable) Experience with IAM, authn/authz frameworks, or identity protocols (OAuth, SAML, OIDC)
  • ,
  • (Desirable) Familiarity with software supply chain security, secure SDLC, or AI/ML security risks
  • ,
  • (Desirable) You've worked somewhere where PII or sensitive data was the core product

What the job involves

  • Persona builds identity verification infrastructure — security isn't a layer we add later, it's core to everything we ship. When security fails at most companies, systems go down. At an identity verification company, real people's identities are compromised. The stakes here are different
  • ,
  • As AI tooling lets teams ship faster than ever and breaches make headlines every week, the gap between what gets built and what gets built securely is widening. The engineers who are working on closing that gap are more critical than ever
  • ,
  • This is a software engineering role first. Security curiosity matters; a dedicated security background doesn't
  • ,
  • The security team operates as a true generalist function. Right now that means:
  • ,
  • Designing and building IAM systems that enterprise customers use to manage PII across global teams
  • ,
  • Supply chain security as Persona's AI tooling and integrations expand
  • ,
  • Building secure, convenient internal tooling for engineers as we scale AI usage
  • ,
  • Small and senior by design. High ownership from day one — this isn't a team where your work disappears into a large org. The seniority of the team means you'd have direct access to experienced engineers invested in your growth
Back to blog