Lead Software Engineer (Provider/Business Unit Portals)

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 Lead Software Engineer on Bitwarden’s Provider/Business Unit Portals team, you will lead the design and development of both the Provider and Business Unit Portals. The former is built to service managed service providers (MSPs) and resellers who administer Bitwarden organizations on behalf of separate, external customers. The latter is is built for a single company's own administrators to manage multiple Enterprise organizations that all belong to that same company (e.g., different business units, subsidiaries, or departments). Both portals give administrators a single, centralized experience for creating and managing multiple Bitwarden Enterprise organizations at scale.

This Lead Software Engineer role is hands-on and does not carry any expectations for people management. You'll stay close to the code while driving architecture, technical direction, and complex, high-impact engineering problems. As our India Product Engineering organization grows, you'll help shape its engineering practices and also navigate opportunities to mentor and elevate other engineers through technical leadership.

• End-to-End Delivery & Ownership: Design, build, test, deploy, and operate secure, performant services and applications for the Provider and Business Unit Portals. You are accountable for these services end to end, including the parts you did not personally write.
• Engineering Standards and Automated Quality: Set the bar in pull request review and own the team's conventions for testing, error handling, API design, and secure coding, keeping automated suites, integration harnesses, and CI/CD pipelines strong enough that manual testing is never the safety net. Maintain the archit