Member of Growth Staff

Capy•San Francisco, CA

10d•$200,000 - $250,000•Onsite

About The Position

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.

Requirements

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.

Nice To Haves

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.

Responsibilities

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.