← Back to Directory

Ancestry

Large Enterprises

Screna has 5 Ancestry interview write-ups. The most reported round is the system design round (3).

5 interview notes · updated Jun 2026

Ancestry·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Ancestry for a software engineer role. The whole thing was one big open-ended question about building a database or data store on top of user feedback text, covering everything from ingestion to scaling. Pretty broad scope for a single session.
  • Design a data store powered by free-form user feedback text. Walk through ingestion, schema design, a processing pipeline for parsing and embedding, query patterns like search and aggregation, and how you'd scale the whole thing.

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

View Post

Ancestry·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Ancestry for a software engineering role. The whole thing centered on one big open-ended problem around item categorization, which sounds manageable until you realize how many moving parts they actually want you to cover.
  • Design a system that automatically updates item categories as new items and signals come in. Walk through how you'd handle taxonomy maintenance, classification approaches, drift detection, human review, experimentation, and rollout.

“This was a lot to fit into one question.”

View Post

Ancestry·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a software engineer role at Ancestry and the main focus was walking through my resume with an emphasis on research experiences. Pretty standard format but it went deeper than I expected on the specifics.
  • Walk me through your resume, focusing on your research experiences. For each project, what did you contribute specifically, what methods did you use, what were the results, and what would you change if you did it again?

“This is deceptively hard to answer well under pressure.”

View Post

Ancestry·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Ancestry ML-adjacent system design round, single question but it sprawled into a lot of territory fast. The feature engineering angle was expected but the depth they wanted on encoding choices and evaluation caught me a bit off guard.
  • How would you define features for finding similar users or similar products? Walk through the feature families you'd consider, how you'd encode them, and how you'd evaluate whether your similarity approach actually works.

“I started with behavioral features because that felt safest for a genealogy product (search history, tree edits, record views) and then worked outward to demographic and content signals.”

View Post

Ancestry·Software Engineer·Technical Phone Screen

Apr 2026
Ancestry had me do what felt like a quick ML fundamentals check, three questions back to back with no warmup. Pretty conceptual stuff but I fumbled parts of it more than I expected for a software engineer role.
  • Can you define supervised, unsupervised, and self-supervised learning and give an 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 what are some real-world scenarios where embeddings are useful?

“Supervised and unsupervised I had no problem with.”

View Post