Software Engineer

About Bitwarden

Bitwarden is the trusted identity security leader for millions of users worldwide, empowering enterprises, developers, and individuals to securely manage and share sensitive information anywhere. Bitwarden makes it easy for all users to extend robust security across their devices with password management, secrets management, and passwordless and passkey innovations. The company is headquartered in Santa Barbara, California with team members located across the globe. Learn more at bitwarden.com. 

THE ROLE

As a Software Engineer on Bitwarden's Secrets Manager team, you will contribute to the design and development of the Secrets Manager application stack that lets developers, DevOps, and cybersecurity teams alike centrally store, manage, and deploy sensitive credentials. You'll build upon the core concepts of secrets, projects, machine accounts, and access tokens across the product suite.

This role is for an engineer early in their career who wants to develop deep expertise across a breadth of languages/frameworks. You will start with well-scoped work and grow into larger, more independent ownership, with senior engineers alongside you on design, review, and the parts of the system that take time to learn.

WHAT YOU WILL DO

• Feature Delivery: Build well-scoped parts of features across the API, the web client, and the SDK. Take on larger and more independent pieces as you grow into the codebase.
• Learning the Security Model: Work inside a zero-knowledge architecture and learn why it is built the way it is. Where a secret gets encrypted, what the server is allowed to see, and how a machine account proves who it is. Asking questions here is the job, not an interruption to it.
• Automated Quality: Write tests alongside your code, and help maintain the automated suites and CI/CD pipelines that keep the team shipping safely.
• Code Review: Take part in pull request review. Act on the feedback you receive, and read your teammates' changes as one of the fastest ways to learn a large codebase.
• Operational Support: Help keep services healthy in production. 
• Collaboration: Work closely with Product, Design, and your fellow engineers to understand what you are building and why, and raise questions and risks early.
• Documentation: Keep internal architecture notes, API contracts, and public open source developer documentation accurate as you work on the code they describe.