The wild part was that they basically put me through the same bar as software engineering, then only later figured out whether I fit FDE.
Interview process
I got in through a referral, and when I went through it the process was long and very SWE-coded. I started with a hard OA, then had a recruiter screen, a non-technical phone screen, and a coding phone screen. After that I did a five-part onsite with credo, coding, system design, debugging a giant repo, and a hiring manager round. I got the offer, and the biggest thing that stood out was that they really seemed to use the same hiring bar for FDE and software engineering, then sort out role fit later.
- Online assessment
- Recruiter screen
- Phone interview
- Technical interview
- Final round
Interview rounds
5 roundsOnline assessment
Overview
I started with an OA that was basically one coding problem, and it felt like a hard LeetCode-style question. Right away it gave me the sense that they were using the same initial bar they use for software engineers.
Question types asked
Recruiter screen
Overview
After I passed the OA, I had a recruiter screen to move me into the rest of the process. It did not feel like they were deeply separating FDE from SWE at that point.
Question types asked
Phone interview
Overview
I had a non-technical phone screen next. My sense was they mostly wanted to see whether I had actually built something end to end, not whether I already sounded like a polished client-facing FDE.
Question types asked
Technical interview
Overview
Then I had a coding phone screen. It still felt very SWE-like, which matched the broader process.
Question types asked
Final round
Overview
The onsite was five separate rounds and felt pretty holistic. I had a credo round, which was basically their version of leadership principles, a coding round, a system design round, a debugging round where they dropped me into a giant repo and asked deep questions, and then a hiring manager round. From my perspective, this was the point where role fit started to matter more.
Question types asked
Interview tips
I would prep this like a real software engineering loop, not like a lighter solutions or sales-engineering process. Be ready for hard coding, system design, and especially debugging in a big unfamiliar codebase, because that round can catch people off guard. I would also have strong stories about projects I built end to end, since that seemed to matter early. And I would not assume they already know where to place you, because FDE versus SWE fit can get decided later in the process.
Company culture
The screens seemed to care a lot about whether you had actually built things end to end, and thus ownership is highly valued. Also, the org seems to be moving toward blending forward deploy and applied AI work, so the direction of the role is getting broader around agents.
Get full access with a membership, or share your experience to try it free.
More Scale AI interview experiences

“What stood out most was the interviewer straight up told me the culture at Scale is “pretty like 996,” which you usually never hear that openly. And the rounds were super speed focused, like two interval-style problems in one hour.”

“Efficient interview process. Recruiter, then hiring manager, then interview loop. Interview loop consists of 4 interviws.”