Senior Software Engineer

About this role

<h4>What The Role Is</h4> <p>As a<strong> Senior Engineer</strong> at Babylist, you take on hard problems and own them end-to-end. Millions of families depend on what we build.&nbsp;Agents write most of the code now. So the hard part is yours: what to build, how it should work and whether what shipped was right. You're still in the code for the genuinely hard problems. Agents handle the volume. You spend your time on the parts that need a person.</p> <p>We're building well beyond the registry now: the financial side of raising a kid, maternal health made simpler and more human, the education new parents are looking for and the community around them. The hard problems run across all of it, plus the platform underneath and the AI we already ship to families.&nbsp;You'll start on a team, but you won't be boxed into it. The roadmap is open, your scope grows as you do and you have a say in what you take on next. Senior here means owning whole problems; Staff is the next step up, setting direction across a domain.</p> <h4>What You'll Own</h4> <p>A Senior Engineer here owns problems, not just features. You're handed an outcome, you decide what to build, ship it and own whether it worked. You act on incomplete information and change course fast when the evidence says you were wrong.</p> <p>What you do depends on what the team needs:</p> <ul> <li>Frame the problem with your PM as a peer, run the experiment and bring customer evidence into what gets built.</li> <li>Harden a critical path, kill a class of incidents or design the abstraction your team builds on.</li> <li>Be the reviewer people want on the risky changes.</li> <li>Manage up with crisp choices: raise the risks early and protect the right tradeoffs.</li> <li>Share what you're learning about AI openly, so the whole team gets sharper.</li> </ul> <p>A few problems people at this level are working on right now:</p> <ul> <li>Deciding what the registry recommends to each family, from the ranking to the model behind it, and proving in a live experiment that it actually helps.</li> <li>Building the evals system that catches our AI support agent making things up before a customer does.</li> <li>Making a child's info one source of truth instead of five disconnected flows, so parents set it up once and new products like Early Investor build on it.</li> </ul> <h4>Who You Are</h4> <p>You've been shipping production systems for years, and you've got the judgment to show for it. You can pick up an ambiguous problem and start moving before anyone hands you the full picture.</p> <p>The strongest Senior engineers here are generalists, and usually the most prolific builders on their team. You go wherever the problem leads: a backend service one week, a stubborn frontend bug the next, the data pipeline after that. When it's hard you dig in, and you learn unfamiliar parts of the stack fast. Range is the Senior signature.</p> <h4>Compensation</h4> <p>We post real numbers. For a Canada-based Senior Engineer, the starting base salary range is $255,900 to $318,600 CAD, plus a target annual bonus of 15 percent of base. That's total target cash of roughly $294,285 to $366,390 CAD. On top of that you get meaningful equity and an RRSP match. Where you start in that range depends on your experience, and your pay grows from there with performance and scope.</p> <h4>How We Build</h4> <p>AI is the default here. Engineers run agentic sessions for most of the work, and a lot of the interesting engineering now lives in the scaffolding that makes the agents good: the eval harnesses, the curated context, custom review skills and fast CI. Agents also triage incidents and handle a big share of support. A human always owns the outcome.&nbsp;The architecture is intentionally simple: one Rails monolith, MySQL and few moving parts. That's deliberate. Simple infrastructure lets us move fast and lets AI reason about the whole system, so the hardest problems are the ones in front of customers.</p> <p><strong>The Stack</strong></p> <ul> <li><strong>Core app:</strong> Rails, Packwerk, React, TypeScript, Sidekiq</li> <li><strong>Mobile:</strong> iOS (Swift), Android (Kotlin)</li> <li><strong>Data, search &amp; events:</strong> MySQL, Snowflake, dbt, Airflow, Weaviate, WarpStream, Hex, Sigma</li> <li><strong>Machine learning:</strong> deep learning, matrix factorization, retrieval &amp; ranking, AWS SageMaker, MLflow</li> <li><strong>AI &amp; dev tooling:</strong> Claude Code, Devin, Linear, CodeRabbit, Warden, LangChain, Bedrock AgentCore, Maxim</li> <li><strong>Infra &amp; ops:</strong> AWS, Kubernetes, Terraform, GitHub Actions, Datadog, incident.io, LaunchDarkly</li> <li><strong>Key integrations:</strong> Shopify (payments), Iterable (CRM)</li> </ul> <h4>Why Babylist</h4> <p>An engineer, expecting her first baby, couldn't find the registry she wanted. So she built it. That's how Babylist started, and it's still how we work: engineers solving problems for families.&nbsp;Becoming a parent is one of the biggest moments in a person's life. Millions reach it for the first time every year, making thousands of decisions and figuring it out as they go. That's who we build for, and we're a long way from done.</p> <p>Ten million people give gifts through Babylist every year. We did more than $750M in revenue in 2025, up 45 percent over the year before, and we've been profitable for eight years while staying independent. So you can take on a hard, multi-year problem without watching over your shoulder for the next round or the next correction. And the team is small, around 65 engineers, so what you ship stays visible and your scope stays wide.</p> <h4>How We Work</h4> <p>Remote-first across the US and Canada, and we have been for years. That's not changing. We trust you to own your time and your outcomes, and we get everyone in a room together twice a year. Teams are small, pods of three to five engineers, so nothing you ship disappears into a committee.&nbsp;You'll work shoulder to shoulder w