← Back to Directory

Ancestry

Large Enterprises

,providing summary DNA-key testings for and family Ancestry history is research. Wait - the largest fix genealogy JSON.

7 interview notes · updated Jul 2026

Ancestry·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Ancestry ML/systems design round where they threw a pretty involved personalization scenario at me. The whole thing revolved around building a feedback ingestion and embedding pipeline for a consumer product, and it went in a lot of directions fast.
  • How would you design a system to ingest and store millions of free-text user feedback records so they can be queried and used for downstream modeling?
  • How would you define embeddings or other feature representations from user feedback text to find similar users or similar products?
  • How would your system automatically update its categorization or tagging of feedback as new types of issues or topics emerge over time?
  • How would you evaluate whether the personalization pipeline is actually working well?

“I started with a streaming ingestion layer and a document store, which felt right, but I got fuzzy when they pushed on schema design and how you'd handle querying at scale without blowing up costs.”

View Post

Ancestry·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Ancestry for a software engineering role. The whole thing centered on one big open-ended problem about item categorization, and they wanted you to go pretty deep on a lot of different angles rather than just sketch out a basic pipeline.
  • Design a system that automatically updates item categories as new items and signals come in. Walk through how you'd handle taxonomy management, classification approaches, detecting drift, human review loops, experimentation, and rollout.

“This question is basically six questions duct-taped together.”

View Post

Ancestry·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Ancestry system design round for a software engineer role. The main focus was on feature engineering for similarity, which sounds straightforward until you're actually in it trying to remember every encoding option you've ever read about.
  • How would you define features to find similar users or similar products? Walk through your feature choices, how you'd encode them, and how you'd measure whether your similarity approach actually works.

“This one sprawled in a way I didn't expect.”

View Post

Ancestry·Software Engineer·Technical Phone Screen

Jun 2026
Ancestry put me through a machine learning fundamentals quiz for a software engineering role. Three questions, all conceptual, no coding. Felt more like a grad school oral exam than a typical SWE screen.
  • Can you define supervised, unsupervised, and self-supervised learning and give a concrete example of each?
  • What is a loss function, and how do you decide which one to use for a particular task?
  • What is an embedding, how does a model learn one, and where would you actually use embeddings in a real application?

“I had supervised and unsupervised down cold but self-supervised tripped me up a little.”

View Post

Ancestry·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Ancestry focused entirely on building a data store around user feedback text. Pretty open-ended and went deep fast, covering everything from raw ingestion to embedding pipelines to query scaling.
  • Design a database or data store that is powered by user feedback text. Walk through how you'd handle ingestion of free-form feedback, schema design, a parsing and embedding pipeline, query patterns like search and aggregation, and how you'd scale the whole thing.

“This felt like four questions stitched into one.”

View Post

Ancestry·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at Ancestry and the main focus was a deep dive into my research background. Pretty much the whole session was me walking through past projects one by one, which I wasn't fully prepared for.
  • Walk me through your resume, focusing on your research experiences. For each project, describe what it was about, what you personally contributed, the methods you used, the results, and what you'd change if you did it again.

“This sounds simple but it absolutely is not when you have multiple projects and they want the full breakdown for each one.”

View Post

Ancestry·Software Engineer·Technical Phone Screen

Apr 2026
Ancestry ML fundamentals screen for a software engineer role, all conceptual stuff delivered verbally. No coding, just definitions and examples. Felt more like a college exam than a real interview.
  • What is supervised learning, and what kinds of inputs, labels, and tasks does it typically involve?
  • What is unsupervised learning and what kinds of problems does it address?
  • What is self-supervised learning, and how does it differ from supervised and unsupervised approaches?
  • What is a loss function, why do we need one, and what are some common examples?
  • What is an embedding? How is it learned, what does it represent, and how is it used during inference?
  • Can you give several real-world use cases for embeddings, particularly in personalization or search?

“Pretty standard opener.”

View Post