Signett

The web is about to gain a second interface

Today, websites are designed for people. Agents must interpret pages, hunt for controls, and imitate clicks to accomplish anything.

We believe that will change. Websites will expose their capabilities directly to agents: structured, testable interfaces that work alongside the human experience. WebMCP is an early step toward that future. Signett is building the developer platform around it.

Our goal is to make creating an excellent agent interface as normal as building an API or testing a user interface.

The foundational product already exists. Signett has a public TypeScript library, documentation, benchmarks, real-world integrations, a website, and a Chrome extension. You would not be joining to turn a slide deck into an MVP. You would be joining to discover what makes a promising product become something developers genuinely adopt.

See it at signett.ai.

The opportunity

You would be Signett’s first hire and would have unusual ownership over the product’s direction.

Your job is to run one loop repeatedly:

1. Find an external developer or team with a real reason to make its website agent-ready.
2. Work inside its codebase and ship the integration.
3. Identify what made the process difficult.
4. Fix that friction yourself—in the library, documentation, testing tools, or extension.
5. Publish what you learned so the next integration becomes easier.

You will move between engineering, product discovery, developer experience, and early distribution. There will be no handoff between those functions because, initially, you are the person connecting them.

The work could help establish how developers build and test agent interfaces for the web. It could also reveal that our present assumptions are wrong. Either outcome requires someone who cares more about finding the truth than defending the existing product.

The first 90 days

The initial targets are deliberately concrete:

• Five external teams attempt the 30-minute integration.
• At least three ship a real workflow without founder intervention.
• Two remain active or request a paid capability such as shared history, CI, analytics, or evaluations.
• Two reference integrations and case studies become public.

By the end, we should know which part of Signett developers truly value—exposure, testing, reliable execution, the Inspector, evaluations, or something we have not yet recognized.

You may be a strong fit if you have

• Six to ten years of experience as a product-oriented full-stack or frontend engineer.
• Strong TypeScript, React or Next.js, browser API, and Playwright or Cypress experience.
• Built SDKs, developer tools, browser tooling, API infrastructure, or observability products.
• Personally helped developers adopt something through documentation, examples, workshops, open-source work, or direct integrations.
• Enough commercial instinct to find a design partner, lead the conversation, and turn the resulting work into a useful public case study.
• The judgment and autonomy to make progress without daily direction.
• Clear writing and demonstration skills in addition to strong engineering ability.
• 
  

Experience with WebMCP or MCP is helpful but not required. Curiosity and the ability to learn an evolving standard matter more. The WebMCP proposal is public at github.com/webmachinelearning/webmcp.

The anti-sell

Signett has a product, but it does not yet have proven product-market fit. Adoption is the open question, and answering it is the core of this role.

You should not join if:

• You want a role devoted entirely to writing code handed to you through a roadmap.
• You expect someone else to find users, conduct interviews, write documentation, or publish the work.
• You need a large team, established processes, or daily management to be effective.
• Your experience is primarily managing mature organizations rather than building from ambiguity.
• Your main strength is developer content without production software behind it.
• You want to research or train models rather than build browser-based products developers use.
• The uncertainty of an emerging standard makes you uncomfortable.
• You need the stability and specialization of a conventional engineering position.

.

This is not a comfortable job with a “founding” title attached to it. It is a chance to take a technically serious, public product and prove—or disprove—that it deserves to become an important company.

How we will start

We begin with a paid four-to-six-week project involving a real external TypeScript application, not a synthetic coding exercise.

The purpose is for both sides to experience the actual work: finding a useful integration, shipping it, learning from developers, and improving Signett. If the collaboration works and the evidence supports continued investment, the intended path is a permanent, full-time role.

The work is fully remote. Compensation, location, time-zone overlap, and the terms of the initial project will be discussed transparently before the process begins.