A video call with the recruiter, then a technical interview with the hiring manager. I did not make it beyond that point. Two days later I got an email from the recruiter saying that they want to move forward with other candidates.
One thing that bothered me a little is that both interviews were done over video. I am not too opinionated about such things, but I think it creates unconscious bias.
The interview with the hiring manager was unusually long for the stage. I talked to him for over an hour and a half. I was given a shared document online to write code and such.
I listed Python and c as skills in my resume so the first two questions were related to that. First one was a simple data structure manipulation in Python. Second one was harder - I was asked to write a c macro manipulating some pointers. C macros were never really my strong suit, but I came up with a solution after some effort and hints.
The final problem was a design challenge around concurrency. I had to design a cache. But fetching from origin takes some time, and the most important requirement was to not issue two concurrent fetches for the same resource.
The following metrics were computed from 6 interview experiences for the Fastly Software Engineer role in United States.
Fastly's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Fastly's Software Engineer interview process in United States.