Senior Product Designer

Babylist is the leading platform for expecting and new families, seeking a Senior Product Designer to build the next generation of their services. The role involves owning the user experience, collaborating with product managers and engineers, and designing intuitive and emotionally resonant interactions for families navigating early parenthood.

Responsibilities:

• Own the experience layer for a customer journey or product surface end-to-end — from information architecture and interaction patterns to shipped frontend code
• Design for families navigating one of the most stressful and meaningful transitions of their lives — the bar is simple, intuitive, and emotionally right, not just functional
• Contribute to and evolve Babylist's design system — reusable components, interaction patterns, consistency across web and native mobile
• Run your own research: user interviews, usability testing, fast feedback loops through Babylist communities and other channels
• Write production frontend code — implement, refine, and polish the experiences you design directly in the codebase
• Model AI-native workflows for the team — prototype, synthesize, build — then share and teach what's working
• Support non-designers in contributing to the experience layer — act as a quality bar and consultant, not a gatekeeper
• Instrument your own work, track whether it's moving the right metrics, and make clean iterate/pivot/stop decisions based on evidence

Requirements:

• You design and ship production frontend code. You don't hand off to an engineer and hope for the best — you close the gap yourself. Transitions, micro-interactions, error states, empty states, keyboard behavior. React, React Native, SwiftUI, or equivalent. You have opinions about component architecture
• You move from concept to interactive prototype in hours, not weeks. You use AI tools to compress exploration cycles. You have a portfolio of things you have designed and built this way — shipped, not just prototyped
• You're a systems thinker. You see how a single interaction fits into a broader flow, how flows connect across products, and how a design system enables all of it. You design for coherence, not just screens
• You can plan and run research end-to-end. Generative and evaluative. You bring concrete qualitative and quantitative evidence into design decisions, not just instincts
• You know what's worth building. You make PMs and engineers faster by reducing ambiguity and tightening scope — not by creating review cycles
• You hold a high bar for craft. You notice the details most people can't articulate but everyone responds to — motion, accessibility, emotional tone. You have a portfolio of shipped consumer product work across web and native mobile that demonstrates this
• You seek feedback before it finds you. You put rough prototypes in front of users early, share in-progress work before it's polished, and treat critique as signal, not threat
• Excited about the AI transformation, not anxious about it. You naturally reach for AI to move faster and improve your output — and you want to help shape what an AI-first design organization looks like
• Own the experience layer for a customer journey or product surface end-to-end — from information architecture and interaction patterns to shipped frontend code
• Design for families navigating one of the most stressful and meaningful transitions of their lives — the bar is simple, intuitive, and emotionally right, not just functional
• Contribute to and evolve Babylist's design system — reusable components, interaction patterns, consistency across web and native mobile
• Run your own research: user interviews, usability testing, fast feedback loops through Babylist communities and other channels
• Write production frontend code — implement, refine, and polish the experiences you design directly in the codebase
• Model AI-native workflows for the team — prototype, synthesize, build — then share and teach what's working
• Support non-designers in contributing to the experience layer — act as a quality bar and consultant, not a gatekeeper
• Instrument your own work, track whether it's moving the right metrics, and make clean iterate/pivot/stop decisions based on evidence