Builder in Residence, Ghost

Tiger Data•San Francisco, CA

4d•Remote

About The Position

We're hiring a Builder in Residence for Ghost, our ephemeral, forkable, MCP-native Postgres for agents. Ghost is the database that fits the way agents actually work: spin one up in a tool call, fork it for testing, throw it away, do it again. Claude Code, Cursor, and other AI coding tools are first-class users. This is a growth role with two centers of gravity: building and community. You'll be Ghost's most prolific user in public, and the voice that explains what you've built and why developers should care. The output is sample apps, reference integrations, and runnable demos, paired with public talks, blog posts, tutorials, and videos that get them in front of the right audience. You'll work closely with Ghost Engineering and Product, Marketing, and the broader Developer Relations function. We're hiring for the strongest candidate, not a specific level. We'll match title and compensation to the body of work you bring. This role is based in the San Francisco Bay Area, we want this hire on the ground with other AI builders.

Requirements

Demonstrated experience shipping public software, whether through open source projects, side projects, integrations, or developer-facing work at a previous company. We need to be able to read your code.
Comfort with PostgreSQL. You don't need to have written a query planner, but you should know what an index is, what a transaction is, and how to debug a slow query without panicking.
Hands-on experience with the modern agent stack. You've used Claude Code or Cursor for real work. You have opinions about MCP. You've built something with an LLM in the loop and felt the rough edges firsthand.
Strong technical writing across formats: blog posts, tutorials, READMEs, and longer-form pieces.
Bias to ship over polish. A working v1 on Monday beats a polished v3 on Friday, and you can tell which is which.
Thoughtful use of AI tools to accelerate building, research, and content iteration while maintaining technical rigor and accuracy.
Are not based in or able to relocate to the San Francisco Bay Area.

Nice To Haves

A track record of maintaining open source projects, even small ones, with real users and contributors.
An existing audience or following in the AI developer community, on GitHub, X, YouTube, or Discord.
Previous experience as a software engineer, Developer Advocate, or solutions engineer at an infrastructure or developer tools company.
Familiarity with the broader agent and AI tooling ecosystem: vector databases, embedding models, agent frameworks, evaluation tools, and the trade-offs between them.
Experience at early-stage or rapidly scaling companies where scope was ambiguous and ownership was real.

Responsibilities

Reference implementations: shipping sample apps that demonstrate what Ghost uniquely enables. Agent memory that persists across sessions. Forkable preview databases per pull request. Ephemeral Postgres per end-user. You pick what to build, you build it, you publish it.
Integrations and the public GitHub: maintaining a growing set of integrations with Claude Code, Cursor, Codex, MCP servers, and agent frameworks like Mastra, LangGraph, and the Vercel AI SDK. When a new agent tool ships on Tuesday, you have a working Ghost integration by Thursday.
Technical content tied to your builds: the posts, READMEs, tutorials, and videos that bring each thing you build to a wider audience. Code first, prose second. Short, runnable, no fluff.
Broader Ghost storytelling: the writing that introduces Ghost to developers who haven't heard of it yet, explains why MCP-native and ephemeral matter, and positions Ghost clearly in the agent stack. Blog posts, conference talks, video, and whatever new format works.
Community presence: living in GitHub issues and Discord, unblocking developers building on Ghost. The first response is a reply. The second response is a pull request.
Product feedback that lands: surfacing the rough edges you hit while building, so engineering can fix them before the next person hits them. You'll be the most credible source of "the DX breaks at step four" feedback in the company.