All roles

CAREERS

Founding Product Engineer

Every system that creates for a brand needs the same source of truth. That's what we're building.

Most brands still live across decks, PDFs, asset folders, and tribal knowledge. That breaks when a marketing team, software product, or agent needs to create on the brand's behalf. Each system interprets the brand again, and the output drifts.

Bloom is the brand layer. Everything that defines a brand — logos, colors, fonts, voice, references, products — lives in one working system. Marketers operate it, software platforms embed it, and agents call it. Every output starts from the same canonical brand.

Images are the first output: ads, social posts, product shots, mockups, and more. Copy, video, voice, and motion will draw from the same system as they ship. We're building the infrastructure that keeps every system working on-brand.

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, and we're in the YC Spring 2026 batch.

The team is me (Ray, founder/CEO) and Sid, founding engineer. We're YC-backed, 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. I need one more engineer.

The Role

You'll work directly with me, in person in San Francisco. Small team, big surface area.

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 our funnels and forming product hypotheses
  • Fixing whatever's broken that day
  • Building internal tooling and dashboards
  • Spinning up a micro-tool 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.

You

  • You're a true generalist. Frontend, backend, AI engineering, growth experiments, product, design, analytics. You can pick up anything and run with it.
  • You have real product sense. If I say “the edit UX sucks, figure out a better approach,” you ship something good without needing a Figma mock.
  • You build with AI tools natively. Claude Code, MCPs, Skills, Agents, whatever's latest. They're part of how you work every day. You're not just using AI. You're obsessed with optimizing your setup to maximize output.
  • You're autonomous. You intuitively know the highest-leverage thing to work on, and you just go do it. You don't need to validate every decision. You have the judgment to run with it and the taste to get it right.
  • You ship a ton. You can hold multiple threads in your head, context-switch without losing momentum, and maintain quality at speed. Look at my commit graph - that's the pace. But speed without quality is just slop. Clean code, proper PRs, strong fundamentals.
  • You're hungry. Startups, shipping fast, building things people actually use. This is what gets you up in the morning.
  • You're on X. You like seeing what people are shipping, what's happening in startups, what tools are new.
  • You're in SF or willing to relocate. This is in-person. If you need visa support, we can help make it happen.

Why Bloom

  • Real traction. This isn't a speculative idea. We're YC-backed, have paying customers, strong MRR growth, and a product people love.
  • Massive ownership. You're joining a three-person team with clear product-market fit signal. The surface area you'll own is enormous.
  • The category is opening up. More marketing teams, software products, and agents create for brands every day. They all need the same canonical brand system.
  • It's a beautiful product. Bloom has a strong brand, a strong community, and a team that's proud of it. If you care about building something you're proud to show people, this is it.
  • It actually matters. When a brand is scattered across documents and folders, every new tool produces drift. Bloom gives every system the same source of truth, so on-brand becomes the default.

Interested?

Apply here