Developer Advocate

CUSTOMDOMAIN™; Oregon (WI); On-site; USD 70,000 - 120,000; Full time

Job summary

CUSTOMDOMAIN™ is seeking a documentation-focused engineer to own developer storytelling for our REST API, embeddable connect widget, and MCP server. You’ll build sample apps that demonstrate end-to-end integration and make complex topics approachable for a 2am coding session.

You’ll also serve as the honest voice from the community, surfacing confusing areas and driving documentation improvements that reduce friction for users.

Qualifications

• Able to write clear developer documentation and sample code.
• Experience documenting REST APIs and embeddable widgets.
• Ability to explain DNS, TLS and webhooks in plain language.

Responsibilities

• Write and maintain docs for REST API, widget, webhooks, and MCP server.
• Build sample integrations and SDK guides end-to-end.
• Create quickstarts developers can complete in one sitting.
• Engage with the developer community in public channels.
• Translate technical concepts into trustworthy, developer-friendly content.

Skills

Write code and prose

REST APIs documentation

Developer docs experience

Tools

SDK guides

Job description

Our users are developers dropping a widget and an API into their own product, so the docs, the examples, and the SDKs are a large part of whether they succeed. You will own that experience. You will write documentation that a developer can follow at 2am, build the sample apps that show the connect widget and the REST API working together, and make sure the MCP server is something an AI agent can actually use. You will also be the honest voice from the community back into the team when something is confusing.

What you will do

• Write and maintain the docs for the REST API, the embeddable connect widget, the webhooks, and the MCP server, including quickstarts a developer finishes in one sitting.
• Build and keep working the example integrations and SDK guides that show a real domain getting connected end to end.
• Produce guides for the moments that trip people up: verifying ownership, handling apex domains, reacting to drift webhooks, and testing before going live.
• Run the developer community: answer questions in public, collect the recurring friction, and bring it back to engineering with specifics.
• Write about how the edge, TLS, and DNS pieces fit together so integrators trust what is happening under the widget.

What we are looking for

• You can write code and write prose, and you hold both to a high bar.
• You have built with REST APIs and embeddable widgets and you know what good developer docs feel like from the receiving end.
• You explain DNS, TLS, and webhooks in plain language without dumbing them down.
• You like being in public with developers and you follow through on the friction you surface.

Bonus

• You have written SDKs or docs for a developer-facing product that people actually adopted.
• You have worked with MCP or built tooling for AI agents.
• You have a track record of talks, writing, or community work that developers found useful.