Scholastic logo

Scholastic Software Engineer Interview Questions
& Process

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

Based on 11 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
72.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Scholastic.

Showing 3 of 11
Scholastic logo
Scholastic

Software Engineer

Engineering · a year ago

Entry Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen Group Presentation
Interview formats
Coding Presentation Group Technical Behavioral

So the first round was basically talking about my experience, like asking me about coding projects I've done. Then the second round had two parts: a coding interview, and then a presentation with the group. The coding part was kinda tough, they asked me how to make my solution better.

Confirmed questions2 questions
  • Can you describe your past work on coding projects?
  • What suggestions do you have for improving the solution from the coding interview?
Scholastic logo
Scholastic

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Phone screen Technical screen Onsite Technical screen
Interview formats
Technical System Design

The interview process was great. It started with a technical phone screen where we discussed my project experience. After that, I had a Super Day on-site in NYC, which included two technical interviews. They didn't ask me to write code, but we talked a lot about cloud computing, scalable systems, and software engineering design.

Confirmed questions1 question
  • How would you implement a stack using two queues?
Scholastic logo
Scholastic

Software Engineer

Engineering

Intern Average Positive experience Accept offer 3 rounds
Interview process
Phone screen Technical screen Onsite
Interview formats
Technical Behavioral Coding

It was 3 rounds in total. First, a phone interview that was technical. Then, two 50-minute interviews back to back which were technical/behavioral. They mostly asked Leetcode medium problems. The whole process was pretty smooth and quick, taking me about a month from start to finish to get the final decision.

Confirmed questions2 questions
  • How would you find duplicate numbers in an unsorted list?
  • Can you explain the difference between a Map and a Set?

Scholastic Software Engineer Interview Questions

Quoted word for word from Scholastic interview reports.

How can you efficiently find all perfect squares within a given range?

Read reports

Can you explain the purpose of the 'Static' keyword in Java?

Read reports

Can you write a function to find all duplicate elements in a given array?

Read reports

How would you find duplicate numbers in an unsorted list?

Read report

Can you explain the difference between a vector and an arraylist?

Read report

Can you explain the difference between a Map and a Set?

Read report

Formats, difficulty and experience

Across all 11 Scholastic interview reports.

Interview formats

Technical 30.3%
Coding 24.2%
Behavioral 21.2%
Group 9.1%
System Design 9.1%

Interview difficulty

Easy 18.2%
Average 81.8%
Difficult 0%

Candidate experience

Neutral 18.2%
Negative 9.1%
Positive 72.7%