Sr. Technical Writer

**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. This role owns the developer\-facing documentation for DNSid, top to bottom: the API reference, conceptual guides, integration tutorials, the developer portal, and the written specifications behind the standard. The Sr. Technical Writer translates a sophisticated protocol into documentation an engineer can act on immediately, and works closely enough with the engineering team to document features before they ship. This role also ensures that documentation is structured and published to be as useful to an AI tool retrieving context as it is to a person reading it. The Sr. Technical Writer will partner closely with the SDK and Integrations Engineers and the Developer Advocate on the DNSid rollout. This role reports to the Director, Software Engineering. **What You'll Do** * Write and maintain the complete API reference for the TypeScript, Python, and Go SDKs: method signatures, parameters, error codes, and annotated code examples * Author conceptual guides that explain the DNSid trust model, the agent lifecycle, the DNS record schema, and the verification flow for developers from AI, platform\-engineering, and identity backgrounds * Produce integration tutorials for each major framework, such as LangChain, CrewAI, the Microsoft Agent Framework, LlamaIndex, and the OpenAI Agents SDK, plus MCP servers, A2A, and edge runtimes, with working code samples validated against the current SDK * Own the DNSid developer portal end to end: information architecture, navigation, search, and the new\-developer journey from first landing to a first successful agent registration * Structure and publish documentation to be AI\-consumable: well\-formed llms.txt, machine\-readable API references, and content that surfaces accurately through AI coding assistants like Codex, Claude, and Cursor, since many developers meet DNSid through these tools before they ever open the portal * Help write the technical standards behind DNSid, working from the IETF draft and engineering notes * Maintain the changelog and release notes for each SDK release, turning engineering diffs into clear, developer\-facing impact statements * Document features before they ship by joining design reviews, reading PRs, and asking the questions that surface gaps early * Work with Developer Advocates so tutorials and guides reflect what developers actually find confusing, based on community feedback and support volume * Set the documentation style guidelines, templates, and review process, and keep them working as the integration surface grows * Keep every documentation code example validated in CI against the current TypeScript, Python, and Go SDKs, partnering with engineering on the setup, so examples never silently go stale as the APIs change * Version documentation clearly acro