Senior Backend Engineer, Growth (US)

Nanit•New York, NY

16h•$180,000 - $200,000•Hybrid

About The Position

Nanit is moving families beyond overwhelm by transforming how parents understand their baby's early years. We combine advanced AI, real-world data from billions of sleep hours, and clinical expertise to deliver the clarity and confidence every parent deserves. Trusted by over one million families and backed by $125M in funding, we're building an entirely new category: predictive parenting intelligence. You'll be the founding backend engineer on a new Growth team - a cross-functional squad owning the full customer funnel, from a parent first considering Nanit through purchase, subscription, engagement, and eventually referring to us or buying again. You'll also be the first R&D engineer based at our US site, hybrid, with your manager and the rest of the team in a different time zone - so you'll need to hold context, make decisions, unblock yourself, and know when a question is worth raising rather than waiting on a sync. Your closest day-to-day partners will be mobile engineers and product managers.

Requirements

5+ years of backend software development with strong coding skills and solid experience in software design and architecture.
Demonstrated success working with significant independence - ideally in a distributed team with limited timezone overlap with your manager or peers.
Excellent asynchronous communication. You write clearly enough that decisions and context survive without a meeting.
Comfort with ambiguity and with shipping to learn. You care about the outcome metric, not only the ticket.
Experience with critical production systems and techniques like load balancing, caching, and distributed systems.
Proficiency designing and maintaining APIs consumed by mobile clients (REST, gRPC, WebSocket).
Hands-on experience with A/B testing infrastructure, feature flags, and event instrumentation (e.g., Unleash, Mixpanel).
Solid experience in testing methodologies and test automation frameworks.
Proficient with tools like Grafana and Prometheus.
Proven experience delivering backend projects successfully.
Knowledge of Agile methodologies.

Nice To Haves

Hands-on experience with Docker and Kubernetes is an advantage.
Experience with consumer subscription products - billing, plan tiering, App Store and Google Play in-app purchases, or Stripe.
Prior work on a growth, monetization, or lifecycle team.
Ability to independently take a concept from research to production.
Enthusiasm for new technologies and willingness to explore them.
Commitment to well-crafted and rigorously tested code.
Willingness to travel to Tel Aviv for onboarding and periodically thereafter.

Responsibilities

Own the backend behind growth bets. Build and ship the services powering paywalls, subscription tiering, onboarding journeys, in-app messaging, referral mechanics, trial models, and checkout bundling.
Make growth measurable. Build and extend the experimentation and instrumentation layer - feature flags, experiment assignment, event tracking - so every bet the team makes can be evaluated on real data rather than opinion.
Work end to end across the funnel. Move between acquisition, activation, and retention work as the roadmap demands, rather than owning a single narrow surface.
Partner tightly with mobile and product. Most of what you build is consumed by our iOS and Android apps. You'll design API contracts in conversation with the engineers using them and with the PMs shaping the experiments.
Operate with high agency. Take ambiguous problems, decide on an approach, communicate it clearly in writing, and ship. Escalate deliberately, not by default.
Set the pattern for US engineering at Nanit. How you work - documentation, async communication, on-call, review habits - becomes the template for everyone who follows.
Anchor on-call coverage in your time zone. Be first responder for production alerts during your working hours, extending the backend group toward true follow-the-sun coverage. Triage, mitigate, escalate what you can't, and hand off open threads in writing.
Contribute to the backend guild. Help drive best practices, guidelines, and standards across R&D, and keep the US perspective represented in them.