StackPath logo

StackPath Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
40% Positive experience

Which role are you interviewing for?

4 roles · 5 reports

Candidate interview experiences

First-hand accounts from people who interviewed at StackPath.

Showing 4 of 5
StackPath logo
StackPath

QA Automation Engineer

Engineering · more than a year ago

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

Had 3 rounds of interviews that took 2 weeks. The first round was with an HR Manager for a quick intro, talking about my work, and some technical questions. The HR Manager and recruiter were approachable and responsive, letting me know right away if I was moving forward. The second round was with two QA Managers, a really smooth and conversational interview, less like an interrogation. The managers explained how CDNs work and gave a high-level overview of the system. They did most of the talking. Technical questions were easy. The third round was with a QA Manager, a QA Team Member, and a Software Engineer. It involved a whiteboard and scenario-based questions. I didn't do great, but the team helped explain things and gave good feedback. Overall, a positive experience with the interviewers, especially the QA manager, from whom I learned a lot. The only downside is that after all 3 interviews, I never heard back for over a month. I reached out, and the recruiter said the position was on hold, but I suspect I was rejected since they reposted the job on LinkedIn. I think a rejection email would have been better than being ghosted.

Confirmed questions2 questions
  • Questions about object-oriented programming and the usage of functions and methods
  • Describe the QA testing steps for various scenarios in a real-life situation
StackPath logo
StackPath

Product Management Vice President

Product · more than a year ago

Executive Easy Negative experience Decline offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

Got contacted by two recruiters from Stackpath on LinkedIn. Wasn't looking but responded after multiple contacts because a former mentor works there. Had a call with Recruiter A, fitting it into my schedule. Recruiter A mentioned the next step was a coffee-chat with the hiring manager. I prepped my resume since I haven't interviewed in a while. Recruiter A then said I'd already interviewed with them. I said I hadn't interviewed in years, and he said it was through Recruiter B. I gave all my info. Recruiter A said he cleared up the confusion and Recruiter B would reach out. Recruiter B never contacted me, not even after a couple of pings. It feels like they lack basic courtesy in handling candidates, especially for executive roles. Maybe they use rookies for executive hires? This was the worst recruiter interaction ever. I'm passing on Stackpath. If this is how they treat people before an interview, imagine the culture once you join.

Confirmed questions1 question
  • Tell me about your experience managing people.
StackPath logo
StackPath

Frontend Developer

Engineering

Entry Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite Offer
Interview formats
Technical Coding

I applied online and got an employee referral. The process started with a 1-hour technical phone call, followed by a code sample submission instead of a typical technical assessment. Then, there was a technical on-site interview with the team, a QA team member, and the VP of Engineering. The entire process wrapped up in about a week, and I received the offer the next business day. Everyone involved was really friendly, helpful, and quick to respond. I genuinely enjoyed the experience, and I was particularly impressed by how fast everything moved.

Confirmed questions4 questions
  • What are your thoughts on JavaScript?
  • Can you tell me about your experience with AngularJS?
  • How do you approach workflows?
StackPath logo
StackPath

Software Engineer

Engineering

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding

First I spoke with recruiters, then a few months later I had a 45-minute chat with the Manager. After that, I got a take-home assignment. The final interview was a 1-1/2 hour grilling on specific technical topics. It seemed like they hadn't even looked at my take-home assignment.

Confirmed questions1 question
  • Can you explain the process of canceling goroutines?

StackPath Interview Questions

Quoted word for word from StackPath interview reports.

Describe the QA testing steps for various scenarios in a real-life situation

Read reports

Formats, difficulty and experience

Across all 5 StackPath interview reports.

Interview formats

Behavioral 44.4%
Technical 33.3%
Coding 22.2%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Neutral 20%
Positive 40%
Negative 40%

Reports by job function

Engineering 3
Sales 1
Product 1