[{"data":1,"prerenderedAt":105},["ShallowReactive",2],{"$fn6U-G777T1FQtUcnj9G5d9dogWWl77n-l69STN28bU8":3,"$fmpkvrJzOaa19cOs8ZpM9uXoEfKHs6SnC3zKZGio-UPg":28},{"job":4},{"id":5,"slug":6,"title":7,"companyname":8,"companylogo":9,"companyTagline":10,"companyIndustry":11,"city":12,"country":12,"remote":13,"employmentType":14,"department":16,"content_html":17,"content_text":18,"years":19,"createdAt":20,"updatedAtISO":21,"postedAtISO":22,"hasSalary":13,"salaryMin":23,"salaryMax":24,"currency":25,"schema":26},"b084f0e88ced4840d1625afcc71b16f6a2cbf2e33e531eaca0a023472be0cffa","senior-software-engineer-at-babylist-e753555faf","Senior Software Engineer","Babylist","https://logo.clearbit.com/babylist.com","We help expecting parents get exactly what they need for the arrival of their new baby.","Retail","Canada",false,[15],"Full-time","Engineering","\u003Ch4>What The Role Is\u003C/h4>\n\u003Cp>As a\u003Cstrong> Senior Engineer\u003C/strong> at Babylist, you take on hard problems and own them end-to-end. Millions of families depend on what we build. 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.\u003C/p>\n\u003Cp>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. 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.\u003C/p>\n\u003Ch4>What You'll Own\u003C/h4>\n\u003Cp>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.\u003C/p>\n\u003Cp>What you do depends on what the team needs:\u003C/p>\n\u003Cul>\n\u003Cli>Frame the problem with your PM as a peer, run the experiment and bring customer evidence into what gets built.\u003C/li>\n\u003Cli>Harden a critical path, kill a class of incidents or design the abstraction your team builds on.\u003C/li>\n\u003Cli>Be the reviewer people want on the risky changes.\u003C/li>\n\u003Cli>Manage up with crisp choices: raise the risks early and protect the right tradeoffs.\u003C/li>\n\u003Cli>Share what you're learning about AI openly, so the whole team gets sharper.\u003C/li>\n\u003C/ul>\n\u003Cp>A few problems people at this level are working on right now:\u003C/p>\n\u003Cul>\n\u003Cli>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.\u003C/li>\n\u003Cli>Building the evals system that catches our AI support agent making things up before a customer does.\u003C/li>\n\u003Cli>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.\u003C/li>\n\u003C/ul>\n\u003Ch4>Who You Are\u003C/h4>\n\u003Cp>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch4>Compensation\u003C/h4>\n\u003Cp>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.\u003C/p>\n\u003Ch4>How We Build\u003C/h4>\n\u003Cp>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. 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.\u003C/p>\n\u003Cp>\u003Cstrong>The Stack\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Core app:\u003C/strong> Rails, Packwerk, React, TypeScript, Sidekiq\u003C/li>\n\u003Cli>\u003Cstrong>Mobile:\u003C/strong> iOS (Swift), Android (Kotlin)\u003C/li>\n\u003Cli>\u003Cstrong>Data, search & events:\u003C/strong> MySQL, Snowflake, dbt, Airflow, Weaviate, WarpStream, Hex, Sigma\u003C/li>\n\u003Cli>\u003Cstrong>Machine learning:\u003C/strong> deep learning, matrix factorization, retrieval & ranking, AWS SageMaker, MLflow\u003C/li>\n\u003Cli>\u003Cstrong>AI & dev tooling:\u003C/strong> Claude Code, Devin, Linear, CodeRabbit, Warden, LangChain, Bedrock AgentCore, Maxim\u003C/li>\n\u003Cli>\u003Cstrong>Infra & ops:\u003C/strong> AWS, Kubernetes, Terraform, GitHub Actions, Datadog, incident.io, LaunchDarkly\u003C/li>\n\u003Cli>\u003Cstrong>Key integrations:\u003C/strong> Shopify (payments), Iterable (CRM)\u003C/li>\n\u003C/ul>\n\u003Ch4>Why Babylist\u003C/h4>\n\u003Cp>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. 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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch4>How We Work\u003C/h4>\n\u003Cp>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. You'll work shoulder to shoulder with product, design and data, and with the partners across the business who rely on what you ship. You'll also stay close to customers yourself: sitting in on user interviews, watching session recordings, riding along with support. Here that's part of the engineering job, on a regular basis.\u003C/p>\n\u003Ch4>How We Hire\u003C/h4>\n\u003Cp>Three rounds, usually two to three weeks, start to finish.\u003C/p>\n\u003Col>\n\u003Cli>\u003Cstrong>Recruiter conversation (30 minutes).\u003C/strong> Trade context: what you want next, what we're building and straight answers on comp, team and remote.\u003C/li>\n\u003Cli>\u003Cstrong>Technical screen (1 hour).\u003C/strong> One round, no AI, language-agnostic. Reach for Google when you normally would. We just want to see how you reason from first principles.\u003C/li>\n\u003Cli>\u003Cstrong>Final round (4 hours).\u003C/strong> Four one-hour interviews: system design, AI-assisted coding with the tools you'd actually use here, product sense and culture and values. You'll hear back either way within 24 to 48 hours.\u003C/li>\n\u003C/ol>\n\u003Cp>If your timeline is tight, tell us and we'll move faster.\u003C/p>\n\u003Ch4>Benefits\u003C/h4>\n\u003Cul>\n\u003Cli>Company-paid medical and fully covered dental and vision\u003C/li>\n\u003Cli>A RRSP match\u003C/li>\n\u003Cli>Generous paid parental leave for birthing and non-birthing parents, plus a gradual return-to-work program\u003C/li>\n\u003Cli>Winter Wonder Week, a paid company-wide week off at the end of the year\u003C/li>\n\u003Cli>A remote-work stipend\u003C/li>\n\u003Cli>Mental-health and wellness support\u003C/li>\n\u003C/ul>\n\u003Ch4>A Few Things To Know\u003C/h4>\n\u003Cul>\n\u003Cli>We record and transcribe interviews to evaluate candidates, in line with applicable privacy laws.\u003C/li>\n\u003Cli>We expect you to use AI in your work and we welcome it in the process, but what you submit and say should reflect your own thinking.\u003C/li>\n\u003Cli>If you have a family member or close relationship with a Babylist employee, let your recruiter know.\u003C/li>\n\u003Cli>Official outreach only ever comes from an @babylist.com address.\u003C/li>\n\u003C/ul>","What The Role Is\nAs a Senior Engineer at Babylist, you take on hard problems and own them end-to-end. Millions of families depend on what we build. 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.\nWe'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. 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.\nWhat You'll Own\nA 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.\nWhat you do depends on what the team needs:\n\nFrame the problem with your PM as a peer, run the experiment and bring customer evidence into what gets built.\nHarden a critical path, kill a class of incidents or design the abstraction your team builds on.\nBe the reviewer people want on the risky changes.\nManage up with crisp choices: raise the risks early and protect the right tradeoffs.\nShare what you're learning about AI openly, so the whole team gets sharper.\n\nA few problems people at this level are working on right now:\n\nDeciding 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.\nBuilding the evals system that catches our AI support agent making things up before a customer does.\nMaking 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.\n\nWho You Are\nYou'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.\nThe 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.\nCompensation\nWe 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.\nHow We Build\nAI 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. 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.\nThe Stack\n\nCore app: Rails, Packwerk, React, TypeScript, Sidekiq\nMobile: iOS (Swift), Android (Kotlin)\nData, search & events: MySQL, Snowflake, dbt, Airflow, Weaviate, WarpStream, Hex, Sigma\nMachine learning: deep learning, matrix factorization, retrieval & ranking, AWS SageMaker, MLflow\nAI & dev tooling: Claude Code, Devin, Linear, CodeRabbit, Warden, LangChain, Bedrock AgentCore, Maxim\nInfra & ops: AWS, Kubernetes, Terraform, GitHub Actions, Datadog, incident.io, LaunchDarkly\nKey integrations: Shopify (payments), Iterable (CRM)\n\nWhy Babylist\nAn 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. 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.\nTen 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.\nHow We Work\nRemote-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. You'll work shoulder to shoulder with product, design and data, and with the partners across the business who rely on what you ship. You'll also stay close to customers yourself: sitting in on user interviews, watching session recordings, riding along with support. Here that's part of the engineering job, on a regular basis.\nHow We Hire\nThree rounds, usually two to three weeks, start to finish.\n\nRecruiter conversation (30 minutes). Trade context: what you want next, what we're building and straight answers on comp, team and remote.\nTechnical screen (1 hour). One round, no AI, language-agnostic. Reach for Google when you normally would. We just want to see how you reason from first principles.\nFinal round (4 hours). Four one-hour interviews: system design, AI-assisted coding with the tools you'd actually use here, product sense and culture and values. You'll hear back either way within 24 to 48 hours.\n\nIf your timeline is tight, tell us and we'll move faster.\nBenefits\n\nCompany-paid medical and fully covered dental and vision\nA RRSP match\nGenerous paid parental leave for birthing and non-birthing parents, plus a gradual return-to-work program\nWinter Wonder Week, a paid company-wide week off at the end of the year\nA remote-work stipend\nMental-health and wellness support\n\nA Few Things To Know\n\nWe record and transcribe interviews to evaluate candidates, in line with applicable privacy laws.\nWe expect you to use AI in your work and we welcome it in the process, but what you submit and say should reflect your own thinking.\nIf you have a family member or close relationship with a Babylist employee, let your recruiter know.\nOfficial outreach only ever comes from an @babylist.com address.",0,1786764934000,"2026-08-15 05:36:35","2026-08-14T17:53:48.000Z",255900,318600,"CAD",{"jsonldValid":13,"jsonld":27},"",{"jobs":29},[30,41,49,54,73,89],{"id":31,"slug":32,"title":33,"companyname":8,"companylogo":9,"companyTagline":10,"companyIndustry":11,"city":12,"country":12,"remote":13,"employmentType":34,"department":16,"content_html":35,"content_text":36,"years":19,"createdAt":20,"updatedAtISO":21,"postedAtISO":37,"hasSalary":13,"salaryMin":38,"salaryMax":39,"currency":25,"schema":40},"9dd136601945afe1253f208e1a8fb2e15502c39f8ec93301fbb99a756598034a","staff-software-engineer-at-babylist-1336192f7f","Staff Software Engineer",[15],"\u003Cp>\u003Cstrong>What The Role Is\u003C/strong>\u003C/p>\n\u003Cp>As a \u003Cstrong>Staff Engineer \u003C/strong>at Babylist, you own some of our hardest domains and decide where they go. Millions of families depend on what we build. 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. 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.\u003C/p>\n\u003Cp>You'll own a big piece of the product, but you won't be boxed into it. The roadmap is open. You have a say in which bets we make, and you pick what you take on next.\u003C/p>\n\u003Ch4>What You'll Own\u003C/h4>\n\u003Cp>A Staff Engineer here sets direction. You own a domain: a product surface, a platform area or a capability that cuts across several teams. You set where it's going over the next year or two, sequence the bets that get there and make the technical and product calls along the way. You're still in the code. We don't have architects who've stopped building. If you stepped away, multiple teams would feel it. Your influence shows up in the systems and the work other teams choose to build on. You don't need direct reports to have that reach. It comes from what you build.\u003C/p>\n\u003Cp>In practice, you:\u003C/p>\n\u003Cul>\n\u003Cli>Take a fuzzy business problem from the first sketch through to production, and stay on the hook for whether it actually helped customers.\u003C/li>\n\u003Cli>Build the platform or tooling other teams adopt by choice, and own it as it scales.\u003C/li>\n\u003Cli>Make the architecture calls that span teams and the ones that are expensive to reverse.\u003C/li>\n\u003Cli>Set the standard for how your domain builds with AI. Decide what good looks like, build the patterns and evals that get agents there and catch the output that's confidently wrong before it ships.\u003C/li>\n\u003Cli>Partner with product, design and data as a peer, shaping what's worth building from the start.\u003C/li>\n\u003Cli>Coach Senior engineers through the hard calls, the ambiguous ones as much as the technical ones.\u003C/li>\n\u003C/ul>\n\u003Cp>A few problems people at this level are working on right now:\u003C/p>\n\u003Cul>\n\u003Cli>Resolving one customer across registry, shop and health, plus the friends and family buying for them, so personalization works everywhere without each team rebuilding it.\u003C/li>\n\u003Cli>Designing the knowledge system our coding agents reliably load, and working out how much context actually helps before it starts to hurt.\u003C/li>\n\u003Cli>Building Early Investor, our new family finance product, from scratch, on a deadline that can't move.\u003C/li>\n\u003C/ul>\n\u003Ch4>Who You Are\u003C/h4>\n\u003Cp>You've shipped production systems for enough years to have earned strong opinions, and you hold them loosely. You can pick up an ambiguous problem and start moving before anyone hands you the full picture. You've already changed how a team builds with AI, and the new way stuck. Most Staff engineers lean one of two ways, and both do well here. Some point their depth at the systems everyone runs on: the platforms, the reliability and security bar, the harnesses that make AI produce good code. Others point it at the customer: framing the problem with PMs as peers, owning a journey end to end, deciding what to build and learning whether it worked. You don't have to be both. You do have to be excellent at one and fluent in the other.\u003C/p>\n\u003Cp>A few things that tend to be true of people who thrive here:\u003C/p>\n\u003Cul>\n\u003Cli>You measure yourself by impact: a customer outcome, or a system a dozen teams come to depend on.\u003C/li>\n\u003Cli>You're curious: you spot problems before they're filed and push your own ideas until they ship.\u003C/li>\n\u003C/ul>\n\u003Ch4>Compensation\u003C/h4>\n\u003Cp>We post real numbers. For a Canada-based Staff Engineer, the starting base salary range is $299,300 to $372,600 CAD, plus a target annual bonus of 20 percent of base. That's total target cash of roughly $359,160 to $447,120 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.\u003C/p>\n\u003Cp>\u003Cstrong>How We Build \u003Cbr>\u003Cbr>\u003C/strong>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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Cp>\u003Cstrong>The Stack\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Core app:\u003C/strong> Rails, Packwerk, React, TypeScript, Sidekiq\u003C/li>\n\u003Cli>\u003Cstrong>Mobile:\u003C/strong> iOS (Swift), Android (Kotlin)\u003C/li>\n\u003Cli>\u003Cstrong>Data, search & events:\u003C/strong> MySQL, Snowflake, dbt, Airflow, Weaviate, WarpStream, Hex, Sigma\u003C/li>\n\u003Cli>\u003Cstrong>Machine learning:\u003C/strong> deep learning, matrix factorization, retrieval & ranking, AWS SageMaker, MLflow\u003C/li>\n\u003Cli>\u003Cstrong>AI & dev tooling:\u003C/strong> Claude Code, Devin, Linear, CodeRabbit, Warden, LangChain, Bedrock AgentCore, Maxim\u003C/li>\n\u003Cli>\u003Cstrong>Infra & ops:\u003C/strong> AWS, Kubernetes, Terraform, GitHub Actions, Datadog, incident.io, LaunchDarkly\u003C/li>\n\u003Cli>\u003Cstrong>Key integrations:\u003C/strong> Shopify (payments), Iterable (CRM)\u003C/li>\n\u003C/ul>\n\u003Ch4>Why Babylist\u003C/h4>\n\u003Cp>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. 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.\u003C/p>\n\u003Cp>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.\u003C/p>\n\u003Ch4>How We Work\u003C/h4>\n\u003Cp>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. You'll work shoulder to shoulder with product, design and data, and with the partners across the business who rely on what you ship. You'll also stay close to customers yourself: sitting in on user interviews, watching session recordings, riding along with support. Here that's part of the engineering job, on a regular basis.\u003C/p>\n\u003Ch4>How We Hire\u003C/h4>\n\u003Cp>Three rounds, usually two to three weeks start to finish.\u003C/p>\n\u003Col>\n\u003Cli>\u003Cstrong>Recruiter conversation (30 minutes).\u003C/strong> Trade context: what you want next, what we're building and straight answers on comp, team and remote.\u003C/li>\n\u003Cli>\u003Cstrong>Technical screen (1 hour).\u003C/strong> One round, no AI, language-agnostic. Reach for Google when you normally would. We just want to see how you reason from first principles.\u003C/li>\n\u003Cli>\u003Cstrong>Final round (4 hours).\u003C/strong> Four one-hour interviews: system design, AI-assisted coding with the tools you'd actually use here, product sense and culture and values. You'll hear back either way within 24 to 48 hours.\u003C/li>\n\u003C/ol>\n\u003Cp>If your timeline is tight, tell us and we'll move faster.\u003C/p>\n\u003Ch4>Benefits\u003C/h4>\n\u003Cul>\n\u003Cli>Company-paid medical and fully covered dental and vision\u003C/li>\n\u003Cli>A RRSP match\u003C/li>\n\u003Cli>Generous paid parental leave for birthing and non-birthing parents, plus a gradual return-to-work program\u003C/li>\n\u003Cli>Winter Wonder Week, a paid company-wide week off at the end of the year\u003C/li>\n\u003Cli>A remote-work stipend\u003C/li>\n\u003Cli>Mental-health and wellness support\u003C/li>\n\u003C/ul>\n\u003Ch4>A Few Things To Know\u003C/h4>\n\u003Cul>\n\u003Cli>We record and transcribe interviews to evaluate candidates, in line with applicable privacy laws.\u003C/li>\n\u003Cli>We expect you to use AI in your work and we welcome it in the process, but what you submit and say should reflect your own thinking.\u003C/li>\n\u003Cli>If you have a family member or close relationship with a Babylist employee, let your recruiter know.\u003C/li>\n\u003Cli>Official outreach only ever comes from an @babylist.com address\u003C/li>\n\u003C/ul>","What The Role Is\nAs a Staff Engineer at Babylist, you own some of our hardest domains and decide where they go. Millions of families depend on what we build. 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. 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.\nYou'll own a big piece of the product, but you won't be boxed into it. The roadmap is open. You have a say in which bets we make, and you pick what you take on next.\nWhat You'll Own\nA Staff Engineer here sets direction. You own a domain: a product surface, a platform area or a capability that cuts across several teams. You set where it's going over the next year or two, sequence the bets that get there and make the technical and product calls along the way. You're still in the code. We don't have architects who've stopped building. If you stepped away, multiple teams would feel it. Your influence shows up in the systems and the work other teams choose to build on. You don't need direct reports to have that reach. It comes from what you build.\nIn practice, you:\n\nTake a fuzzy business problem from the first sketch through to production, and stay on the hook for whether it actually helped customers.\nBuild the platform or tooling other teams adopt by choice, and own it as it scales.\nMake the architecture calls that span teams and the ones that are expensive to reverse.\nSet the standard for how your domain builds with AI. Decide what good looks like, build the patterns and evals that get agents there and catch the output that's confidently wrong before it ships.\nPartner with product, design and data as a peer, shaping what's worth building from the start.\nCoach Senior engineers through the hard calls, the ambiguous ones as much as the technical ones.\n\nA few problems people at this level are working on right now:\n\nResolving one customer across registry, shop and health, plus the friends and family buying for them, so personalization works everywhere without each team rebuilding it.\nDesigning the knowledge system our coding agents reliably load, and working out how much context actually helps before it starts to hurt.\nBuilding Early Investor, our new family finance product, from scratch, on a deadline that can't move.\n\nWho You Are\nYou've shipped production systems for enough years to have earned strong opinions, and you hold them loosely. You can pick up an ambiguous problem and start moving before anyone hands you the full picture. You've already changed how a team builds with AI, and the new way stuck. Most Staff engineers lean one of two ways, and both do well here. Some point their depth at the systems everyone runs on: the platforms, the reliability and security bar, the harnesses that make AI produce good code. Others point it at the customer: framing the problem with PMs as peers, owning a journey end to end, deciding what to build and learning whether it worked. You don't have to be both. You do have to be excellent at one and fluent in the other.\nA few things that tend to be true of people who thrive here:\n\nYou measure yourself by impact: a customer outcome, or a system a dozen teams come to depend on.\nYou're curious: you spot problems before they're filed and push your own ideas until they ship.\n\nCompensation\nWe post real numbers. For a Canada-based Staff Engineer, the starting base salary range is $299,300 to $372,600 CAD, plus a target annual bonus of 20 percent of base. That's total target cash of roughly $359,160 to $447,120 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.\nHow We Build 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.\nThe 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.\nThe Stack\n\nCore app: Rails, Packwerk, React, TypeScript, Sidekiq\nMobile: iOS (Swift), Android (Kotlin)\nData, search & events: MySQL, Snowflake, dbt, Airflow, Weaviate, WarpStream, Hex, Sigma\nMachine learning: deep learning, matrix factorization, retrieval & ranking, AWS SageMaker, MLflow\nAI & dev tooling: Claude Code, Devin, Linear, CodeRabbit, Warden, LangChain, Bedrock AgentCore, Maxim\nInfra & ops: AWS, Kubernetes, Terraform, GitHub Actions, Datadog, incident.io, LaunchDarkly\nKey integrations: Shopify (payments), Iterable (CRM)\n\nWhy Babylist\nAn 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. 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.\nTen 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.\nHow We Work\nRemote-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. You'll work shoulder to shoulder with product, design and data, and with the partners across the business who rely on what you ship. You'll also stay close to customers yourself: sitting in on user interviews, watching session recordings, riding along with support. Here that's part of the engineering job, on a regular basis.\nHow We Hire\nThree rounds, usually two to three weeks start to finish.\n\nRecruiter conversation (30 minutes). Trade context: what you want next, what we're building and straight answers on comp, team and remote.\nTechnical screen (1 hour). One round, no AI, language-agnostic. Reach for Google when you normally would. We just want to see how you reason from first principles.\nFinal round (4 hours). Four one-hour interviews: system design, AI-assisted coding with the tools you'd actually use here, product sense and culture and values. You'll hear back either way within 24 to 48 hours.\n\nIf your timeline is tight, tell us and we'll move faster.\nBenefits\n\nCompany-paid medical and fully covered dental and vision\nA RRSP match\nGenerous paid parental leave for birthing and non-birthing parents, plus a gradual return-to-work program\nWinter Wonder Week, a paid company-wide week off at the end of the year\nA remote-work stipend\nMental-health and wellness support\n\nA Few Things To Know\n\nWe record and transcribe interviews to evaluate candidates, in line with applicable privacy laws.\nWe expect you to use AI in your work and we welcome it in the process, but what you submit and say should reflect your own thinking.\nIf you have a family member or close relationship with a Babylist employee, let your recruiter know.\nOfficial outreach only ever comes from an @babylist.com address","2026-08-14T17:53:46.000Z",299300,372600,{"jsonldValid":13,"jsonld":27},{"id":42,"slug":43,"title":7,"companyname":8,"companylogo":9,"companyTagline":10,"companyIndustry":11,"city":12,"country":12,"remote":13,"employmentType":44,"department":16,"content_html":17,"content_text":18,"years":19,"createdAt":45,"updatedAtISO":46,"postedAtISO":47,"hasSalary":13,"salaryMin":23,"salaryMax":24,"currency":25,"schema":48},"4693e69b89cc9a61f37fa8294db9ec068f37c5238934828c13c7415fc194af92","senior-software-engineer-at-babylist-be9fb5d8da",[15],1784950259000,"2026-07-25 05:31:33","2026-07-17T18:59:53.000Z",{"jsonldValid":13,"jsonld":27},{"id":50,"slug":51,"title":33,"companyname":8,"companylogo":9,"companyTagline":10,"companyIndustry":11,"city":12,"country":12,"remote":13,"employmentType":52,"department":16,"content_html":35,"content_text":36,"years":19,"createdAt":45,"updatedAtISO":46,"postedAtISO":47,"hasSalary":13,"salaryMin":38,"salaryMax":39,"currency":25,"schema":53},"390b996fabd114d8f078c5d27fe40789b5615e43e0d664678f522830278a9a87","staff-software-engineer-at-babylist-abd260fe1a",[15],{"jsonldValid":13,"jsonld":27},{"id":55,"slug":56,"title":57,"companyname":58,"companylogo":59,"companyTagline":60,"companyIndustry":61,"city":62,"country":63,"remote":13,"employmentType":64,"department":65,"content_html":66,"content_text":67,"years":19,"createdAt":68,"updatedAtISO":69,"postedAtISO":70,"hasSalary":13,"salaryMin":19,"salaryMax":19,"currency":71,"schema":72},"33a2f83af193e3e6fae05b2f14ea32f432b36fab859588e934897a9e500dbc15","campaign-developer-marketo-at-icuc-84496c2fc3","Campaign Developer - Marketo","ICUC","https://logo.clearbit.com/icuc.social","We stay awake 24/7 👀 answering and understanding your global customers and fans on social media so you don't have to.","Marketing Services","India - Maharashtra- Pune - Baner - Amar Madhuban Tech Park","India",[15],"Marketing","\u003Cp>\u003Cb>Job Description:\u003C/b>\u003C/p>\u003Cp>\u003Cb>Job Description – Marketo Specialist\u003C/b>\u003C/p>\u003Cp>\u003Cb>Position Summary\u003C/b>\u003C/p>\u003Cp>We are seeking a skilled Marketo Specialist with hands-on experience in Adobe Marketo Engage to execute and manage marketing automation campaigns. The ideal candidate should possess a strong understanding of Marketo architecture, lead management, campaign execution, asset creation, reporting, and marketing operations best practices. Understanding about how Marketo integrates with CRM systems and third-party platforms.\u003C/p>\u003Cp>\u003Cb>Key Responsibilities:\u003C/b>\u003C/p>\u003Cul>\u003Cli>Setup, test and execute marketing emails, landing pages, forms, audience lists and flows for demand generations programs and more complex trigger, drip, and nurture campaigns.\u003C/li>\u003Cli>Execution of end-to-end campaigns; develop cohesive automated workflows and pulling targeted lists.\u003C/li>\u003Cli>Support essential marketing operations initiatives in Marketo, Salesforce and other marketing automation technologies.\u003C/li>\u003Cli>Understand and report on campaign metrics and distribute campaign performance reports as needed.\u003C/li>\u003Cli>Handle requests for special reports, data, and marketing tracking information.\u003C/li>\u003Cli>Troubleshoot Marketo related issues as needed.\u003C/li>\u003Cli>Assuring the accuracy, reliability, and consistency of marketing automation production services prior to final output/delivery.\u003C/li>\u003Cli>Assess content to ensure consistent and accurate branding and design and identify any issues.\u003C/li>\u003Cli>Ensure a thorough understanding of requirements, both from Merkle and our clients.\u003C/li>\u003Cli>Accurately maintain quality reports and relevant documentation.\u003C/li>\u003C/ul>\u003Cp>\u003Cb>Required Skills & Qualifications\u003C/b>\u003C/p>\u003Cul>\u003Cli>2+ years of hands-on experience building and executing campaigns in Adobe Marketo Engage.\u003C/li>\u003Cli>Strong working knowledge of Smart Campaigns, Smart Lists, Flow Steps, Programs, Channels\u003C/li>\u003Cli>Proven experience building emails, landing pages, forms, snippets, and templates from scratch.\u003C/li>\u003Cli>Solid understanding of tokens and dynamic/personalized content setup.\u003C/li>\u003Cli>Demonstrated understanding of lead lifecycle management, lead scoring, and lead routing concepts.\u003C/li>\u003Cli>General understanding of how Marketo integrates with a CRM and other martech tools — conceptual fluency is required, but active integration ownership is not part of this role.\u003C/li>\u003Cli>Experience with basic HTML/CSS for email and landing page troubleshooting is a plus.\u003C/li>\u003Cli>Strong attention to detail, QA discipline, and ability to manage multiple campaigns/programs simultaneously.\u003C/li>\u003Cli>Marketo Certified Expert (MCE) preferred.\u003C/li>\u003Cli>Excellent communication and stakeholder management abilities.\u003C/li>\u003C/ul>\u003Cp>\u003Cb>Location:\u003C/b>\u003C/p>India - Maharashtra- Pune - Baner - Amar Madhuban Tech Park\u003Cp>\u003Cb>Brand:\u003C/b>\u003C/p>Merkle\u003Cp>\u003Cb>Time Type:\u003C/b>\u003C/p>Full time\u003Cp>\u003Cb>Contract Type:\u003C/b>\u003C/p>Permanent","Job Description:Job Description – Marketo SpecialistPosition SummaryWe are seeking a skilled Marketo Specialist with hands-on experience in Adobe Marketo Engage to execute and manage marketing automation campaigns. The ideal candidate should possess a strong understanding of Marketo architecture, lead management, campaign execution, asset creation, reporting, and marketing operations best practices. Understanding about how Marketo integrates with CRM systems and third-party platforms.Key Responsibilities:Setup, test and execute marketing emails, landing pages, forms, audience lists and flows for demand generations programs and more complex trigger, drip, and nurture campaigns.Execution of end-to-end campaigns; develop cohesive automated workflows and pulling targeted lists.Support essential marketing operations initiatives in Marketo, Salesforce and other marketing automation technologies.Understand and report on campaign metrics and distribute campaign performance reports as needed.Handle requests for special reports, data, and marketing tracking information.Troubleshoot Marketo related issues as needed.Assuring the accuracy, reliability, and consistency of marketing automation production services prior to final output/delivery.Assess content to ensure consistent and accurate branding and design and identify any issues.Ensure a thorough understanding of requirements, both from Merkle and our clients.Accurately maintain quality reports and relevant documentation.Required Skills & Qualifications2+ years of hands-on experience building and executing campaigns in Adobe Marketo Engage.Strong working knowledge of Smart Campaigns, Smart Lists, Flow Steps, Programs, ChannelsProven experience building emails, landing pages, forms, snippets, and templates from scratch.Solid understanding of tokens and dynamic/personalized content setup.Demonstrated understanding of lead lifecycle management, lead scoring, and lead routing concepts.General understanding of how Marketo integrates with a CRM and other martech tools — conceptual fluency is required, but active integration ownership is not part of this role.Experience with basic HTML/CSS for email and landing page troubleshooting is a plus.Strong attention to detail, QA discipline, and ability to manage multiple campaigns/programs simultaneously.Marketo Certified Expert (MCE) preferred.Excellent communication and stakeholder management abilities.Location:India - Maharashtra- Pune - Baner - Amar Madhuban Tech ParkBrand:MerkleTime Type:Full timeContract Type:Permanent",1786808006000,"2026-08-15 17:33:48","2026-08-15T15:33:48.000Z","INR",{"jsonldValid":13,"jsonld":27},{"id":74,"slug":75,"title":76,"companyname":77,"companylogo":78,"companyTagline":79,"companyIndustry":80,"city":81,"country":82,"remote":13,"employmentType":83,"department":16,"content_html":84,"content_text":85,"years":19,"createdAt":68,"updatedAtISO":69,"postedAtISO":86,"hasSalary":13,"salaryMin":19,"salaryMax":19,"currency":87,"schema":88},"42c47f00eb7d12702ba5628346ae036b122a5b40f5eeea33f7f3c6ebee3d879f","data-platform-engineer-at-evismarttm-9b41963a05","Data Platform Engineer","EviSmart™","https://logo.clearbit.com/evismart.com","The world's leading AI-Powered Dental Workflow Automation and Dental CAD Design outsourcing company","Software Development","BGC","Taguig City",[15],"\u003Ch1>\u003Cstrong>\u003Cspan>Data Architect\u003C/span>\u003C/strong>\u003C/h1>\n\u003Cp>\u003Cstrong>\u003Cspan>In-house . Full Time . On-Site at BGC, Taguig. Dayshift Schedule\u003Cbr>\u003Cbr>About the Role\u003C/span>\u003C/strong> \u003C/p>\n\u003Cp>We're looking for a Data Engineer to own our company's single source of truth for data. This isn't a back-office infrastructure role — it's the foundation that makes every team's decisions better, from Sales and Finance to the product teams building our newest tools. \u003C/p>\n\u003Cp>You'll be responsible for the full data platform: getting data in cleanly from every system we use, structuring it into one trusted warehouse, and making sure that no matter where someone looks across the company, the numbers always match. You'll also help make that data easy enough to use that our teams (and our AI tools) can self-serve most of their own analysis, with you and your team focused on keeping the foundation rock solid. \u003Cbr>\u003Cbr>\u003C/p>\n\u003Cp>\u003Cstrong>Who this suits:\u003C/strong> We need someone who \u003Cstrong>o\u003C/strong>\u003Cem>\u003Cstrong>wns our data from the moment it's entered,\u003C/strong>\u003C/em> not just once it reaches the warehouse. If you are a data professional who wants influence over the source systems, not only the pipeline. If you've ever been handed dirty data and wished you could fix it at the form instead of the query, this is that job\u003C/p>\n\n\u003Cp>\u003Cstrong>\u003Cspan>What You'll Own\u003C/span>\u003C/strong> \u003C/p>\n\u003Cul>\n\u003Cli>Data pipelines: build and run reliable, automated pipelines that bring data in from every system we use — our in-house portals, HubSpot, QuickBooks, Jira, and more — into one central warehouse. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>One source of truth: maintain a single, trusted customer and business record so that every team and every system shows the same numbers, every time. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Data quality: catch and fix data issues before anyone downstream notices them. You own the monitoring, not the complaints. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Proactive delivery: work directly with teams across the company to understand what data they need, and have it ready — clean, structured, and refreshed in near real-time — before they have to ask. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Safe change management: review any change to how a system structures its data before it ships, so changes never quietly break the warehouse or any report built on it. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Self-serve enablement: structure and document data well enough that our teams, and our AI tools, can query it directly and get the right answer without needing a custom report built for them. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Team leadership: manage and grow 2 data engineers. Support a dedicated data analyst with the access and platform tools they need to deliver deeper, custom insights for leadership and the teams they work with. \u003C/li>\n\u003C/ul>\n\n\u003Cp>\u003Cstrong>\u003Cspan>What Success Looks Like\u003C/span>\u003C/strong> \u003C/p>\n\u003Cul>\n\u003Cli>Pull the same number from two different systems — they always match. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Every team has the data they need, when they need it, without feeling blocked. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Data lands clean and on time, with zero quality issues reaching a team before you've already caught and fixed them. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Our AI tools and internal teams can ask a data question directly and get an accurate answer, without a custom report being built for them. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>When any system changes how it structures data, nothing breaks downstream — because you reviewed it first. \u003C/li>\n\u003C/ul>\n\n\u003Cp>\u003Cstrong>\u003Cspan>How Success Is Measured\u003C/span>\u003C/strong> \u003C/p>\n\u003Cp>Performance is tracked against a few simple, outcome-based numbers — not a long list of technical metrics. \u003C/p>\n\u003Ctable>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\n\u003Cp>\u003Cstrong>KPI\u003C/strong> \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>\u003Cstrong>Target\u003C/strong> \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>\u003Cstrong>What It Means\u003C/strong> \u003C/p>\n\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\n\u003Cp>Data Availability \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>99%+ \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>Data pipelines run on schedule and the warehouse is up and accessible when teams need it. \u003C/p>\n\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\n\u003Cp>Data Accuracy \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>99%+ \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>Numbers match across every system. Zero data quality issues reach a team before they've already been caught and fixed. \u003C/p>\n\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\n\u003Cp>Data Accessibility \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>99%+ \u003C/p>\n\u003C/td>\n\u003Ctd>\n\u003Cp>Teams and AI tools can get the data they need, when they need it, through self-serve access — without being blocked or waiting on a custom report. \u003C/p>\n\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\n\n\u003Cul>\n\u003Cli>4+ years of experience in data engineering, with a track record of owning a production data warehouse or platform end to end. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Strong SQL skills and hands-on experience with modern data pipeline and ETL/ELT tools (e.g. dbt, Airflow, Fivetran, or similar). \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Experience working with a layered warehouse architecture (medallion architecture — bronze/silver/gold). \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Hands-on experience with Databricks and Azure cloud services (e.g. Azure Data Factory, Azure Data Lake, Azure SQL). \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Comfort integrating data from a mix of in-house systems and third-party platforms (CRM, finance, project management tools). \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Experience exposing data via APIs, or working with teams that consume data through APIs. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Some experience with, or strong interest in, the data needs of ML/AI pipelines — you don't need to build models, but you understand what clean, structured data they require. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>People management experience, or strong readiness to manage and grow a small team. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Clear communicator who's comfortable partnering directly with non-technical teams to understand what they need. \u003C/li>\n\u003C/ul>\n\n\u003Cp>\u003Cstrong>\u003Cspan>Nice to Have\u003C/span>\u003C/strong> \u003C/p>\n\u003Cul>\n\u003Cli>Experience working in a fast-growing or scaling company where the data platform was built (or rebuilt) from the ground up. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Familiarity with Python for data tooling and automation. \u003C/li>\n\u003C/ul>\n\u003Cul>\n\u003Cli>Experience setting data governance standards or leading data quality initiatives. \u003C/li>\n\u003C/ul>\n\n\u003Cp>\u003Cstrong>\u003Cspan>Why This Role Matters\u003C/span>\u003C/strong> \u003C/p>\n\u003Cp>The data platform you'll own is the foundation for everything we're building next — from AI-powered tools to new internal products that depend on clean, real-time data. If you want to be the person who makes sure the whole company can trust its numbers, this is that role. \u003C/p>","Data Architect\nIn-house . Full Time . On-Site at BGC, Taguig. Dayshift ScheduleAbout the Role \nWe're looking for a Data Engineer to own our company's single source of truth for data. This isn't a back-office infrastructure role — it's the foundation that makes every team's decisions better, from Sales and Finance to the product teams building our newest tools. \nYou'll be responsible for the full data platform: getting data in cleanly from every system we use, structuring it into one trusted warehouse, and making sure that no matter where someone looks across the company, the numbers always match. You'll also help make that data easy enough to use that our teams (and our AI tools) can self-serve most of their own analysis, with you and your team focused on keeping the foundation rock solid. \nWho this suits: We need someone who owns our data from the moment it's entered, not just once it reaches the warehouse. If you are a data professional who wants influence over the source systems, not only the pipeline. If you've ever been handed dirty data and wished you could fix it at the form instead of the query, this is that job\n\nWhat You'll Own \n\nData pipelines: build and run reliable, automated pipelines that bring data in from every system we use — our in-house portals, HubSpot, QuickBooks, Jira, and more — into one central warehouse. \n\n\nOne source of truth: maintain a single, trusted customer and business record so that every team and every system shows the same numbers, every time. \n\n\nData quality: catch and fix data issues before anyone downstream notices them. You own the monitoring, not the complaints. \n\n\nProactive delivery: work directly with teams across the company to understand what data they need, and have it ready — clean, structured, and refreshed in near real-time — before they have to ask. \n\n\nSafe change management: review any change to how a system structures its data before it ships, so changes never quietly break the warehouse or any report built on it. \n\n\nSelf-serve enablement: structure and document data well enough that our teams, and our AI tools, can query it directly and get the right answer without needing a custom report built for them. \n\n\nTeam leadership: manage and grow 2 data engineers. Support a dedicated data analyst with the access and platform tools they need to deliver deeper, custom insights for leadership and the teams they work with. \n\n\nWhat Success Looks Like \n\nPull the same number from two different systems — they always match. \n\n\nEvery team has the data they need, when they need it, without feeling blocked. \n\n\nData lands clean and on time, with zero quality issues reaching a team before you've already caught and fixed them. \n\n\nOur AI tools and internal teams can ask a data question directly and get an accurate answer, without a custom report being built for them. \n\n\nWhen any system changes how it structures data, nothing breaks downstream — because you reviewed it first. \n\n\nHow Success Is Measured \nPerformance is tracked against a few simple, outcome-based numbers — not a long list of technical metrics. \n\n\n\n\nKPI \n\n\nTarget \n\n\nWhat It Means \n\n\n\n\nData Availability \n\n\n99%+ \n\n\nData pipelines run on schedule and the warehouse is up and accessible when teams need it. \n\n\n\n\nData Accuracy \n\n\n99%+ \n\n\nNumbers match across every system. Zero data quality issues reach a team before they've already been caught and fixed. \n\n\n\n\nData Accessibility \n\n\n99%+ \n\n\nTeams and AI tools can get the data they need, when they need it, through self-serve access — without being blocked or waiting on a custom report. \n\n\n\n\n\n\n4+ years of experience in data engineering, with a track record of owning a production data warehouse or platform end to end. \n\n\nStrong SQL skills and hands-on experience with modern data pipeline and ETL/ELT tools (e.g. dbt, Airflow, Fivetran, or similar). \n\n\nExperience working with a layered warehouse architecture (medallion architecture — bronze/silver/gold). \n\n\nHands-on experience with Databricks and Azure cloud services (e.g. Azure Data Factory, Azure Data Lake, Azure SQL). \n\n\nComfort integrating data from a mix of in-house systems and third-party platforms (CRM, finance, project management tools). \n\n\nExperience exposing data via APIs, or working with teams that consume data through APIs. \n\n\nSome experience with, or strong interest in, the data needs of ML/AI pipelines — you don't need to build models, but you understand what clean, structured data they require. \n\n\nPeople management experience, or strong readiness to manage and grow a small team. \n\n\nClear communicator who's comfortable partnering directly with non-technical teams to understand what they need. \n\n\nNice to Have \n\nExperience working in a fast-growing or scaling company where the data platform was built (or rebuilt) from the ground up. \n\n\nFamiliarity with Python for data tooling and automation. \n\n\nExperience setting data governance standards or leading data quality initiatives. \n\n\nWhy This Role Matters \nThe data platform you'll own is the foundation for everything we're building next — from AI-powered tools to new internal products that depend on clean, real-time data. If you want to be the person who makes sure the whole company can trust its numbers, this is that role.","2026-08-13T03:24:50.000Z","USD",{"jsonldValid":13,"jsonld":27},{"id":90,"slug":91,"title":92,"companyname":93,"companylogo":94,"companyTagline":95,"companyIndustry":96,"city":97,"country":97,"remote":13,"employmentType":98,"department":99,"content_html":100,"content_text":101,"years":19,"createdAt":20,"updatedAtISO":102,"postedAtISO":103,"hasSalary":13,"salaryMin":19,"salaryMax":19,"currency":87,"schema":104},"6197311a92988b223b7435d82b13d343a77c01be2aa14016261445198487ff1a","business-development-representative-healthcare-technology-at-provider1st-d6e20deb2b","Business Development Representative (Healthcare Technology)","Provider1st","https://logo.clearbit.com/provider1st.com","Enabling providers to improve revenue and reduce administrative burden","Medical Practices","United States",[15],"Other","\u003Cp>\u003Cstrong>About Us:\u003C/strong>\u003C/p>\u003Cp>At Provider1st, we simplify the Release of Information (ROI) process for healthcare providers. By offering compliant, efficient, and patient first ROI services, we help healthcare organizations focus on what matters most—caring for patients. We're a fast-growing company committed to exceptional service, innovative technology, and building lasting relationships with our clients.\u003C/p>\u003Cp>About Provider1st Video \u003C/p>\u003Cp>\u003Cstrong>Position Summary:\u003C/strong>\u003C/p>\u003Cp>Provider1st is where your Sales Development career can accelerate. We move fast, think boldly, and empower you to do the best work of your life. You’ll be surrounded by teammates who care deeply, challenge each other, and celebrate wins. Provider1st is growing and looking for passionate, talented individuals to join our Sales Development team!  \u003C/p>\u003Cp>We are looking for motivated SDRs to kickstart new business by prospecting, researching, and connecting with healthcare providers. In this role, you’ll help open doors, set meetings with decision-makers, and build the pipeline that fuels our growing sales team’s success.  \u003C/p>\u003Cp>The SDR role is designed for someone eager to grow their career within the healthcare segment, work closely with top performing Account Executives, and help expand Provider1st’s reach across the healthcare marketplace. \u003C/p>\u003Cp>About Business Development Representative Video \u003C/p>\u003Cp>\u003Cstrong>About the role:\u003C/strong>\u003C/p>\u003Cul>\u003Cli>Provider1st is looking for a self-starter BDR with a demonstrated track record of top performance, ability to receive and incorporate feedback, and excitement to grow a career in the healthcare space. \u003C/li>\u003Cli>This foundational position will report to the Manager of Business Development and will be responsible for prospecting, identifying, and qualifying sales opportunities for the Provider1st Sales team. \u003C/li>\u003Cli>This role is extremely important within the sales organization at Provider1st and will help lay the foundation of our success. \u003C/li>\u003Cli>In this role, you are responsible for generating pipeline for the sales team. \u003C/li>\u003Cli>Our Sales Development Representatives are specialists in researching prospects, discovering pain points, getting access to and setting meetings with decision makers. \u003C/li>\u003Cli>This role allows our Field Sales Team to focus on conducting meetings with prospects and increasing the overall productivity of our sales organization. \u003C/li>\u003C/ul>\u003Cp>\u003Cstrong>You will:\u003C/strong>\u003C/p>\u003Cul>\u003Cli>Identify and engage senior-level executives within the healthcare market, building a robust sales pipeline for our Account Executives. \u003C/li>\u003Cli>Generate new business opportunities by prospecting, researching, and outbounding into identified accounts and warm leads across various segments of healthcare provider groups. \u003C/li>\u003Cli>Research, develop, and execute a strategic outbound sales plan by mapping out targeted accounts and driving opportunities. \u003C/li>\u003Cli>Educate prospective leads on the full suite of Provider1st solutions, focusing on how our products solve real pain points within in their management and release of healthcare information. \u003C/li>\u003Cli>Help prospects understand the business impact Provider1st can deliver, ensuring your conversations are rooted in their needs and challenges. \u003C/li>\u003Cli>Establish strong, trusting relationships with both internal team members and external stakeholders, building confidence in the value Provider1st brings. \u003C/li>\u003Cli>Conduct high level qualification conversations with decision makers. \u003C/li>\u003Cli>Effectively communicate the value of Provider1st and our products to potential customers. \u003C/li>\u003Cli>Align and collaborate with stakeholders across sales, product, and marketing. \u003C/li>\u003Cli>Achieve or exceed monthly and quarterly quotas of qualified opportunities. \u003C/li>\u003Cli>Ensure all interactions and engagements are logged and tracked in the CRM system \u003C/li>\u003Cli>Identify creative approaches to engage and build trust with prospects \u003C/li>\u003Cli>100% responsible for generating targeted prospect list, messaging and research \u003C/li>\u003Cli>Ability to forecast your business, pipeline and targets backed by data \u003C/li>\u003C/ul>\u003Cbr>\u003Ch2>Requirements\u003C/h2>\u003Cul>\u003Cli>2+ year of experience targeting new prospects, demonstrating a strong ability to uncover opportunities and engaging decision-makers. \u003C/li>\u003Cli>Demonstrated skill in communicating in a concise and compelling way to mid/senior-level executives across multiple departments. \u003C/li>\u003Cli>The ability to assess prospects’ needs, personalize your outreach, and uncover high-probability opportunities that align with their business challenges. \u003C/li>\u003Cli>Experience creating, executing, and maintaining a well-structured prospecting plan that drives results. \u003C/li>\u003Cli>An eagerness to understand market trends, customer pain points, and organizational changes to improve the effectiveness of your outreach. \u003C/li>\u003Cli>Experience with go-to-market (GTM) technologies like HubSpot, Outlook, and ZoomInfo is a plus. \u003C/li>\u003Cli>Adaptability and the ability to thrive in a fast-paced environment and always be thinking of new ways to drive engagement and pipeline. \u003C/li>\u003Cli>Success working remotely and a strong home set up for being successful \u003C/li>\u003Cli>Grit, strong work ethic, coachable, confident, curious, self-aware and focused on self-development. \u003C/li>\u003C/ul>\u003Cbr>\u003Ch2>Benefits\u003C/h2>\u003Cul>\u003Cli>Opportunity to make a real impact on our business and our customers\u003C/li>\u003C/ul>\u003Cul>\u003Cli>Collaborative, mission-driven culture with growth opportunities\u003C/li>\u003Cli>Remote-friendly workplace\u003C/li>\u003Cli>Medical/Dental/Vision/Life Insurance\u003C/li>\u003C/ul>","About Us:At Provider1st, we simplify the Release of Information (ROI) process for healthcare providers. By offering compliant, efficient, and patient first ROI services, we help healthcare organizations focus on what matters most—caring for patients. We're a fast-growing company committed to exceptional service, innovative technology, and building lasting relationships with our clients.About Provider1st Video Position Summary:Provider1st is where your Sales Development career can accelerate. We move fast, think boldly, and empower you to do the best work of your life. You’ll be surrounded by teammates who care deeply, challenge each other, and celebrate wins. Provider1st is growing and looking for passionate, talented individuals to join our Sales Development team!  We are looking for motivated SDRs to kickstart new business by prospecting, researching, and connecting with healthcare providers. In this role, you’ll help open doors, set meetings with decision-makers, and build the pipeline that fuels our growing sales team’s success.  The SDR role is designed for someone eager to grow their career within the healthcare segment, work closely with top performing Account Executives, and help expand Provider1st’s reach across the healthcare marketplace. About Business Development Representative Video About the role:Provider1st is looking for a self-starter BDR with a demonstrated track record of top performance, ability to receive and incorporate feedback, and excitement to grow a career in the healthcare space. This foundational position will report to the Manager of Business Development and will be responsible for prospecting, identifying, and qualifying sales opportunities for the Provider1st Sales team. This role is extremely important within the sales organization at Provider1st and will help lay the foundation of our success. In this role, you are responsible for generating pipeline for the sales team. Our Sales Development Representatives are specialists in researching prospects, discovering pain points, getting access to and setting meetings with decision makers. This role allows our Field Sales Team to focus on conducting meetings with prospects and increasing the overall productivity of our sales organization. You will:Identify and engage senior-level executives within the healthcare market, building a robust sales pipeline for our Account Executives. Generate new business opportunities by prospecting, researching, and outbounding into identified accounts and warm leads across various segments of healthcare provider groups. Research, develop, and execute a strategic outbound sales plan by mapping out targeted accounts and driving opportunities. Educate prospective leads on the full suite of Provider1st solutions, focusing on how our products solve real pain points within in their management and release of healthcare information. Help prospects understand the business impact Provider1st can deliver, ensuring your conversations are rooted in their needs and challenges. Establish strong, trusting relationships with both internal team members and external stakeholders, building confidence in the value Provider1st brings. Conduct high level qualification conversations with decision makers. Effectively communicate the value of Provider1st and our products to potential customers. Align and collaborate with stakeholders across sales, product, and marketing. Achieve or exceed monthly and quarterly quotas of qualified opportunities. Ensure all interactions and engagements are logged and tracked in the CRM system Identify creative approaches to engage and build trust with prospects 100% responsible for generating targeted prospect list, messaging and research Ability to forecast your business, pipeline and targets backed by data Requirements2+ year of experience targeting new prospects, demonstrating a strong ability to uncover opportunities and engaging decision-makers. Demonstrated skill in communicating in a concise and compelling way to mid/senior-level executives across multiple departments. The ability to assess prospects’ needs, personalize your outreach, and uncover high-probability opportunities that align with their business challenges. Experience creating, executing, and maintaining a well-structured prospecting plan that drives results. An eagerness to understand market trends, customer pain points, and organizational changes to improve the effectiveness of your outreach. Experience with go-to-market (GTM) technologies like HubSpot, Outlook, and ZoomInfo is a plus. Adaptability and the ability to thrive in a fast-paced environment and always be thinking of new ways to drive engagement and pipeline. Success working remotely and a strong home set up for being successful Grit, strong work ethic, coachable, confident, curious, self-aware and focused on self-development. BenefitsOpportunity to make a real impact on our business and our customersCollaborative, mission-driven culture with growth opportunitiesRemote-friendly workplaceMedical/Dental/Vision/Life Insurance","2026-08-15 05:36:36","2026-08-15T03:36:36.000Z",{"jsonldValid":13,"jsonld":27},1786869730953]