GRAIL logo

GRAIL Software Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
26.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GRAIL.

Showing 3 of 15
GRAIL logo
GRAIL

Software Engineer

Engineering · a year ago

Intern Easy Negative experience No offer 1 round
Interview process
Recruiter call Offer
Interview formats
Behavioral

A recruiter contacted me for an interview. It was shorter than typical, around 5 minutes, and didn't even include basic behavioral questions. She suggested connecting on LinkedIn, which we did. I got a rejection email a few days later.

Confirmed questions1 question
  • Tell me about yourself
GRAIL logo
GRAIL

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home Background check
Interview formats
Technical Coding Other

The interview process started with two 30-minute interviews. After that, I was sent a take-home project that was due by the end of Sunday, which ruined my weekend. I submitted the project and was ghosted afterwards, which felt like a waste of 5 hours. I had to chase for feedback, and when I got it, it contradicted the brief. They asked for things that the brief said to assume. I would not recommend this company, it feels like a waste of time.

Confirmed questions1 question
  • Build a microservice API for managing patient details (create, update, delete).
GRAIL logo
GRAIL

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience No offer 6 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Panel Group Presentation Background check Offer
Interview formats
Behavioral Technical Coding System Design Case Presentation Group Other

I applied through a recruiter and the interview process involved a few steps. First, there was an intro call with talent acquisition, then another intro call with a technical director from the UK. After that, I had a take-home assignment where I had to build an API. The next part was a series of Zoom panel interviews that could be spread over one or two days. This included a 45-minute coding test on codeinterview.io where I had to model a Lightbulb and Lightswitch. Then there was a 45-minute call with the tech director from the UK to discuss my assignment, CV, and some Amazon behavior questions. Following that, I had a 45-minute call with the tech director from the USA to go over my CV and more Amazon behavior questions. Finally, there was a 15-minute call with talent acquisition. It was a bit longer than usual, but everyone was nice and knew their stuff. My advice: be ready to write code without an IDE, have specific examples for the Amazon behavior questions (they expect STAR method answers), and make sure you're actively participating in conversations.

Confirmed questions3 questions
  • Could you share an instance where you introduced a bug, and describe your approach to identifying and rectifying it?
  • Tell me about a bug you created, explaining how you discovered it and the steps you took to fix it.
  • Can you provide an example of a bug you introduced, detailing how you found it and subsequently fixed it?

GRAIL Software Engineer Interview Questions

Quoted word for word from GRAIL interview reports.

Can you generate a lexical ordering from a given ordered list of words?

Read reports

Build a microservice API for managing patient details (create, update, delete).

Read reports

Can you provide an example of a bug you introduced, detailing how you found it and subsequently fixed it?

Read report

Tell me about a bug you created, explaining how you discovered it and the steps you took to fix it.

Read report

Can you tell me about a situation where you had to work with someone you didn't get along with?

Read report

Could you share an instance where you introduced a bug, and describe your approach to identifying and rectifying it?

Read report

Formats, difficulty and experience

Across all 15 GRAIL interview reports.

Interview formats

Behavioral 31.6%
Technical 28.9%
Coding 21.1%
System Design 5.3%
Other 5.3%

Interview difficulty

Easy 26.7%
Average 66.7%
Difficult 6.7%

Candidate experience

Negative 60%
Positive 26.7%
Neutral 13.3%