FamilySearch.org Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at FamilySearch.org.
FamilySearch.org
Software Engineer
Mid Easy Positive experience No offer 1 round
Interview process
Phone screen
Interview formats
Technical Behavioral
The interview process was great. I first did a phone evaluation, but unfortunately, I didn't make it through because I wasn't as prepared as I should have been. They asked about my background and experience. The interviewer was the manager of the team, so I learned about the portfolio and projects during the call.
Confirmed questions1 question
- Can you explain the various React hooks and provide examples of their usage?
FamilySearch.org
Software Engineer
Entry Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Coding
The interview process was pretty good. There were 3 rounds. It involved some technical questions and a live coding challenge. The interviewers were super nice and encouraging. If it's a front-end role, I'd suggest brushing up on React, basic JS, HTML, and CSS.
Confirmed questions2 questions
- Can you explain what a React hook is and how to create a custom one?
- What are the advantages of using components?
FamilySearch.org
Software Developer
Entry Average Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral
It started with two phone interviews, and then an all-day in-person interview. It was a really frustrating process because they seemed unprepared. I was put in a small, hot room for most of it, wearing a suit in 90-degree heat. I spoke with about five different people. I thought I did well on the coding problems, but I wasn't great with the terminology, which was disappointing. One interviewer took a personal call mid-interview, which made me question the job. They said they'd respond by a certain date but didn't. After I emailed them, they just said I didn't get the offer. I suspect someone's family member might have been competing for the role, and they were just interviewing others for show. I took time off work for this, losing PTO. They mentioned there might have been another interview if I'd moved forward. My first phone interview started 30 minutes late, and they told me I needed to be near a computer even though they initially said it wasn't necessary.
Confirmed questions1 question
- The questions focused more on terminology than on actual skills.
FamilySearch.org Software Engineer Interview Questions
Quoted word for word from FamilySearch.org interview reports.
“What is an HTTP request?”
Read reports →“Could you create a Java class for a deck of cards?”
Read reports →“Could you write a method that determines if a given number is prime?”
Read reports →“Explain polymorphism.”
Read reports →“Can you explain what a React hook is and how to create a custom one?”
Read report →“Could you write the code for the Fizz-Buzz problem?”
Read report →“What are the advantages of using components?”
Read report →“Can you design a program to shuffle a deck of cards?”
Read report →“Tell me about polymorphism in Object Oriented programming.”
Read report →Formats, difficulty and experience
Across all 8 FamilySearch.org interview reports.