Sr. Software Engineer (SDK & Integrations)

Summary / Objective
IDIL is building DNS-native identity infrastructure for AI agents and other non-human identities: a durable, governance-backed domain name that serves as an agent's foundational identity. The Sr. Software Engineer (SDK & Integrations) builds the SDK layer that makes DNSid real for developers: producing production-grade TypeScript, Python, and Go libraries, plus the integrations that connect DNSid to the frameworks and infrastructure where agents actually run.
https://dnsid.ai/
This role sets technical direction and keeps libraries current as the ecosystem evolves. Core responsibilities include building and hardening integrations across every major touchpoint, and collaborating with Developer Advocates to ensure each deliverable maintains the high code quality, robust documentation, and exceptional developer experience required for a successful rollout. In this capacity, the Sr. Software Engineer (SDK & Integrations) works in close partnership with the Developer Advocate and Technical Writer for the DNSid rollout.
The Sr. Software Engineer (SDK & Integrations) reports to the Director, Software Engineering.
What You'll Do
Design, build, and maintain the official DNSid SDKs in TypeScript, Python, and Go: agent registration, DNS TXT record publication, lifecycle state management, and cryptographic verification flows
Write and ship production-grade integrations for the AI agent frameworks developers use, such as LangChain, LangGraph, LlamaIndex, CrewAI, the Microsoft Agent Framework, and the OpenAI Agents SDK, and maintain them as those frameworks evolve
Contribute code upstream to those third-party frameworks and tools, landing native DNSid support where developers already build, in partnership with the Developer Advocate
Build edge-server middleware and plugins for edge runtimes like Cloudflare Workers, Fastly Compute, and Vercel Edge that enforce DNSid verification at the request boundary
Build the MCP and A2A integrations so an agent's DNSid identity carries correctly from one agent to another
Provide secure key-lifecycle abstractions in the SDK, covering generation, storage, rotation, and revocation, that stay cryptographically agile across the runtimes developers deploy to
Create reference implementations and sample applications that demonstrate the full DNSid lifecycle, from registration and delegation through verification and revocation, in realistic agent scenarios
Engineer developer tooling that speeds adoption: IDE plugins, AI skills, CLI utilities, and agent-native extensions
Build local DNS mocking utilities and test infrastructure so developers can validate DNSid-enabled agents in CI without live DNS records or resolver dependencies.
Write integration tests, conformance suites, and CI pipelines that validate SDK behavior against the IETF draft specification, and publish to npm and PyPI and release Go modules through the Go module proxy, with semantic versioning, changelogs, and deprecation policies
Help shape the technical standards behind DNSid, turning insights gained from building the SDKs into clear written specifications
Triage community issues and pull requests on GitHub, holding a high bar for API stability and backward compatibility, and evaluate new frameworks and edge runtimes for integration priority based on adoption signals
Actively models and promotes Identity Digital's core values through day-to-day interactions, behaviors, and decision-making
Other duties as assigned

Who You Are / What You Bring
5+ years of professional, commercial software engineering, with a track record of shipping and maintaining production libraries or SDKs
Bachelor's degree in a relevant field or equivalent experience
Fluency in TypeScript and Python, and working proficiency in Go sufficient to own a production Go module
Solid understanding of DNS internals: zone files, TXT record syntax, TTL semantics, DNSSEC basics, and resolver behavior
Hands-on experience with HTTP/1.1 and HTTP/2 mechanics, including TLS and request authentication (OAuth 2.0, OIDC, mTLS)
Direct experience building with at least two AI agent frameworks (those listed above, or comparable)
Familiarity with MCP or A2A, or a demonstrated ability to implement against an evolving IETF-style draft
Experience writing middleware or plugins for a major edge runtime
Strong API design instincts: naming, error handling, extensibility, and the gap between what an API allows and what it makes easy
Experience publishing open-source packages with automated CI/CD, semantic versioning, and public changelogs
Comfortable reading IETF RFCs and translating them into working code
Familiarity with the cryptographic primitives used in identity protocols: key pairs, JWTs, JWK Sets, ES256 and Ed25519 signatures, and certificate chains
Ability to travel as needed
Ability to work across time zones as part of a global organization as needed

Preferred Qualifications
Prior experience contributing to or implementing against an IETF draft standard or W3C specification
Experience with SPIFFE/SPIRE, WebID, or other machine-identity or decentralized-identity systems
Familiarity with DNS operator APIs for programmatic record management, including Identity Digital's
Active contributions to open-source AI agent framework repositories or edge-runtime ecosystems
Experience with WebAssembly (WASM) as a cross-runtime deployment target for SDK components

Location: Remote
This position is open to candidates residing in the following states only: AZ, CA, CO, DE, MD, MA, MO, NJ, NV, NY, NC, OR, OK, PA, SC, TX, UT, VA, and WA.
Physical Requirements
Prolonged periods of sitting at a desk and working on a computer
Must be able to lift up to 15 pounds at times

Salary Range
The U.S. base salary range for this full-time position is $150,000 - $180,000 (flexibility based on experience) plus benefits as described below. In addition, the successful candidate will be eligible to receive other compensation from time to time in the form of discretionary and/or nondiscretionary bonuses and long-term incentive plan. Actual compensation will be influenced by a candidate's qualifications, internal employee equity considerations, and location. We will not ask for information about a candidate's current or past compensation for purposes of developing an offer of employment.