We're building the AI software engineer you hand real work to. A thread starts from Slack, Linear, the web app, the desktop app, or the API; Capy makes the change on a cloud machine or right on your own laptop, office Mac mini, or any device you've paired, opens the pull request, and handles CI and review feedback until it merges. Work moves between your devices and the cloud mid-thread, big work splits into parallel agents across those machines, a review agent reads every PR, and automations run on a schedule or on platform events. The age of the solo coder is over: developers stop babysitting single agent sessions and start orchestrating fleets of agents, together with their team.
We're a small team in San Francisco, backed by Y Combinator and tier-1 investors, shipping to teams that run Capy on production codebases every day. We build Capy with Capy: our own PRs, reviews, and automations run through it.
AI coding is a crowded market now, and developers expect first-minute magic and a quality bar that holds across every surface. Meeting that bar means you will have to own the entire product experience and craft it with care.
\"Full stack\" here means the whole width of Capy: the interfaces developers direct agents from, the agent loop and its tools, the backend the loop re-plans from, the infrastructure the machines boot on, and the layer that talks to every frontier model. You'll make product decisions without a PM, design without waiting on a mockup, and solve the hard engineering problem yourself rather than handing it off. This is a role for people who build with taste and feel the gap between what exists and what should, then close it.
Ship across the whole stack. One day is a new tool in the agent loop, the next is the React surface that shows what it did, the migration behind it, and the Kubernetes change that ships it.
Set the standard for agent UX. Threads, tasks, diffs, reviews, live machine desktops streamed from our Rust remote desktop: twenty-five agents running at once need an interface that stays legible.
Design in code. Take a feature from rough idea to a polished, animated, keyboard-first interface in the React web app and Electron desktop app.
Build the backend the agent runs on. Effect services over MySQL (Vitess on PlanetScale), realtime fan-out over NATS, the typed API and protocol every client shares, the git proxy, the worker that drains threads.
Push what the agent can do. New tools, better verification, tighter loops with CI and review, smarter task orchestration, and the provider layer across Anthropic, OpenAI, Gemini, and the rest.
Run the infrastructure. The Kubernetes clusters and IaC that deploy Capy, and the VM images and sandbox platform every cloud machine boots from.
Direct Capy on Capy. Most of your day is writing specs, steering agents, reviewing their PRs, and fixing the harness when it lets them down.
Talk to users. Developers running Capy on real codebases tell you what's wrong; you turn it into what ships that day.
Agent-native. Claude Code, Codex, Cursor, etc (or your own harness) is how you already work, and you have sharp opinions about where they fall short.
Fluent in our stack. TypeScript 7 on Node 24 and React in production, and typed functional code (Effect or the like) you can read and write without a ramp. You've shipped against MySQL, run something on Kubernetes, and touched a message bus like NATS.
Comfortable at every layer. A slow query, a broken websocket, a failing Helm release, and a misbehaving tool call in the same afternoon, and you don't wait for a specialist on any of them.
Taste in interfaces. You notice the four-pixel misalignment, you care about motion, hierarchy, and empty states, and you can point at shipped work that proves it.
Independent product judgment. You make the call on what to build and how it should feel without a PM or designer defining the problem first.
Fast without shortcuts. You verify your work, read your diffs, and would rather delete code than add an abstraction nobody uses yet.
In San Francisco. In a room with people doing the same.
You've felt the gap between an agent product that demos well and one you'd trust with your own repo, and you want to close it.
You'd rather own a feature from idea to merge than hand it off halfway.
You think the next five years of software engineering look nothing like the last five, and you want to be the one deciding what they look like.
Effect in production, or Rust (our remote desktop is Rust).
Sandboxed execution, VM images, remote desktops, or a git proxy you've built or operated.
A model-provider layer you've built, or direct work against Anthropic, OpenAI, and Gemini APIs.
Design-tool fluency (Figma or similar) on top of prototyping in code.
Public work: open source, posts, demos, an active account on X.
Founder or early-employee experience.
$200K – $300K salary plus 0.5% – 1.5% equity. Medical, dental, and vision. Flexible PTO. Visa sponsorship and relocation support.
1. A 30-minute call with a founder about what you've built and what you'd build here.
2. A take-home you do with whatever agents you like, then a walkthrough of how you directed them and why.
3. A day in the office pairing with the team on real work.
4. Offer, usually within a week of the first call.
If you've shipped something you're proud of, send it with your application. That's what we'll look at first.
","descriptionPlain":"ABOUT CAPY\n\nWe're building the AI software engineer you hand real work to. A thread starts from Slack, Linear, the web app, the desktop app, or the API; Capy makes the change on a cloud machine or right on your own laptop, office Mac mini, or any device you've paired, opens the pull request, and handles CI and review feedback until it merges. Work moves between your devices and the cloud mid-thread, big work splits into parallel agents across those machines, a review agent reads every PR, and automations run on a schedule or on platform events. The age of the solo coder is over: developers stop babysitting single agent sessions and start orchestrating fleets of agents, together with their team.\n\nWe're a small team in San Francisco, backed by Y Combinator and tier-1 investors, shipping to teams that run Capy on production codebases every day. We build Capy with Capy: our own PRs, reviews, and automations run through it.\n\n\nTHE ROLE\n\nAI coding is a crowded market now, and developers expect first-minute magic and a quality bar that holds across every surface. Meeting that bar means you will have to own the entire product experience and craft it with care.\n\n\"Full stack\" here means the whole width of Capy: the interfaces developers direct agents from, the agent loop and its tools, the backend the loop re-plans from, the infrastructure the machines boot on, and the layer that talks to every frontier model. You'll make product decisions without a PM, design without waiting on a mockup, and solve the hard engineering problem yourself rather than handing it off. This is a role for people who build with taste and feel the gap between what exists and what should, then close it.\n\n\nWHAT YOU'LL DO\n\n - Ship across the whole stack. One day is a new tool in the agent loop, the next is the React surface that shows what it did, the migration behind it, and the Kubernetes change that ships it.\n\n - Set the standard for agent UX. Threads, tasks, diffs, reviews, live machine desktops streamed from our Rust remote desktop: twenty-five agents running at once need an interface that stays legible.\n\n - Design in code. Take a feature from rough idea to a polished, animated, keyboard-first interface in the React web app and Electron desktop app.\n\n - Build the backend the agent runs on. Effect services over MySQL (Vitess on PlanetScale), realtime fan-out over NATS, the typed API and protocol every client shares, the git proxy, the worker that drains threads.\n\n - Push what the agent can do. New tools, better verification, tighter loops with CI and review, smarter task orchestration, and the provider layer across Anthropic, OpenAI, Gemini, and the rest.\n\n - Run the infrastructure. The Kubernetes clusters and IaC that deploy Capy, and the VM images and sandbox platform every cloud machine boots from.\n\n - Direct Capy on Capy. Most of your day is writing specs, steering agents, reviewing their PRs, and fixing the harness when it lets them down.\n\n - Talk to users. Developers running Capy on real codebases tell you what's wrong; you turn it into what ships that day.\n\n\nWHO YOU ARE\n\n - Agent-native. Claude Code, Codex, Cursor, etc (or your own harness) is how you already work, and you have sharp opinions about where they fall short.\n\n - Fluent in our stack. TypeScript 7 on Node 24 and React in production, and typed functional code (Effect or the like) you can read and write without a ramp. You've shipped against MySQL, run something on Kubernetes, and touched a message bus like NATS.\n\n - Comfortable at every layer. A slow query, a broken websocket, a failing Helm release, and a misbehaving tool call in the same afternoon, and you don't wait for a specialist on any of them.\n\n - Taste in interfaces. You notice the four-pixel misalignment, you care about motion, hierarchy, and empty states, and you can point at shipped work that proves it.\n\n - Independent product judgment. You make the call on what to build and how it should feel without a PM or designer defining the problem first.\n\n - Fast without shortcuts. You verify your work, read your diffs, and would rather delete code than add an abstraction nobody uses yet.\n\n - In San Francisco. In a room with people doing the same.\n\n\nYOU MIGHT THRIVE HERE IF\n\n - You've felt the gap between an agent product that demos well and one you'd trust with your own repo, and you want to close it.\n\n - You'd rather own a feature from idea to merge than hand it off halfway.\n\n - You think the next five years of software engineering look nothing like the last five, and you want to be the one deciding what they look like.\n\n\nNICE TO HAVE\n\n - Effect in production, or Rust (our remote desktop is Rust).\n\n - Sandboxed execution, VM images, remote desktops, or a git proxy you've built or operated.\n\n - A model-provider layer you've built, or direct work against Anthropic, OpenAI, and Gemini APIs.\n\n - Design-tool fluency (Figma or similar) on top of prototyping in code.\n\n - Public work: open source, posts, demos, an active account on X.\n\n - Founder or early-employee experience.\n\n\nCOMPENSATION\n\n$200K – $300K salary plus 0.5% – 1.5% equity. Medical, dental, and vision. Flexible PTO. Visa sponsorship and relocation support.\n\n\nHOW WE HIRE\n\n1. A 30-minute call with a founder about what you've built and what you'd build here.\n\n2. A take-home you do with whatever agents you like, then a walkthrough of how you directed them and why.\n\n3. A day in the office pairing with the team on real work.\n\n4. Offer, usually within a week of the first call.\n\nIf you've shipped something you're proud of, send it with your application. That's what we'll look at first.","compensation":{"compensationTierSummary":"$200K – $300K • 0.5% – 1.5%","scrapeableCompensationSalarySummary":"$200K - $300K","compensationTiers":[{"id":"c3eacc13-ed9a-4932-981b-f7c170580380","tierSummary":"$200K – $300K • 0.5% – 1.5%","title":null,"additionalInformation":null,"components":[{"id":"f21f6944-c475-4bcd-b32c-b7737fbd4dc6","summary":"$200K – $300K","compensationType":"Salary","interval":"1 YEAR","currencyCode":"USD","minValue":200000,"maxValue":300000},{"id":"47122c00-5cb7-4799-88de-deecb2b28667","summary":"0.5% – 1.5%","compensationType":"EquityPercentage","interval":"NONE","currencyCode":null,"minValue":0.5,"maxValue":1.5}]}],"summaryComponents":[{"compensationType":"Salary","interval":"1 YEAR","currencyCode":"USD","minValue":200000,"maxValue":300000},{"compensationType":"EquityPercentage","interval":"NONE","currencyCode":null,"minValue":0.5,"maxValue":1.5}]}},{"id":"d3fd5373-5a3b-4efa-ad47-50bd848bb21e","title":"Member of Growth Staff","department":"Engineering","team":"Engineering","employmentType":"FullTime","location":"SF","shouldDisplayCompensationOnJobPostings":true,"secondaryLocations":[],"publishedAt":"2026-10-06T20:48:33.462+00:00","isListed":true,"isRemote":false,"workplaceType":"OnSite","address":{"postalAddress":{"addressRegion":"California","addressCountry":"United States","addressLocality":"San Francisco"}},"jobUrl":"https://jobs.ashbyhq.com/capy/d3fd5373-5a3b-4efa-ad47-50bd848bb21e","applyUrl":"https://jobs.ashbyhq.com/capy/d3fd5373-5a3b-4efa-ad47-50bd848bb21e/application","descriptionHtml":"We're building the AI software engineer you hand real work to. A thread starts from Slack, Linear, the web app, the desktop app, or the API; Capy makes the change on a cloud machine or right on your own laptop, office Mac mini, or any device you've paired, opens the pull request, and handles CI and review feedback until it merges. Work moves between your devices and the cloud mid-thread, big work splits into parallel agents across those machines, a review agent reads every PR, and automations run on a schedule or on platform events. The age of the solo coder is over: developers stop babysitting single agent sessions and start orchestrating fleets of agents, together with their team.
We're a small team in San Francisco, backed by Y Combinator and tier-1 investors, shipping to teams that run Capy on production codebases every day. We build Capy with Capy: our own PRs, reviews, and automations run through it.
Growth at Capy is about getting developers to find Capy, try it, and bring their team. It's a real engineering job and a lot more: you'll build the automation, tools, and pages that make growth scale, talk to customers constantly, make content about what people build with Capy, and run the events that put us in front of developers. The mandate is revenue leverage: you pick whichever lever moves the number fastest that week, whether that's something you ship, a customer call, a video, or a meetup.
This is a role for an engineer who loves hacking on things, is great with people, and is organized enough to run an event end to end. You'll own growth slices from the idea to the shipped thing and the result, and you'll do it without waiting on anyone.
Build what moves the numbers. Outreach and lifecycle automation, enrichment and qualification pipelines, landing pages, onboarding flows, demos, integrations, scrapers, and internal dashboards. Much of it runs on Capy agents, and you'll tell us where the agent falls short.
Talk to customers, a lot. Onboarding calls, feedback sessions, and check-ins with the teams running Capy every day. You'll know better than anyone why teams adopt Capy, where they get stuck, and why they bring their team, and you'll turn that into what we build and what we say.
Make content. Articles, videos, and demos about Capy, the workflows teams run with it, and the cool things people build: launch videos, side-by-side comparisons, and benchmarks included.
Run events. Hackathons, meetups, dinners, and workshops, often with other startups and developer communities. You own it end to end, from partners and venue to the follow-up that turns attendees into users.
Get Capy noticed in unexpected ways. The occasional guerrilla stunt or launch moment that people talk about.
Own the funnel. How developers find Capy, what they see first, how fast they reach a merged PR, and why they bring their team. You instrument every step and improve it.
Run experiments weekly. Ship, measure, keep what works, and kill what doesn't.
Technical. You can build a page, wire an API, query a database, write the automation, and ship a working prototype yourself, without waiting on an engineer.
A hacker. Your weekends have side projects, your browser has too many tabs of half-finished experiments, and you've shipped something people actually used.
Agent-native. Claude Code, Codex, Cursor, or Capy is how you already get things done, and you want to point a fleet of them at growth problems.
Great with people. You enjoy customer calls, you're good at getting developers to tell you what's really wrong, and people come away wanting to help you.
A creator. You can write an article developers finish and make a video that shows the thing instead of describing it.
Organized. You can run an event for a hundred developers without it feeling chaotic, and nothing falls through the cracks afterwards.
Measured. You know a vanity metric from one that pays for itself, and you set up the tracking to tell them apart.
In San Francisco. In a room with people doing the same.
You've grown something by building it and staying close to its users, and you'd rather show the thing than the slides.
You like switching between shipping code, a customer call, and filming a demo in the same day.
You get energized by a number that moved because of something you did last Tuesday.
Developer-focused growth before: devtools, infrastructure, open source, or an API product.
Events run for developers: hackathons, meetups, or conferences.
An audience or community you've built somewhere: X, YouTube, a newsletter, a Discord, GitHub.
Hands-on outreach tooling: enrichment, sequencing, and CRMs, wired together yourself.
Video and design chops: you can cut a launch clip or lay out a page without help.
Founder or early-employee experience.
$200K – $250K salary plus 0.5% – 1% equity. Medical, dental, and vision. Flexible PTO. Visa sponsorship and relocation support.
1. A 30-minute call with a founder about what you've grown and what you'd try first here.
2. A take-home: we give you a growth problem, you ship something real for it with whatever tools and agents you like, then walk us through it.
3. A day in the office working with the team.
4. Offer, usually within a week of the first call.
If you've ever grown something by building it and getting close to its users, we want to see it. Apply, or just send us the thing.
","descriptionPlain":"ABOUT CAPY\n\nWe're building the AI software engineer you hand real work to. A thread starts from Slack, Linear, the web app, the desktop app, or the API; Capy makes the change on a cloud machine or right on your own laptop, office Mac mini, or any device you've paired, opens the pull request, and handles CI and review feedback until it merges. Work moves between your devices and the cloud mid-thread, big work splits into parallel agents across those machines, a review agent reads every PR, and automations run on a schedule or on platform events. The age of the solo coder is over: developers stop babysitting single agent sessions and start orchestrating fleets of agents, together with their team.\n\nWe're a small team in San Francisco, backed by Y Combinator and tier-1 investors, shipping to teams that run Capy on production codebases every day. We build Capy with Capy: our own PRs, reviews, and automations run through it.\n\n\nTHE ROLE\n\nGrowth at Capy is about getting developers to find Capy, try it, and bring their team. It's a real engineering job and a lot more: you'll build the automation, tools, and pages that make growth scale, talk to customers constantly, make content about what people build with Capy, and run the events that put us in front of developers. The mandate is revenue leverage: you pick whichever lever moves the number fastest that week, whether that's something you ship, a customer call, a video, or a meetup.\n\nThis is a role for an engineer who loves hacking on things, is great with people, and is organized enough to run an event end to end. You'll own growth slices from the idea to the shipped thing and the result, and you'll do it without waiting on anyone.\n\n\nWHAT YOU'LL DO\n\n - Build what moves the numbers. Outreach and lifecycle automation, enrichment and qualification pipelines, landing pages, onboarding flows, demos, integrations, scrapers, and internal dashboards. Much of it runs on Capy agents, and you'll tell us where the agent falls short.\n\n - Talk to customers, a lot. Onboarding calls, feedback sessions, and check-ins with the teams running Capy every day. You'll know better than anyone why teams adopt Capy, where they get stuck, and why they bring their team, and you'll turn that into what we build and what we say.\n\n - Make content. Articles, videos, and demos about Capy, the workflows teams run with it, and the cool things people build: launch videos, side-by-side comparisons, and benchmarks included.\n\n - Run events. Hackathons, meetups, dinners, and workshops, often with other startups and developer communities. You own it end to end, from partners and venue to the follow-up that turns attendees into users.\n\n - Get Capy noticed in unexpected ways. The occasional guerrilla stunt or launch moment that people talk about.\n\n - Own the funnel. How developers find Capy, what they see first, how fast they reach a merged PR, and why they bring their team. You instrument every step and improve it.\n\n - Run experiments weekly. Ship, measure, keep what works, and kill what doesn't.\n\n\nWHO YOU ARE\n\n - Technical. You can build a page, wire an API, query a database, write the automation, and ship a working prototype yourself, without waiting on an engineer.\n\n - A hacker. Your weekends have side projects, your browser has too many tabs of half-finished experiments, and you've shipped something people actually used.\n\n - Agent-native. Claude Code, Codex, Cursor, or Capy is how you already get things done, and you want to point a fleet of them at growth problems.\n\n - Great with people. You enjoy customer calls, you're good at getting developers to tell you what's really wrong, and people come away wanting to help you.\n\n - A creator. You can write an article developers finish and make a video that shows the thing instead of describing it.\n\n - Organized. You can run an event for a hundred developers without it feeling chaotic, and nothing falls through the cracks afterwards.\n\n - Measured. You know a vanity metric from one that pays for itself, and you set up the tracking to tell them apart.\n\n - In San Francisco. In a room with people doing the same.\n\n\nYOU MIGHT THRIVE HERE IF\n\n - You've grown something by building it and staying close to its users, and you'd rather show the thing than the slides.\n\n - You like switching between shipping code, a customer call, and filming a demo in the same day.\n\n - You get energized by a number that moved because of something you did last Tuesday.\n\n\nNICE TO HAVE\n\n - Developer-focused growth before: devtools, infrastructure, open source, or an API product.\n\n - Events run for developers: hackathons, meetups, or conferences.\n\n - An audience or community you've built somewhere: X, YouTube, a newsletter, a Discord, GitHub.\n\n - Hands-on outreach tooling: enrichment, sequencing, and CRMs, wired together yourself.\n\n - Video and design chops: you can cut a launch clip or lay out a page without help.\n\n - Founder or early-employee experience.\n\n\nCOMPENSATION\n\n$200K – $250K salary plus 0.5% – 1% equity. Medical, dental, and vision. Flexible PTO. Visa sponsorship and relocation support.\n\n\nHOW WE HIRE\n\n1. A 30-minute call with a founder about what you've grown and what you'd try first here.\n\n2. A take-home: we give you a growth problem, you ship something real for it with whatever tools and agents you like, then walk us through it.\n\n3. A day in the office working with the team.\n\n4. Offer, usually within a week of the first call.\n\nIf you've ever grown something by building it and getting close to its users, we want to see it. Apply, or just send us the thing.","compensation":{"compensationTierSummary":"$200K – $250K • 0.5% – 1%","scrapeableCompensationSalarySummary":"$200K - $250K","compensationTiers":[{"id":"5ce39916-3c19-40d5-b5a5-d1cd696e4232","tierSummary":"$200K – $250K • 0.5% – 1%","title":null,"additionalInformation":null,"components":[{"id":"3ee76b88-2777-48f6-ba48-288e00693583","summary":"$200K – $250K","compensationType":"Salary","interval":"1 YEAR","currencyCode":"USD","minValue":200000,"maxValue":250000},{"id":"adaf870a-1fb9-45bc-bac1-9aed3ee30d36","summary":"0.5% – 1%","compensationType":"EquityPercentage","interval":"NONE","currencyCode":null,"minValue":0.5,"maxValue":1}]}],"summaryComponents":[{"compensationType":"Salary","interval":"1 YEAR","currencyCode":"USD","minValue":200000,"maxValue":250000},{"compensationType":"EquityPercentage","interval":"NONE","currencyCode":null,"minValue":0.5,"maxValue":1}]}}],"apiVersion":"1"}