Senior Software Engineer (Onboarding & Activation)

Bitwarden promotes better internet security and safety with the leading open source password management solution for individuals, teams, and business organizations. Our philosophy on security is that “we are all in this together” – we continue to offer a full-featured free version of Bitwarden so that everyone can be protected with strong password management. We also provide enterprise-grade solutions to some of the largest companies in the world, and will continue to innovate in the identity and authentication market as the world starts to grow beyond passwords. Read more on the Bitwarden blog. 

Onboarding & Activation owns the user's journey from first run to paying customer: the onboarding and activation experience that proves the product's value, and the client-side surfaces that convert it. This spans guided setup, trial initiation, upgrade paywalls and plan selection, and the user-facing subscription, plan, payment-method, and invoice experiences. As the Senior Engineer on this team, you'll own the back-end logic that sits behind those surfaces: trial state and eligibility, activation/onboarding progress tracking, and paywall/entitlement gating, working in close coordination with the Billing team, who own the core subscription, payment-provider, and licensing systems this team's flows ultimately depend on. This is revenue-critical, externally coupled work: a mistake here can let a user through a paywall they shouldn't pass, or lock out one who should have access. You will work on a globally distributed, asynchronous team that relies on written clarity and a bias to action.

• →Build and maintain the back-end logic for trial initiation and lifecycle (start, expiration, conversion, extension) and the eligibility rules that decide when a user can start or re-start one.
• →Build and maintain the entitlement/gating logic behind upgrade paywalls, ensuring what a user is shown and permitted to do stays correctly in sync with their actual plan and trial state.
• →Design and maintain the back-end services and data model tracking a user's onboarding and activation progress, in coordination with the client-side guided-setup experience.
• →Coordinate closely with the Billing team on the API contract for subscription, plan, and licensing data this team's flows consume, and flag any change that could affect correctness on either side.
• →Design clean, testable services with explicit success/input-error/conflict/unhandled outcomes, avoiding silent failures anywhere a decision affects what a user can access or pay for.
• →Author safe, backwards-compatible data access and schema changes as this team's own data model (trial state, onboarding progress) evolves.
• →Uphold the same payment-security and privacy standards as the rest of the org: no raw card data, secrets, or PII in this team's systems or logs.
• →Review pull requests and raise back-end quality; partner with front-end, Product, and AppSec.

• Experience Level: 6-10 years in back-end software engineering, with the ability to own services and event/state-transition logic with minimal guidance. C#/.NET (ASP.NET Core) strongly preferred; strong experience in Java, Kotlin, Go, or a similar statically-typed stack, with willingness to ramp onto .NET, is acceptable.
• Correctness and Security Rigor: Experience with correctness-critical state and event handling (e.g., idempotent processing, explicit success/error/conflict handling, no silent failures) in systems where a mistake affects what a user can access or pay for, plus sound judgment around not exposing payment data, secrets, or PII.
• Relational Data Modeling: Strong SQL skill and the judgment to make safe, additive, backwards-compatible schema changes.
• Self-Direction and Collaboration: Drives work forward with minimal oversight, and collaborates effectively across time zones on a distributed, asynchronous team, defaulting to written clarity.
• Domain and Integration Experience: Experience with subscription, trial, or entitlement/feature-gating systems; comfort integrating with or consuming an API contract owned by another team.
• Engineering Practices and Tooling: Feature-flagged rollouts (LaunchDarkly or similar) for staged/gated features; comfort in a large, high-traffic monorepo with shared ownership.

We are committed to fostering an inclusive workplace where everyone can do their best work. We welcome applicants from all backgrounds and make employment decisions based on skills, experience, qualifications, and business needs.