Vibe Coder in Residence — Full Time

Qualifications and requirements

You're a builder who can't stop shipping. Specifically:

• Experience launching mobile apps — this is a hard requirement. You've shipped to the App Store or Google Play, not just localhost.
• Fluent in the new stack. AI agents, vibe-coding tools (Cursor, Claude Code, v0, Replit, etc.), and whatever ships next week.
• Receipts. You build in public and can prove it — GitHub, live projects, launch threads, demo videos.
• Fast shipper. You're comfortable going from idea to live product in a day and iterating in production.
• Low-ego, high-output. You treat "impossible" as a dare.

Job Functions

The Vibe Coder in Residence ("VCR") is part builder, part mad scientist, part hype machine. You use AI tools to turn "wouldn't it be cool if..." into something live — same day. No red tape, no approval chains.

• Ship daily. Prototypes, micro-apps, and experiments. If it's fun and useful, it goes live.
• Build in public. Demos, threads, and behind-the-scenes content that puts Zagged everywhere.
• Remix what works. Take a win, loop it, and make it better across growth, content, and product.
• Never touch marketing. You focus entirely on building — distribution is our core business, and we aim it at your projects.

Success is measured in shipped projects, not meetings attended.

Desirable skills

None of these are required, but they'll make us pay attention:

• Growth or consumer product instincts — you know what makes something shareable before you build it.
• Familiarity with social/creator platforms — TikTok, Reels, Shorts, or short-form content tools.
• Your own audience or distribution channel — a following on X, a newsletter, a YouTube channel, anything.
• Design taste — your projects look good, not just work.
• Strong opinions about fonts. Yes, really. There's a question about this in the application.

Conditions

• Fully remote team setup, enabling flexible work from anywhere.
• Fast-paced startup environment where shipping and learning are prioritized.
• Collaborative engineering culture with active peer review and shared ownership of outcomes.