Company Overview

IDMe is the next-generation digital identity wallet that simplifies how individuals securely prove their identity online. Consumers can verify their identity with IDMe once and seamlessly login across websites without having to create a new login and verify their identity again. Over 175 million users experience streamlined login and identity verification with IDMe at 22 federal agencies, 50 state government agencies, and more than 100 healthcare organizations. Over 600 consumer brands use IDMe to verify communities and user segments to honor service and build more authentic relationships. IDMe’s technology meets the federal standards for consumer authentication set by the Commerce Department and is approved as a NIST 800-63-3 IAL2 / AAL2 credential service provider by the Kantara Initiative. IDMe is committed to “No Identity Left Behind” to enable all people to have a secure digital identity. To learn more, visit https://network.id.me/.

IDMe is a full-time, in-office culture. Unless a specific job description explicitly states otherwise, all roles are on-site five days per week at one of our offices in McLean, VA; Mountain View, CA; New York City, NY; or Tampa, FL. Certain roles — such as field-based sales or other remote-by-design positions — may have different work arrangements as noted in their individual postings.

At IDMe, we embrace the thoughtful use of AI tools in our daily work and there are even occasions where we leverage AI in our hiring process. However, during the interview process, we want to understand your individual skills and experiences. Therefore, we have guidelines on how AI can be appropriately used during your application and interviews which can be found here.

Position Overview

This Staff Engineer role sits at the intersection of engineering, testing, AI evals, and developer experience. You will own the architecture and strategy for the evaluation frameworks, automation tools, and testing infrastructure that give IDMe engineering teams the confidence to ship quickly and safely across functional, end-to-end, LLM/eval, and security-focused testing practices, as well as the CI/CD quality gates the org depends on.

It requires deep engineering rigor, the judgment to set testing strategy for complex, asynchronous, event-driven systems, and the ability to build tooling and standards that other teams adopt widely. You will raise the quality bar across the engineering org, mentor senior and mid-level engineers, champion AI-assisted testing practices, and partner directly with engineering, product, and security teams to embed quality into every stage of development for a platform that verifies the identity of millions of users.

Key Responsibilities

Own Test Architecture & Strategy: Set the architecture and long-term strategy for automation frameworks and testing infrastructure (Playwright, Python, Jest, API automation) across IDMe's services, and ensure comprehensive, reliable coverage org-wide.
Lead Testing Strategy for Distributed Systems: Define end-to-end and integration testing strategy for complex, asynchronous, event-driven, and eventually-consistent systems, including workflow orchestration platforms such as Temporal.
Drive Testing-in-Production as an Org Standard: Build and champion canary deployments, progressive/phased rollouts, synthetic monitoring, and automated rollback triggers to validate real-world behavior safely before full release.
Own Security-Focused Test Automation: Set the standard for testing authentication/authorization flows (OAuth 2.0, OIDC), RBAC/ReBAC, secrets management, and tenant isolation.
CI/CD Quality Gates: Integrate automated testing into CI/CD pipelines (e.g., GitHub Actions) org-wide to give every team fast, reliable feedback.
Drive AI & Evals Culture: Build robust evaluation pipelines for AI-assisted features and LLM agents, while applying AI tools to accelerate test authoring, test plan generation, and code review across the org.
Cross-Team Collaboration: Partner with Security, Platform, and Product teams as a testing strategist, advising on testable code structure, coverage gaps, and quality checks throughout the development lifecycle.