Pearson logo

Pearson Software Engineer Interview Questions
& Process

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

Based on 101 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
59% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Pearson.

Showing 3 of 101
Pearson logo
Pearson

Software Engineer Intern

Engineering · nearly a year ago

Intern Easy Positive experience Accept offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

It was a really chill interview, no technical questions at all. They mostly focused on my resume and projects, digging into them quite a bit. They asked about my favorite project, how I built it, and what tech stack was used.

Confirmed questions3 questions
  • Could you tell me about your favorite project and the reasons behind it?
  • What was the entire process like when you were building your favorite project?
  • Regarding your favorite project, what aspects of the tech stack were utilized?
Pearson logo
Pearson

Software Engineer

Engineering · nearly a year ago

Mid Average Negative experience Decline offer 1 round
Interview process
Onsite
Interview formats
Technical Coding System Design

I had a physical interview at the company. It was friendly, but the interviewer wasn't really on point. The person interviewing me was young, and all the questions focused on quality assurance and testing. They gave me a lot of scenarios to design use cases and asked about unit testing, integration testing, system testing, and acceptance testing.

Confirmed questions3 questions
  • Tell me about OOP and dependency injection.
  • What are your thoughts on quality assurance?
  • Can you design use cases?
Pearson logo
Pearson

Senior Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call Technical screen Panel
Interview formats
Behavioral Technical

A recruiter reached out to me for the role and we set up an interview. I thought it was strange that there was no hackerrank or coding assessment for a software engineering job, but I agreed to interview anyway. I asked the interviewer about the question style beforehand and got vague answers, finally being told it was a single round with scenario-based questions. That wasn't accurate. During the interview, I didn't get to write code, discuss system design, frameworks, or tooling. Instead, I was asked a few behavioral questions. It's odd, given my background (1300 LeetCode problems solved, 3700 GitHub contributions, a solution channel, and an MS in CS with a 4.0 GPA), that I wasn't given a chance to show my skills. I wasn't even advanced, which feels unfair and lacking empathy. When I asked for feedback, I was told I lacked passion for AI (which wasn't in the job description, my resume, or mentioned by the recruiter) and that it would be a one-round interview, contradicting what the interviewer said about selecting candidates near the end. It's unfair to reject someone with my coding skills without a coding interview, and I'd suggest a more scientific approach.

Confirmed questions2 questions
  • Tell me about your hobbies and any side projects you have.
  • What hobbies and side projects are you working on?

Pearson Software Engineer Interview Questions

Quoted word for word from Pearson interview reports.

What is the distinction between PUT and POST methods in REST APIs?

Read reports

How would you print a binary search tree in reverse order without using extra space?

Read reports

How would you find the 3rd largest number in an array if you couldn't sort it?

Read reports

How would you reverse a number, for instance, transforming 12345 into 54321?

Read reports

In what ways do Java and C# facilitate the implementation of multiple inheritance?

Read report

How many test cases could you create for a sign-on screen with fields for username, password, and a submit button?

Read report

Can you explain the fundamental concepts of object-oriented programming and briefly elaborate on each?

Read report

Can you explain the components of an n-tier architecture for a given problem, detailing what would reside in each tier?

Read report

Can you explain Level order traversal on a whiteboard with an example?

Read report

Formats, difficulty and experience

Across all 101 Pearson interview reports.

Interview formats

Technical 38.5%
Behavioral 35.8%
Coding 16.8%
Presentation 2.7%
System Design 2.2%

Interview difficulty

Easy 25.7%
Average 63.4%
Difficult 10.9%

Candidate experience

Positive 59%
Negative 17%
Neutral 24%