Fathom logo

Fathom Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 42 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
28.6% Positive experience

Which role are you interviewing for?

7 roles · 42 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Fathom.

Showing 4 of 42
Fathom logo
Fathom

Machine Learning Engineer

Engineering · nearly a year ago

Mid Average Positive experience Decline offer 1 round
Interview process
Technical screen
Interview formats
Technical Presentation

The interview involved explaining a machine learning problem I solved in the past. I had to detail my approach to data preprocessing, model training, and how I used domain knowledge. It also required showing how communication played a role and what the overall problem-solving process looked like.

Confirmed questions1 question
  • Are you open to relocating?
Fathom logo
Fathom

Senior Software Engineer

Engineering · more than a year ago

Senior Average Neutral experience No offer 5 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Coding System Design Coding

The interview process was generally good, with interviewers who were professional and assessed me fairly. I got feedback based on their notes, which was great. But I have two things to mention about the interviews: 1. The screening round used GitHub Codespaces, which I found a bit confusing. It seemed like I'd have to work through a whole codebase, but I only had to read and finish a few functions in one file, making GitHub Codespaces not really needed. 2. One of the coding rounds had me implement a classic algorithm iteratively. I don't think that's a good interview question because it has a lot of edge cases to debug in 45 minutes, and it doesn't really show how a candidate thinks. It felt like a lot of work, but not very insightful.

Confirmed questions3 questions
  • A screening round that involved coding in a GitHub Codespace.
  • Two rounds focused on system design.
  • Two rounds involving coding challenges using HackerRank's editor.
Fathom logo
Fathom

Technical Recruiter

HR · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Presentation
Interview formats
Behavioral Presentation Other

So I was in my third round, which was a 2-hour interview with a role play, a live writing test, and a presentation. I really prepped hard for this. They said I did great, but then they just ghosted me. They gave me a timeline for a decision, but I never heard back. No feedback, no decision, nothing. It's a really awful and insulting experience, especially when people take their personal time to prepare so intensely.

Confirmed questions3 questions
  • Can you tell me about the recruitment metrics you've utilized?
  • What makes you interested in Fathom Health specifically?
  • In your opinion, what are the essential traits and skills for a recruiter?
Fathom logo
Fathom

Machine Learning Engineer

Engineering

Mid Average Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen
Interview formats
Coding

even though the job description was for ML, I went through three rounds of pure coding leet code style questions. based on my interview experience and conversations I had with people, if one wants to grow their ML skills and make a resume in ML, this is not the place. you would wind up doing a lot of debugging and software development stuff. you may get the chance to train a model now and then, but don't count on it. in general I enjoyed the questions, but I was disappointed of the interview process and how people behaved. I mean no one even took a minute to introduce themselves to me or ask me who I am and what I do. I felt a lot of pressure doing the live coding. Also, the work life balance sucks at this company and I could even feel it based on their interview process!

Confirmed questions1 question
  • They like graph and string questions

Fathom Interview Questions

Quoted word for word from Fathom interview reports.

How would you design a restaurant recommendation system that leverages user location?

Read report

How would you determine the on-call hours for each user?

Read report

Formats, difficulty and experience

Across all 42 Fathom interview reports.

Interview formats

Coding 31.9%
Behavioral 22.7%
Technical 19.3%
Presentation 15.1%
System Design 9.2%

Interview difficulty

Easy 16.7%
Average 61.9%
Difficult 21.4%

Candidate experience

Positive 28.6%
Negative 54.8%
Neutral 16.7%

Reports by job function

Engineering 37
HR 2
Marketing 1
Finance 1
Product 1