Looking for a Community & Growth Lead

Zapstore is a permissionless app store built on Nostr. We’re at thousands of daily users and growing fast, but we’re still mostly unknown outside the Nostr ecosystem. We need someone to change that.

What you’ll actually be doing

Growth and community. You’ll be finding where our users are, figuring out what makes them install apps from Zapstore instead of Google Play, and building the loops that turn one user into ten.

That means outreach: developer relations, community building, partnerships. Social media: not just posting into the void, but running experiments, tracking what works, iterating fast. Content: writing, recording, creating things that spread. Distribution: getting Zapstore in front of people who don’t know they need it yet.

It also means support. Replying to questions on Nostr, X, Reddit, GitHub — wherever users show up. Helping developers publish their first app. Triaging bug reports. Turning confused users into advocates. You are the support team, and support is a growth channel.

You’ll also be running growth experiments — referral mechanics, onboarding flows, viral loops, anything that moves the needle. Some will work, most won’t. The job is to try a lot of things quickly and double down on what hits.

This is not a “post three times a week and call it content marketing” role. You’ll have autonomy and direct access to the product. If an experiment needs a feature built, you work with the team to ship it. If a campaign needs tooling, you build it.

What we’re not looking for

There is no marketing team. It’s you, the core team, and whatever you can automate or outsource tactically.

We don’t need polished corporate comms. Zapstore is freedom tech — permissionless, censorship-resistant, built on Nostr. The tone is direct, the community is technical, and the pitch has to be real.

What matters

You need to understand growth as a discipline. Metrics, funnels, cohorts, retention curves. You should know the difference between a vanity metric and a leading indicator, and you should be able to design an experiment that actually tests a hypothesis.

Social media fluency across platforms: Nostr (obviously), X, Reddit, Hacker News, Product Hunt, YouTube, podcasts, newsletters. You need to know where technical users hang out and how to reach them without being annoying.

Writing. A lot of this job is writing — posts, threads, scripts, emails, landing page copy. You need to be able to explain why Zapstore matters in a way that makes people care.

Scrappiness. You’ll be doing things that don’t scale, manually, until you figure out what works. Then you automate or delegate.

Nostr familiarity is essential. You should understand why permissionless infrastructure matters, what Nostr enables that centralized platforms can’t, and how to talk about it without sounding like a zealot. If you’ve been active in the Nostr community, even better.

We communicate internally via a Signal group. The team is small and things move fast. Remote, but not a black box. Show up, share what you’re testing, flag what’s working and what’s not.

One more thing

We use LLMs and agents extensively and expect you to do the same — not just for drafting posts, but for research, data analysis, content generation at scale, outreach automation, anything that lets you move faster. Good judgment over the output matters more than output volume.

We also care about making Zapstore discoverable to AI systems. If you have ideas about optimizing for AI-powered search, LLM citations, or agent-driven app discovery, there’s room to experiment.

To apply

Send us a DM on Nostr: zapstore.