Founding Product Engineer

About the role

Founding Product Engineer at Bloom — Engineer #2 About Bloom: Bloom turns your brand into a system. Give us your website, and we extract your brand DNA — colors, typography, tone, visual style — so you can instantly generate on-brand marketing materials: social posts, ads, mockups, logos. Assets that actually look like you. But images are just the start. We're building the brand hub — a system that deeply understands your brand, evolves with it over time, and becomes the engine for everything brand-related: video, audio, campaigns, competitive research, trend monitoring. We launched in December 2025 and went viral — 1.4M views, 14K users, 50K+ images generated in the first week, zero paid marketing. We've raised $1M from investors including Guillermo Rauch (Vercel). The team is Ray (founder/CEO) and Sid (founding engineer). We have more inbound than we can ship, a roadmap that's growing faster than we can build, and a clear vision for what Bloom becomes. The Role: You'll be engineer #2, working directly with Ray, in person in San Francisco. This is a founding product engineer role — you'll own big chunks of the product, not take tickets from a backlog. The work is broad by design. In any given week you'll be: • Shipping new product features end-to-end — designing the UX, building it, shipping it • Improving the product based on user feedback • Building and refining AI pipelines — prompt engineering, eval systems, handling non-deterministic outputs • Building email lifecycle flows to drive activation and retention • Analyzing funnels and forming product hypotheses • Fixing whatever's broken that day • Building internal tooling and dashboards • Spinning up micro-tools that could go viral on X The common thread isn't a specific technology — it's range. We need someone who can context-switch across product, engineering, AI, growth, and analytics without losing momentum. Who You Are: • True generalist — frontend, backend, AI engineering, growth experiments, product, design, analytics. You can pick up anything and run with it. • Real product sense — if told "the edit UX sucks, figure out a better approach," you ship something good without needing a Figma mock. • Build with AI tools natively — Claude Code, MCPs, Skills, Agents, etc. They're part of how you work every day. You're obsessed with optimizing your setup to maximize output. • Autonomous — you intuitively know the highest-leverage thing to work on, and you just go do it. You have the judgment to run with it and the taste to get it right. • Ship a ton — you hold multiple threads in your head, context-switch without losing momentum, and maintain quality at speed. Speed without quality is just slop. Clean code, proper PRs, strong fundamentals. • Hungry — startups, shipping fast, building things people actually use. This is what gets you up in the morning. • In SF or willing to relocate. This is in-person. Visa sponsorship available. Why Bloom: • Real traction — paying customers, strong MRR growth, and a product people love • Massive ownership — engineer #2 at a company with clear product-market fit signal • The space is on fire — AI + creative tools is one of the most exciting areas to build in right now • Beautiful product — strong brand, strong community, and a team that's proud of it • It actually matters — good design is inaccessible for most businesses. Bloom gives every business the ability to look like themselves at scale. Tech Stack: React, Next.js, REST API, MCP (Model Context Protocol), Claude Code, Cursor, VS Code Copilot