Developer Relations Engineer (Open Source / MCP)

About Manufact

Manufact (formerly mcp-use) builds the open-source SDKs and cloud infrastructure powering the Model Context Protocol (MCP) ecosystem. Our SDKs are used by thousands of developers to build MCP servers, agents, and ChatGPT Apps. We are YC S25, founder-stage, and moving fast.

We are hiring a Developer Relations Engineer in San Francisco to ship demos every day, speak at events, run partnerships with the rest of the dev tools world, and write the content that makes developers fall in love with mcp-use.

What you will own

Daily demos

Ship a cool demo every single day. Deep dives on features of the mcp-use SDK, walkthroughs of new product surfaces, short videos, working repos, X threads, GIFs. The kind of content that makes a developer stop scrolling and clone the repo. You will be the person who shows the world what mcp-use can actually do.

Speaking and events

Be on stage. Conferences, meetups, hackathons, podcasts, livestreams. AI Engineer Summit, MCP-themed events, partner workshops, university talks. We expect you to be a regular speaker at the events where MCP and AI builders show up, and to know everyone worth knowing in that scene.

Partnerships and ecosystem coordination

Run our collaborations with other dev tools companies. Cursor, Anthropic, OpenAI, Vercel, Zed, Replit, Linear, Stripe, every adjacent SDK and AI tool we should be cross-promoting with. You will coordinate joint demos, joint blog posts, joint launches, integration tutorials, and quarterly co-marketing pushes. This is real surface area: you own the relationships, the calendar, and the deliverables.

Writing

Blog posts, tutorials, deep technical guides, launch posts, X threads, LinkedIn essays. Manufact's voice on the internet runs through you. Frequent, high-quality, technically credible writing.

Open source community

Triage issues. Review PRs. Keep contributors unblocked. Be the person who makes mcp-use the most welcoming OSS surface in the MCP world.

Bridge to the MCP committee

Stay close to the official modelcontextprotocol/* maintainers and the broader spec community. Influence the protocol from the inside.

Who we want

You ship code AND ship content, in equal measure. Every week.

You are already in the MCP world. You have built MCP servers, contributed to modelcontextprotocol/*, used mcp-use, or shipped tools other MCP developers use. This is the strongest single signal.

You live on GitHub. Maintainership of an OSS project, meaningful PRs to repos you do not own, or stars on your own work.

You write and speak in public. A blog, an X account with real engagement, conference talks, a podcast, a YouTube channel, anything. You are comfortable with a camera, a microphone, and a stage.

You can run a partnership end to end. Organized enough to schedule a joint launch with another company's DevRel lead, kick off the engineering work, write the post, and ship on time.

Deep curiosity about LLMs, agents, and the agentic protocol stack. You read MCP spec changes the day they drop.

Smarter than the founders. We mean it.

Bonus points

You have spoken at a conference, run a meetup, or organized a hackathon.

You have shipped a ChatGPT App, Claude desktop integration, or Cursor extension.

You have maintained a Discord, OSS community, or large GitHub project.

You have a real X presence, blog, or YouTube channel.

You have strong opinions about Paul Graham essays.

Red flags

Pure marketing or non-technical DevRel. This role writes code.

No public GitHub footprint, no shipped projects.

Want to work remote.

BigCo experience with no side projects, no OSS, no community involvement.

Interview process

1. Tell us about things you have built. Send URLs: repos, posts, talks, demos. The bar is what you have made, not what is on your CV.
2. Send a short 2 to 3 minute Loom telling us about you and what excites you about MCP.
3. Intro call with the founders.
4. Take-home or OSS contribution. A real PR to one of our repos, or a small project we agree on.
5. Paid trial. A week or two working with the team in SF.

We expect you to have

Used the mcp-use library and skimmed our docs.

Built at least one thing involving MCP, even a weekend hack.

Strong opinions about how the agentic AI stack should look.

How to apply

Apply through Work at a Startup. Include:

Links to your GitHub, blog, X, talks, demos.

One sentence: the most interesting MCP server, agent, or AI tool you have built or used.

Your favorite OSS project that is not yours, and why.

If you have contributed to MCP in any form, flag it loudly.