Paige logo

Paige Interview Questions
& Process

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

Based on 22 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
72.7% Positive experience

Which role are you interviewing for?

9 roles · 22 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Paige.

Showing 4 of 22
Paige logo
Paige

Engineering Manager

Engineering · more than a year ago

Manager Average Positive experience Decline offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Background check Offer
Interview formats
Behavioral Technical

The interview process was a bit longer than usual because of the holidays, but it wasn't too tough and felt pretty standard for a management role. I really liked that they took the time to make sure it was the right fit for everyone involved, which says a lot about the People and Engineering teams at Paige. Everyone I talked to was professional, open, and engaging. The interviews were usually an hour or less and scheduled conveniently for both sides. Even though I ended up taking another job, I thought this was a really great experience with a company that's doing important work and has a promising future.

Confirmed questions1 question
  • As is common in management interviews, the questions were more like a discussion, focusing on your past experiences, your usual processes, and how you handle problem-solving at an organizational level, rather than asking for specific technical solutions.
Paige logo
Paige

Platform Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical System Design Behavioral

The interview process included five 1-hour Zoom calls: one with the Director, one with a Lead Engineer, two with Staff Engineers, and one with a Senior Engineer. These calls focused on deep dives into past architectural decisions and implementation details of technologies like Kubernetes. I also had opportunities to learn about the company's operations, goals, and challenges, and everyone was open and friendly, making for a really positive experience.

Confirmed questions2 questions
  • Why did you select this specific Kubernetes network design over alternative options?
  • Regarding the architecture with a cache layer, what are some key implementation considerations?
Paige logo
Paige

Front End Engineer

Engineering

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen
Interview formats
Technical Coding Behavioral

This was a lot of interviews. First, a 30-minute video call with the recruiter. Then, a 1-hour video interview with a UI engineer, covering a high-level technical intro to the product. Next, a 1-hour technical interview with a peer developer that involved a live programming exercise. I had to build a stopwatch with start/pause functionality. I struggled with React for this and didn't finish, despite asking for help which wasn't really given. Surprisingly, I then had another 1-hour video interview with a different engineer, more conversational but still technical. I discussed the stopwatch issue and how I'd do it in vanilla JS. A fifth interview, a 1-hour video call with another engineer, possibly a manager. By then I was out of questions and tired. I was later told by phone that I didn't get the offer.

Confirmed questions1 question
  • Describe how you would create a stopwatch feature that can be started and paused.
Paige logo
Paige

Senior Software Engineer

Engineering

Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Background check Offer
Interview formats
Technical Coding System Design Behavioral

My interview experience was really bad, with no consideration for candidates' time or updates. The interviews were okay but a bit disorganized and repetitive. My recruiter changed midway through, from an external agency to an internal one. There were 4 interviews in total: a technical discussion with a coding challenge, an interview on architecture, ML, and testing, a coding interview, and a discussion on software engineering and cultural fit. After these 4 rounds, I had to wait 11 days for a decision. I tried contacting the company on day 7 but was ignored by the internal recruiter. Then, I got an automated rejection from the initial external recruiter saying the job was closed. The internal recruiter then told me the position was closed due to headcount issues in Europe but he would see if they could get approval and let me know. The next day, a third recruiter emailed to say the position was closed. I never heard back about headcount. It was a terrible experience, showing a clear lack of respect for candidates' time.

Confirmed questions1 question
  • How would you approach testing a class?

Paige Interview Questions

Quoted word for word from Paige interview reports.

How would you go about storing tiled images within an S3 bucket?

Read reports

Regarding the architecture with a cache layer, what are some key implementation considerations?

Read reports

Describe how you would create a stopwatch feature that can be started and paused.

Read reports

Could you construct a basic React Component that continuously updates its state and addresses potential edge cases or complexities?

Read report

Why did you select this specific Kubernetes network design over alternative options?

Read report

Formats, difficulty and experience

Across all 22 Paige interview reports.

Interview formats

Behavioral 33.3%
Technical 31.7%
Coding 20%
System Design 8.3%
Presentation 3.3%

Interview difficulty

Easy 18.2%
Average 68.2%
Difficult 13.6%

Candidate experience

Negative 22.7%
Positive 72.7%
Neutral 4.5%

Reports by job function

Engineering 14
Operations 4
Research 3
Sales 1