Software Engineer applicants have rated the interview process at Scale with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 26% positive. To compare, the company-average is 37.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 21 days to get hired, when considering 42 user submitted interviews for this role. To compare, the hiring process at Scale overall takes an average of 23 days.
Common stages of the interview process at Scale as a Software Engineer according to 42 Glassdoor interviews include:
Phone interview: 40%
One on one interview: 23%
Skills test: 18%
Personality test: 10%
Group panel interview: 8%
Other: 3%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1 week. I interviewed at Scale in Dec 2022
Interview
Recruiter reached out to me via email. Met with a team and then scheduled a technical round using Coderpad or something of the like. Received one of the worst questions I think a company has ever given me, and my interviewer was a brick wall. I have no idea what engineering skills this question is supposed to measure. You are explicitly wrong if you write an answer that “scales” better so you better write inefficient code or you’ll fail
Interview questions [1]
Question 1
There are 3 parts Part 1. Write a task scheduler. Start be defining a ‘Task’ class and a ‘Thread’ class. Define a function that will take in some list of Tasks and some list of Threads and assign every task to a thread. The function will print out every ‘step’ of the function. Example: for tasks=[A,B,C], numThreads=2 “Step 1 Task A assigned to Thread 1 Task B assigned to Thread 2 Step 2 Task C assigned to Thread 1 Part 2. Here is where things get dumb. Now each Task is composed of some subtasks that must all be completed before the Task is finished. Each Thread can only work one certain subtasks as well. Output the NON-OPTIMAL solution. I repeat, non-optimal - if you optimize by making sure every thread is occupied when a task could be operated on by that thread then you are wrong. They will give you a specific output that they want, and you must generate that output in that order. They basically want you to create a specific non-optimal solution. Makes no sense what signal this is trying to measure for new-hires but whatever ¯\_(ツ)_/¯ Example: TaskA: subtasks: [“square”, “circle”] TaskB:subtasks: [“star”] Thread1: [“square”] Thread2: [“ circle”, “star”] Output: “ step1 Task A assigned to Thread 1 Step2 Task A assigned to Thread2 Step3 Task B assigned to Thread2 “ The example is a little more complex but that’s the basic idea Part 3. Didn’t get to it. Part 2 was too dumb and I spent too much time optimizing after telling the interviewer how I was going to optimize. After I was almost done he was like “You must print out the exact same output as the example output”
Pretty in line with what others are saying. Heavy coding rounds, questions about past work experiences, and standard behavioral questions. Interviewers did not seem very engaged. Interviews sometimes felt long.
I applied online. I interviewed at Scale (San Francisco, CA) in Mar 2026
Interview
After an initial online assessment, I had a 60 minute live coding interview. The main problem focused on designing and implementing a task prioritization system, where tasks had to be managed based on priority and constraints. The interview was practical and implementation focused rather than purely algorithmic. This was not the superday, just the OA followed by the live coding round.
I applied online. I interviewed at Scale in Feb 2026
Interview
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.