Fathom Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 27 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Fathom.
Fathom
Software Engineer
Entry Average Positive experience No offer 3 rounds
Interview process
Technical screen Recruiter call Technical screen
Interview formats
Coding Behavioral Technical
I did a HackerRank code screening, then a 30 min behavioral chat with the recruiter, and then a technical interview with an engineer. There were more parts after that, but I didn't get that far.
Confirmed questions3 questions
- Could you help us develop some functions for an on-call scheduler example?
- How would you determine the on-call hours for each user?
- How would you create a schedule for users with the fewest on-call hours?
Fathom
Senior Software Engineer
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
Software Engineer
Mid Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Coding
Got reached out by upper management on LinkedIn, then sent to HR. Had a quick chat (15 mins) with HR, who asked a mix of questions, some not relevant or already answered. Then got a link for an online test. Waited a few days for feedback (which wasn't detailed). HR said it went well, asked more bureaucratic questions, and promised an update by the end of the week. It's been 3 weeks with no word. They kept mentioning they were shortlisting, which seems to mean they cut contact whenever they want. Typical firm with a lot of investment money, acting like big shots now. Don't waste your time.
Confirmed questions3 questions
- How did you find out about us?
- What are your long-term career goals?
- Complete 3 medium-difficulty tasks on Hackerrank.
Fathom Software Engineer Interview Questions
Quoted word for word from Fathom interview reports.
“Solve 'Substring with concatenation of all words'”
Read reports →“Solve 'Check if the rectangle corner is reachable'”
Read reports →“Solve a problem related to finding anagrams.”
Read reports →“Design a dam using dynamic programming principles.”
Read reports →“Write code to make API calls and sort the responses.”
Read report →“How would you determine the on-call hours for each user?”
Read report →“How would you parse a JSON response from an API and then perform an operation on a specific field within that data?”
Read report →“How would you create a schedule for users with the fewest on-call hours?”
Read report →“Solve a LeetCode problem that's medium to hard difficulty.”
Read report →Formats, difficulty and experience
Across all 27 Fathom interview reports.