Senior Software Engineer applicants have rated the interview process at Fastly with 2.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 38% positive. To compare, the company-average is 45.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 21 days to get hired, when considering 8 user submitted interviews for this role. To compare, the hiring process at Fastly overall takes an average of 29 days.
Common stages of the interview process at Fastly as a Senior Software Engineer according to 8 Glassdoor interviews include:
Phone interview: 29%
One on one interview: 24%
Group panel interview: 10%
Personality test: 10%
Drug test: 10%
Skills test: 10%
Presentation: 5%
Background check: 5%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Fastly in Dec 2021
Interview
I received an email from a recruiter requesting for my availability with a link to book a slot
My link was expired. I replied the recruiter requesting for another link.
He never got back. I sent a follow up a week later with no reply
I applied through an employee referral. The process took 3 weeks. I interviewed at Fastly (New York, NY) in Aug 2024
Interview
A really great cross-functional process that focused on the day-to-day rather than comp-sci trivia. I had a coding screen appropriate to my level, conversations with product, and various "tell me about a time" questions.
Interview questions [1]
Question 1
This component is incomplete. This is what we'd like it to do. How would you do that?
I applied online. The process took 3 weeks. I interviewed at Fastly (Denver, CO)
Interview
Interview process involves a recruiter screen for thirty minutes. This is then followed by a hiring manager interview for an hour. Then I heard back from the recruiter about two weeks after the interviews took place. Disrespectful recruiter.
Fairly easy interviews. Easy coding question to implement data structure and then a few conversations about my career. A few systems design questions and inquiring how I would handle different engineering scenarios.