Full Stack Engineer

Bloom is a forward-deployed growth studio that partners with early-stage portfolio companies to build and launch products. The Full-Stack Engineer owns architecture, data, APIs, integrations, and infrastructure while helping teams turn product ideas into production systems and growth capabilities.

Responsibilities:

• Build production backends for several high-velocity launches at once
• Build the growth engine into each product: payments, lifecycle messaging, analytics, and AI-native features
• Turn what we learn on each launch into reusable systems and AI-native workflows, so every launch goes faster than the last
• Work directly with early-stage teams on what to build, not only how to build it

Requirements:

• 5+ years building and shipping production software, including at least one product you took from zero to live users
• Deep backend skills in TypeScript/Node or Python, with strong API design (REST/GraphQL), background jobs, and event-driven systems
• Strong data modeling in Postgres: schemas, migrations and query performance that hold up as the product grows
• Hands-on cloud and infrastructure experience (AWS, GCP, Vercel or Supabase), including CI/CD, observability, and keeping production stable when things break
• Experience building the plumbing of a growth stack: auth, payments (Stripe), webhooks, third-party APIs, and product analytics
• LLM features shipped to production, such as retrieval, agents, evals and structured outputs, plus a clear view of where they break
• AI-native habits: you use AI coding tools every day and have the judgment to review, test and own what they produce
• Enough frontend skill (React/Next.js) to build a feature end to end without waiting on anyone
• Security fundamentals: you handle secrets, permissions and user data the way a company 10x your size would
• Clear, direct communication with non-engineers, and comfort pushing back on scope when the timeline doesn't fit it
• You can work across several engagements at once and switch context without losing quality
• US-based
• You've founded a company or been an early engineer (first 10) at a startup
• You've built messaging automation, customer data pipelines or attribution systems
• You have taste: you notice when an interaction feels wrong, even when the code is right
• You've written or open-sourced internal tools, templates or starters that other engineers adopted