Software Development Engineer In Test

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. 

As a Software Development Engineer in Test (SDET) on Bitwarden’s Autofill Coverage team, you will help make autofill work reliably on the sites people actually use, and keep it fast and unobtrusive as the product evolves. Autofill is the Bitwarden capability that fills logins, payment details, and identities into web forms across browsers. The Autofill Coverage team maintains and expands a curated dataset of site-specific autofill rules, builds automation that continuously checks autofill across popular websites, and builds lab-based measurement of autofill’s performance in the browser. Every engineer on the team works across all of this, so we value curiosity and range over a perfect match to any single tool. This is a hands-on role. You will spend your time writing, reviewing, and shipping code, alongside your teammatesand in close partnership with the wider Autofill team.

WHAT YOU WILL DO

• UI Automation: Build and maintain browser automation that checks autofill across popular real-world websites and purpose-built test pages. Keep suites stable as sites change, with reliable locators, sensible waits, and flakiness fixed at its root.
• Performance Testing: Run, extend, and maintain lab-based benchmarks that measure how autofill affects page responsiveness, rendering, and memory in the browser. Set up runs, review results, and investigate numbers that look wrong.
• Trustworthy Results: Make sure test and benchmark results can be relied on. Confirm that two runs did the same work before comparing them, and flag misleading metrics before anyone acts on them.
• Test Scenarios: Build and maintain test pages that recreate tricky real-world patterns, such as dynamic forms, shadow DOM, and iframes, so they can be tested repeatably.
• Failure Triage: Reproduce autofill failures found by automation, support, or internal reports. Document them clearly, hand dataset fixes to teammates, and route the rest to the right owner.
• Reporting and Observability: Publish results to dashboards, set up alerting on regressions, and report coverage and trends on a regular cadence.