GreatSchools logo

GreatSchools Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
9.1% Positive experience

Which role are you interviewing for?

7 roles · 12 reports

Candidate interview experiences

First-hand accounts from people who interviewed at GreatSchools.

Showing 4 of 12
GreatSchools logo
GreatSchools

Data Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 1 round
Interview process
Take home
Interview formats
Other

It took more than a month to even get in touch with them. Once I did, I was given a take-home coding assignment. It's now been a full month since I submitted that test. I sent a follow-up email after a week and heard nothing back. Reaching out via LinkedIn message after two weeks also got no response. I even commented on one of their posts after three weeks and still nothing. It's been exactly four weeks now with zero communication. They didn't even have the courtesy to send a simple 'no thank you' via email, message, or text. Honestly, I'd steer clear of this company.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

GreatSchools logo
GreatSchools

Human Resources Business Partner

HR · more than a year ago

Mid Average Positive experience Decline offer 3 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral

Process with recruiter, operations director, and people director. Very organized process, and people were super welcoming during the interview. It was great to be part of the process. It was also fast, with lots of information given throughout.

Confirmed questions1 question
  • How do you handle an environment that's always changing and has many processes yet to be designed?
GreatSchools logo
GreatSchools

Software Engineer

Engineering

Entry Difficult Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Onsite
Interview formats
Technical Coding Behavioral

It started with a phone screen where I was asked some Ruby questions, which I think went well, and then I got an easy codingame.com challenge that I completed. About a week later, I had a 3-hour onsite interview. Early on, there were some concerning signs about work-life balance and enthusiasm for the role, plus they mentioned high turnover, especially for junior folks leaving after a year. The team interview was tough because their tech stack is ROR with React, and I don't have extensive experience with either. This was my first onsite technical interview, and I was pretty nervous, which led to me blanking on or not understanding some questions. While I take responsibility for not performing well due to my inexperience, it was known from the start that I was new to this. I was surprised to even reach the onsite, given the job posting asked for a year of React/ROR experience. The team was nice, though, and tried to make me feel comfortable despite my lack of framework/language experience. Towards the end, things got awkward when they commented on my age and gender. When the main interviewer returned, they said the interview wasn't going well and that we were done, mentioning they'd interviewed more qualified candidates the previous week. I knew I wasn't the best fit, but ending it that way felt unprofessional. I asked for feedback on the coding challenge and onsite since I invested about 3 hours in total, but I haven't heard back. They also didn't discuss the coding challenge at all during the interview.

Confirmed questions3 questions
  • Can you interpret this Ruby code that's querying an API?
  • Identify the React components on the Greatschools.org website.
  • What occurs after an HTTP response has been sent?
GreatSchools logo
GreatSchools

QA Engineer

Engineering

Entry Easy No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Technical Coding Behavioral

I applied online and then the hiring manager reached out after a few weeks to set up a phone interview. A few days after that, I got an email for an onsite interview. It was with four people, and I had about half an hour with each. The interviews themselves were pretty easy and everyone was really nice. The downside was that the hiring manager never got back to me with any results, even after I followed up, which was kind of unprofessional.

Confirmed questions3 questions
  • Can you define different types of testing?
  • Please write test cases for the provided web page.
  • Can you write some SQL queries?

GreatSchools Interview Questions

Quoted word for word from GreatSchools interview reports.

What's the difference between Lambda and Proc in Ruby, and what about closures in JavaScript?

Read reports

Can you explain what happens when a request is made to a website built with Rails?

Read report

Can you explain the distinctions between left/right joins and inner/outer joins in SQL?

Read report

Could you analyze the ReactJs code and suggest improvements?

Read report

Did you build a page on Ruby on Rails, including routes, reading from the database, making migrations, generating a model, and creating a view?

Read report

Formats, difficulty and experience

Across all 12 GreatSchools interview reports.

Interview formats

Coding 32.3%
Technical 25.8%
Behavioral 22.6%
Other 6.5%
Presentation 6.5%

Interview difficulty

Easy 16.7%
Average 66.7%
Difficult 16.7%

Candidate experience

Negative 54.5%
Positive 9.1%
Neutral 36.4%

Reports by job function

Engineering 10
HR 1
Analytics 1