Staff Product Engineer, Developer Experience

About Ancestry:

When you join Ancestry, you join a human-centered company where every person’s story is important. Ancestry®, the global leader in family history, connects everyone with their past so they can discover, preserve, and share their unique family stories. With our unparalleled collection of more than 65 billion records, over 3.5 million subscribers, and over 27 million people in our growing DNA network, customers can discover their family story and gain a new level of understanding about their lives. Over the past 40 years, we’ve built trusted relationships with millions of people who have chosen us as the platform for discovering, preserving, and sharing the most important information about themselves and their families.

We are committed to our location flexible work approach, allowing you to choose to work in the nearest office, from your home, or a hybrid of both (subject to location restrictions and roles that are required to be in the office- ). We will continue to hire and promote beyond the boundaries of our office locations, to enable broadened possibilities for employee diversity.

Together, we work every day to foster a work environment that’s inclusive as well as diverse, and where our people can be themselves. Every idea and perspective is valued so that our products and services reflect the global and diverse clients we serve.

Ancestry encourages applications from minorities, women, the disabled, protected veterans and all other qualified applicants. Passionate about dedicating your work to enriching people’s lives? Join the curious.

Engineering Productivity owns how software gets made at Ancestry. We run the CI/CD platform that every service ships through, and we own the tools where the work happens day-to-day: GitHub, Harness, Jira, Confluence, and Figma. On top of those, we build our own platforms, including internal services for cost governance, developer metadata, and entity APIs, and CLI tooling that puts AI agents into everyday engineering workflows.

Our customers are the engineers, product managers, and designers of Ancestry. The time we save shows up in the output of every product team. Nobody is required to use what we build, so adoption has to be earned.

About the role

This is a product role that ships code. You will own one part of the developer experience, usually a specific workflow, tool, or user problem, and carry it from the first conversation through adoption. Within what you own, you are the product manager, designer, and engineer. You talk to users, decide which problem to take on next, choose the shape of the solution, build it, launch it, and find out whether it helped. Your manager, architect, and the team set portfolio priorities and define where your ownership begins and ends. Inside those boundaries, nobody hands you a groomed backlog or a finished mock.

The work mixes zero-to-one product building with applied AI. One project might be a CLI that makes a painful release workflow easy to follow. Another might be an agent that triages and drafts work during software delivery, with the evaluation and review points that make it safe to depend on. The right answer might be a small automation, a polished product surface, an agent, or no new tool at all. Deciding which, then shipping the smallest useful version, is your call.

We want someone opinionated about craft in internal tools, specifically. Internal software is usually held to a lower standard than customer-facing work. It should embarrass us when a tool we ship is slower, uglier, or more confusing than the consumer products our colleagues build for customers.

What you’ll do

• Own a specific developer workflow, tool, or user problem through discovery, definition, design, build, rollout, and adoption, including the decision to keep it, change it, or retire it. When that decision reaches workflows you do not own, bring the team in.
• Run your own product discovery. Interview engineers, product managers, and designers, watch them work, and read the support tickets, usage data, and CI logs to find the problem most worth solving.
• Turn what you learn into a plan: frame the problem, define who it is for and what changes for them, decide what you are not building, and sequence the smallest useful releases. Larger bets, and work that would expand what you own, go through team planning.
• Design the experience before writing production code, including flows, states, empt…