Scale logo

Scale Software Engineer Interview Questions
& Process

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

Based on 68 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
35.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Scale.

Showing 3 of 68
Scale logo
Scale

Software Engineer

Engineering · half a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

So I got contacted on LinkedIn by a recruiter, and we had an initial chat about my background and if I'd be a good fit. Then I did a technical phone screen with a senior engineer. After that, I met with the hiring manager to talk about my past work/projects and answer some behavioral questions. The final loop was a mix of mostly technical stuff and some behavioral questions.

Confirmed questions2 questions
  • Can you discuss your previous work and projects?
  • Do you have any behavioral questions to ask?
Scale logo
Scale

Software Engineer

Engineering · half a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding Technical

Recruiting call followed by an online assessment. The assessment involves building a task scheduler. First, create a basic scheduling service to return the next best task. Then, add task dependencies. Finally, consider scaling and edge cases. You should also brush up on data structures, specifically how to find the highest priority item, how to map relationships, and practice incremental development.

Confirmed questions1 question
  • Why do you want to work at scale?
Scale logo
Scale

Software Engineer

Engineering · nearly a year ago

Mid Difficult Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen
Interview formats
Coding Behavioral Technical

It was many rounds of implementation heavy coding, honestly got tiring and boring. Plus behavioral and debugging round, which was excruciating. The work they were talking about sounded extremely boring and maybe unethical. Some interviewers were good but some just turned their camera off and were silent the whole for the coding round. I would not work here if I received the offer.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Scale Software Engineer Interview Questions

Quoted word for word from Scale interview reports.

Given a graph, remove a node chosen uniformly at random and verify if it was subsequently reinserted.

Read reports

Implement a card game given some python class and criteria.

Read reports

Can you write a program to output the characters of a given word sorted by frequency? For example, 'tree' should become 'eert'.

Read reports

Could you implement a task scheduler and also print out the task scheduling and running logs for it?

Read report

Can you solve this technical question about a card game?

Read report

For a graph problem where you're given a list of lists, each representing a question with a boolean at index 0 (answered status) and a list of indices at index 1 (dependencies), how would you determine which questions to render? A question should be rendered if it's answered and all its dependencies are also rendered. What's the approach for handling situations where dependent questions might not appear in the correct order?

Read report

Formats, difficulty and experience

Across all 68 Scale interview reports.

Interview formats

Coding 39%
Technical 29.8%
Behavioral 22%
System Design 7.8%
Other 1.4%

Interview difficulty

Easy 10.3%
Average 58.8%
Difficult 30.9%

Candidate experience

Positive 35.3%
Neutral 38.2%
Negative 26.5%