SupplyPike logo

SupplyPike Interview Questions
& Process

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

Based on 14 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
57.1% Positive experience

Which role are you interviewing for?

7 roles · 14 reports

Candidate interview experiences

First-hand accounts from people who interviewed at SupplyPike.

Showing 4 of 14
SupplyPike logo
SupplyPike

Graphic Designer

Design · a year ago

Mid Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Background check
Interview formats
Technical Behavioral

It started with 2 introductions, then 2 technical interviews, and finally a culture fit assessment. The interviewers were very interactive and kept me updated throughout, while also challenging me to ensure I was a good fit for the role.

Confirmed questions2 questions
  • Can you walk me through your technical design prompt and answer follow-up questions?
  • What are your thoughts on the technical design prompt?
SupplyPike logo
SupplyPike

Marketing Coordinator

Marketing · a year ago

Entry Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Presentation Background check Offer
Interview formats
Behavioral Presentation

The communication was pretty bad. They said there would be a presentation for the technical interview, but they never sent over the prompt. I had to chase them for it and found out I wasn't the only one who had this issue. After two interviews and two follow-up emails, I was ghosted. Then, two months later, I got an automated rejection.

Confirmed questions4 questions
  • Can you share an instance where you encountered a difficulty in marketing?
  • Describe a time you were responsible for coordinating a marketing campaign.
  • Provide an example of a marketing effort that you contributed to that was successful.
SupplyPike logo
SupplyPike

Senior Account Executive

Sales · more than a year ago

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Take home Presentation Onsite
Interview formats
Behavioral Presentation Group Other

This was the most thorough, confusing, and misleading interview process I've ever been through. It took about a month. First, there was a call with the recruiter about salary and career path. Then, I had a 40-minute personality assessment. After that, I had to prepare a presentation for a panel of 5 based on a scenario. This took about 2 hours to prep the content/demo, and the actual call was about an hour and a half of questions and feedback. The goal seemed to be understanding my selling style and how I present. Finally, there was a 2-day in-person culture fit interview with 6.5 hours of back-to-back meetings with the executive staff. I only found out who I was meeting the night before, and most didn't have questions. Even though I got positive feedback throughout, the offer was 25% lower than discussed. I felt insulted and confused about what changed. Pushing back got me a 'max budget' response, which felt misleading and destroyed my trust. It seemed like poor communication and inexperience from the team. It was frustrating to invest so much time in prep, interviews, and travel for a significantly lower offer. I suggest a smoother process and honesty about compensation.

Confirmed questions3 questions
  • What are you looking for in terms of career advancement?
  • How will you uphold our company culture in a remote setting?
  • What aspects of this role generate enthusiasm for you?
SupplyPike logo
SupplyPike

Software Engineer

Engineering

Senior Average Positive experience Accept offer 3 rounds
Interview process
Phone screen Technical screen Take home Onsite
Interview formats
Technical Coding Behavioral

The interview process happened in 3 main stages: 1. Phone screen I spoke with a developer over the phone. It was fairly short (~30 mins), and covered pretty basic stuff. What technologies do you use and why? That sort of thing. Kanat (the engineer I spoke with) was smart and engaging, and gave me plenty of information about the company and how it works. 2. Code project / Questionnaire I next did a short (~10 minute) timed quiz with basic CS questions. It was short and not that complicated, even for someone like me who's been out of school for a while. After that, I had ~2 hours to write and submit a simple code project. The technology stack was not dictated, and overall the code project was pretty open ended. I enjoyed it. 3. Final interview Finally, I went over the code project with the same engineer (Kanat) that did the phone screen. I walked him through the decisions that I had made and why, and he had plenty of insightful questions. This process took maybe an hour and a half, but that might be because I'm talkative.

Confirmed questions1 question
  • What is the difference between a List and a Map, and how's a hashmap implemented at a high level?

SupplyPike Interview Questions

Quoted word for word from SupplyPike interview reports.

What is the difference between a List and a Map, and how's a hashmap implemented at a high level?

Read reports

Can we work together to build a dynamic array like ArrayList?

Read reports

Tell me about a programming problem involving sorting trucks.

Read report

How do you manage when you have multiple marketing tasks demanding your attention at the same time?

Read report

What's your approach when a client dislikes your work?

Read report

Formats, difficulty and experience

Across all 14 SupplyPike interview reports.

Interview formats

Behavioral 29.4%
Technical 26.5%
Coding 14.7%
Presentation 11.8%
System Design 5.9%

Interview difficulty

Easy 7.1%
Average 71.4%
Difficult 21.4%

Candidate experience

Positive 57.1%
Negative 28.6%
Neutral 14.3%

Reports by job function

Engineering 7
Design 2
Sales 2
Operations 2
Marketing 1