Founding Full-Stack Engineer

About the role

You will build the whole product, not a slice of it. On a given day you might ship a step in the connect widget, add an endpoint to the REST API, wire a new event into the webhook pipeline, and touch the edge proxy that terminates TLS. This is a small senior team, so the person in this seat owns features end to end and cares about how they feel for the SaaS teams that embed us and the end-users who connect a domain in about 30 seconds.

Responsibilities

• Build features across the stack: the embeddable connect widget, the console, the REST API, and the services behind domain detection, DNS record writing, and verification.
• Turn a raw domain into a working connection: detect the DNS provider, write the correct records, verify ownership, and hand off to the edge for HTTPS.
• Design and ship API endpoints and webhook events that integrators build against, and keep them stable once teams depend on them.
• Instrument the flow so we can see where a connection stalls, then close the gap before a customer files a ticket.
• Review other engineers' work and write the kind of code you would be happy to inherit.

Requirements

• You have shipped production software across frontend and backend and are comfortable owning a feature from the widget down to the service that writes DNS records.
• You are strong in TypeScript and Node, and you can read and work in Go where the edge and systems layers live.
• You understand how DNS, HTTPS, and reverse proxies actually behave, or you are the kind of engineer who will learn the details fast rather than guess.
• You write plainly, keep scope honest, and prefer a small correct change over a large clever one.

Bonus

• You have worked on developer-facing products where the API and the docs are the product.
• You have dealt with DNS providers or ACME certificate issuance before and know where the sharp edges are.
• You have built or maintained an embeddable widget that runs inside other people's sites.