Senior Software Engineer (Autofills Coverage)

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 Senior Software Engineer on the Autofills side of this team, yyou 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 teammates and in close partnership with the wider Autofill team. WHAT YOU WILL DO • End-to-End Delivery & Ownership: Own substantial pieces of the team’s work from design through production: the site-specific rule dataset and its tooling, theautomation that continuously checks autofill on real websites and turns failures into fixes, and the benchmarking harness that measures autofill’s performance impact and responsiveness. Stay with your work once it is live. • Automation at Scale: Design browser automation that runs reliably against real, constantly changing websites. Handle flakiness, dynamic content, and anti-bot measures, and turn results into actionable signal rather than noise. • Performance Measurement: Build and improve lab-based benchmarks that measure how autofill affects page responsiveness, rendering, and memory. Treat measurement as engineering: control noise, question surprising numbers, and make sure a metric means what it claims before anyone acts on it. • Engineering Standards and Automated Quality: Build and maintain the validation, versioning, and CI checks that catch bad data and misleading results before they ship. Review teammates’ pull requests with care and invite the same scrutiny of your own. Keep documentation and contribution guidance in our open source repositories clear. • Decoupled Architecture and Service Boundaries: Design the dataset so it can evolve independently of client release cycles, with backward compatibility across supported client versions. Keep test and measurement tooling cleanly separated from the product code it exercises. • Technical Mentorship: Pair on hard problems, share what you learn, and help SDETs and newer engineers find their footing in a security-sensitive codebase. • AI-Assisted Development: Use AI coding assistants effectively in daily engineering and exercise judgement about where they help and where they do not. Build assistive tooling that speeds up rule authoring, with a human always reviewing and approving the result. • Operational Stewardship: Triage autofill defects from support, internal reports, automated checks, and benchmarks. Fix what belongs to the team and route the rest to the right owner with clear attribution. • Cross-Functional Partnership & Collaboration: Partner closely with the Autofill team, Product, Security, and SDET teammates to design and validate solutions before implementation begins. WHAT YOU BRING • Overall Experience: 5–9 years building and operating production software, with a track record of owning substantial, technically demanding work end to end as an individual contributor. • Technical Stack: We hire for strength and mindset, not an exact tool match. You should be strong in at least one of browser automation or front-end performance, and keen to grow into the other. • Expertise – TypeScript or JavaScript, and Node.js – The DOM, HTML forms, and CSS selectors, including how real-world pages diverge from spec – Browser automation with Playwright, Puppeteer, Selenium, or Cypress, or front-end performance analysis with Chrome DevTools, Lighthouse, and Core Web Vitals – CI/CD with GitHub Actions or a similar platform • Experience – Shell scripting and Docker – Data validation with JSON Schema or similar, and maintaining versioned datasets or configuration – Reading performance data: percentiles, run-to-run variation, and telling a real regression from noise – Dashboards and alerting with Datadog, Grafana/Prometheus, New Relic, or similar – AI-assisted development, preferably Claude Code • Familiarity – Browser internals such as rendering, garbage collection, the Chrome DevTools Protocol, and Performance APIs (PerformanceObserver, Long Tasks, User Timing) – Browser extension architecture (Manifest V3, content scripts, extension messaging) – Front-end frameworks and tooling such as Lit, React, RxJS, and webpack • T-Shaped Engineering Mindset: Depth in one area and genuine range across others. You ask why, not just what; you treat a flaky test or a surprising number as something to understand rather than hide; and you pick up new tools quickly. • Practical experience with containerized environments, automated test frameworks (unit, integration, and end-to-end), CI/CD pipelines, and observability tooling. • Secure Coding: Familiarity with zero-trust and zero-knowledge security architectures, encryption standards, and threat-modeling methodologies, and an understanding of why vetted, human-authored rules and heuristic-based autofill carry different security postures. • Collaborative Spirit: A highl