Registry Experience
The registry, signup, and checkout millions of families and gift-givers use.
Come build technology for millions of growing families.
Engineering at Babylist · Remote-first across the US & Canada
- 10M+
- people shop with us every year
- $750M+
- 2025 revenue, up 45% year over year
- Profitable
- 8 years running, independent the whole way
- 65
- engineers, small enough that your work is visible
Cabo Offsite, 2025An engineer, expecting her first baby, couldn’t find the registry she wanted, so she built it. That’s Babylist. We still build the same way: engineers solving problems for families.
Natalie, CEO & Founder, tells the story on the
How I Built This
podcast.
The work
Where could I make an impact?
Babylist engineering spans the registry, commerce, healthcare, AI, and the platform underneath it all. Most teams are pods of three to five engineers, so you own meaningful pieces and ship fast.
Recommendations
Search, recommendations, and ranking: the ML that helps families find the right gear, plus the catalog behind it.
Growth & LTV
New bets that keep families coming back: Early Investor, Education, Invitations, Wishlist, Family Memories.
Operations Tech
The systems behind the scenes: AI-powered operations, healthcare billing, supply chain, and finance.
Platform
The foundation everyone builds on: dev tooling, security, infrastructure, reliability, shared services.
You’ll start on one team. You won’t be stuck there. The code and the roadmap are open, and you’ll have a say in what your pod builds next.
How we build
AI is the default here.
Nearly every pull request we merge is AI-assisted. Code output is up 50% over the last few months. That changes the job. Today, the work is knowing what to build, steering the agents and owning the result.
-
Judgment is the job
We hire for taste: knowing what to build and whether the agent got it right. The work is steering the agents and owning the result.
-
The scaffolding is the real work
Agents are only as good as their environment, so we invest there: design systems, curated knowledge, custom review skills and faster CI. A lot of the interesting engineering lives here now.
-
Everyone builds, not just engineers
We brought AI to the whole company in about a year. Everyone has Claude, and more than 100 people run their own local dev setups, including teammates in data, research, accounting and legal. The bar keeps rising because everyone's pushing it.
You'll build AI, not just build with it
This is product work, in production. Our support assistant runs on Sierra and handles about half of our support volume. Customers rate it highly. Addie, our registry consultant, runs on our own platform: Bedrock AgentCore, Claude, and Weaviate. It's rolling out to families now.
The stack
- Core app
- RailsPackwerkReactTypeScriptSidekiqMySQL
- Mobile
- iOS (Swift)Android (Kotlin)
- Data, search & events
- SnowflakedbtAirflowWeaviateWarpStreamHexSigma
- Machine learning
- Deep learningMatrix factorizationRetrieval & rankingAWS SageMakerMLflow
- AI & dev tooling
- Claude CodeDevinLinearCodeRabbitWardenLangChainBedrock AgentCore
- Infra & ops
- AWSKubernetesTerraformGitHub ActionsDatadogincident.ioLaunchDarkly
- Key integrations
- Sierra (agentic support)Shopify (payments)Iterable (CRM)NetSuite (ERP)
What might surprise you
The honest version. Worth reading before you apply.
Most careers pages sand off the edges. Here's what we'd rather you hear now than discover in week three.
Our architecture is intentionally simple.
A Rails monolith and MySQL in 2026 isn't tech debt or inertia. It's a choice. One codebase. Few moving parts. No microservice sprawl paging you at 2 a.m. Simple infrastructure lets us move faster, and lets AI reason about the whole system. The hard problems live in the product, not the plumbing.
Shipped enough to love simple? You'll feel at home.
We change how we work whenever it stops serving us.
And lately, that's often. Most engineering processes assume one thing: engineering is the scarce resource. They’re designed to ration it. AI broke that assumption. So we're rethinking how we plan, scope and ship: trying new things, keeping what works and dropping what doesn't.
You'd rather write the playbook than follow one.
You'll own outcomes, not tickets.
High autonomy means little hand-holding. You'll get an ambiguous problem and the trust to decide what to build.
Bring your own judgment.
How we hire
Three rounds. Thorough on purpose, usually two to three weeks.
We keep the interview loop focused and consistent. Every conversation explores something different, and every candidate goes through the same process. It's a high bar because you'll work alongside people who cleared it too. If your timeline is tight, we'll move faster.
-
Round 1 · 30 minutes
Recruiter conversation
A call to trade context: what you want next, what we're building, and straight answers on comp, team, and remote.
-
Round 2 · 1 hour
Technical screen
One round, no AI, language-agnostic and framework-free. Reach for Google when you'd reach for it normally; we just want to watch how you reason from first principles.
-
Round 3 · 4 hours
Final round
Four one-hour interviews: system design, AI-assisted coding (with the tools you'd use here), product sense, and culture & values. Feedback either way, within 24–48 hours.
Open roles
Build what you’d want for your own family.
Plus great pay, strong benefits, and perks worth talking about.
See benefits & perks →
-
Senior Software Engineer
-
Senior Software Engineer
-
Staff Engineer, Site Reliability
-
Staff Engineer, Site Reliability
-
Staff Machine Learning Engineer
-
Staff Machine Learning Engineer
-
Staff Software Engineer
-
Staff Software Engineer
-
Senior Data Engineer
-
Senior Data Engineer
Don’t see the right role? We always want to hear from senior engineers.
Introduce yourself.