Software Engineer (Trust Service Team)

Join <ID.me>, a leading identity verification platform, as a Software Engineer III. In this role, you will work on a high-throughput, correctness-critical Java backend service. You will design and evolve REST APIs, write precise database queries, and ship features used at production scale. You will also own the trust inspection data model and the REST API contract, ensuring correctness, reliability, and performance. Additionally, you will collaborate with cross-functional teams and contribute to the company's AI-first engineering culture.

• Design, implement, and evolve the Trust Service API end-to-end, from API contract design through database query authoring and production deployment.
• Own the trust inspection data model and the REST API contract that downstream consumers and SDKs bind to, making deliberate decisions about backwards compatibility and versioning.
• Ensure that trust reads and writes are correct under concurrent load, identify and resolve performance bottlenecks in database query plans, and own reliability improvements.
• Deep comfort with relational databases, writing complex SQL queries, reasoning about query plans, and working within a production database schema
• Proficiency with AI-assisted development tooling (e.g., Claude Code, Cursor) and commitment to an AI-first engineering culture that leverages these tools to maximize code quality, test coverage, and engineering velocity
• 4+ years of professional software development experience with a strong emphasis on backend service engineering, preferably in Java or another JVM language
• Bachelor's degree in Computer Science, Engineering, or a related field (or equivalent practical experience)
• Experience designing and versioning REST APIs backed by OpenAPI specifications
• Experience with modern Java (21+) and its type-safety features — records, sealed interfaces, pattern matching — applied to real production codebases
• Familiarity with graph or highly relational data models: understanding entity relationships, traversal patterns, and the tradeoffs of different read/write shapes
• Comfort reasoning about identity and trust decisions: what it means for a credential to be verified, how different verification methods vary in reliability, and how expiration or decay affects downstream trust
• Experience with identity standards such as NIST 800-63-3, OAuth2, or OpenID Connect
• Strong track record of shipping well-tested, production-quality backend features with careful attention to failure modes, rollback safety, and backwards-compatible schema changes
• Startup or high-growth company experience with a strong bias toward ownership and execution