The Broad Institute Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 17 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at The Broad Institute.
The Broad Institute
Software Engineer
Entry Difficult Neutral experience No offer 5 rounds
Interview process
Recruiter call Phone screen Take home Panel Group
Interview formats
Technical Coding Behavioral
The process started with two screening rounds, followed by a take home project that had a flexible deadline of 1-2 weeks. After that, there was a panel interview and then a fit round. I thought the whole process was a bit too long for the salary they were offering, so I decided not to move forward after the first two screenings.
Confirmed questions1 question
- What makes you want to join Broad Institute?
The Broad Institute
Software Engineer
Mid Average Positive experience Decline offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral
Had a video call with my potential direct manager. It was a 45-minute chat covering lots of ground. They asked a bunch of probing questions digging into a really broad set of my knowledge and experience. This included general stuff like how I handle data structures and algorithm complexity, plus my experience with various programming languages. It also went into more specific areas like Markov Chains, Monte-Carlo methods, deep learning architectures, and processing sequencing data.
Confirmed questions6 questions
- Tell me about your related experience.
- How would you describe your knowledge of algorithms?
- What's your understanding of probabilistic algorithms?
The Broad Institute
Software Engineer
Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Technical screen Panel
Interview formats
Technical Behavioral Technical
The interview experience was really good, and everyone was super nice and made me feel comfortable. They were very clear about the interview process and what to expect at each step. I got feedback fast. First, there was an intro call. Then, I had to do a technical assessment as a take-home task. It was a pretty good one, not too much work but a solid way to check skills. After that, I had a 3-part interview: a casual chat about behavior and culture, a review of my take-home assessment solution, and then a more general technical discussion.
Confirmed questions2 questions
- What were your reasons for the implementation decisions you made in the technical assessment?
- Could you elaborate on the specific choices you made during the technical assessment's implementation?
The Broad Institute Software Engineer Interview Questions
Quoted word for word from The Broad Institute interview reports.
“Can you write a function to determine the best 5-card poker hand from a given set of n cards?”
Read reports →“Could you write a program in any programming language that takes a JSON input of poker hands and identifies the winning hand?”
Read reports →“What's your understanding of probabilistic algorithms?”
Read reports →“Were you using JavaScript, or were your websites mostly static?”
Read reports →“What specifically about the Broad and this team appeals to you?”
Read report →“What would you do to add this new feature?”
Read report →“What makes you want to join Broad Institute?”
Read report →“What makes you want to apply to the Broad?”
Read report →“Can you explain the reasoning behind your code's design and structure?”
Read report →Formats, difficulty and experience
Across all 17 The Broad Institute interview reports.