Search

Full Stack Engineer

PublishedPublished: 6/14/2022
Technology
|

Job Description

Full-Stack Engineer at Bloom

\n

Remote, US · Full-time · $150K–$225K

\n


\n

Who we are

\n

Bloom is a forward-deployed growth studio. We’re changing how software gets built and delivered.

\n

AI has made output cheap. Screens, code and first drafts are no longer scarce. What’s scarce is getting products to land: shipping fast, finding the growth signal, and building something people choose to use. Value is moving from making things to making things land.

\n

We think design is the new code. The product teams that win from here will pair builders, who are entrepreneurial, technical and above all tasteful, with full-stack engineers who can turn a vision into production systems in weeks. We’ve worked this way for six years, before the model had a name, and we’re now taking it to early-stage portfolio companies that need to get to market fast.

\n

We don’t hand over decks or bill for screens. We speed up the path from idea to live product.

\n


\n

The role

\n

You’re the full-stack half of that partnership. You’ll pair with our design engineers to take portfolio companies from zero to launch and then to traction. You’ll own the architecture, data, APIs, integrations and infrastructure, and you’ll work across the stack when the product needs it.

\n


\n

What you’ll do

\n

    \n
  • Build production backends for several high-velocity launches at once
  • \n

  • Build the growth engine into each product: payments, lifecycle messaging, analytics, and AI-native features
  • \n

  • Turn what we learn on each launch into reusable systems and AI-native workflows, so every launch goes faster than the last
  • \n

  • Work directly with early-stage teams on what to build, not only how to build it
  • \n

\n


\n

What you bring

\n

    \n
  • 5+ years building and shipping production software, including at least one product you took from zero to live users
  • \n

  • Deep backend skills in TypeScript/Node or Python, with strong API design (REST/GraphQL), background jobs, and event-driven systems
  • \n

  • Strong data modeling in Postgres: schemas, migrations and query performance that hold up as the product grows
  • \n

  • Hands-on cloud and infrastructure experience (AWS, GCP, Vercel or Supabase), including CI/CD, observability, and keeping production stable when things break
  • \n

  • Experience building the plumbing of a growth stack: auth, payments (Stripe), webhooks, third-party APIs, and product analytics
  • \n

  • LLM features shipped to production, such as retrieval, agents, evals and structured outputs, plus a clear view of where they break
  • \n

  • AI-native habits: you use AI coding tools every day and have the judgment to review, test and own what they produce
  • \n

  • Enough frontend skill (React/Next.js) to build a feature end to end without waiting on anyone
  • \n

  • Security fundamentals: you handle secrets, permissions and user data the way a company 10x your size would
  • \n

  • Clear, direct communication with non-engineers, and comfort pushing back on scope when the timeline doesn’t fit it
  • \n

  • You can work across several engagements at once and switch context without losing quality
  • \n

  • US-based, with working hours that overlap US time zones
  • \n

\n


\n

Bonus points

\n

    \n
  • You’ve founded a company or been an early engineer (first 10) at a startup
  • \n

  • You’ve built messaging automation, customer data pipelines or attribution systems
  • \n

  • You have taste: you notice when an interaction feels wrong, even when the code is right
  • \n

  • You’ve written or open-sourced internal tools, templates or starters that other engineers adopted
  • \n

\n


\n

Why Bloom

\n

    \n
  • You’ll help define a new category, the forward-deployed model for product
  • \n

  • You’ll ship more in a year than most engineers ship in five
  • \n

  • You’ll work directly with founders, with no layers in between
  • \n

  • $150K–$225K base salary
  • \n

  • Apply: Send us something you shipped and tell us why it landed.
  • \n

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...