
SupplyPike Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at SupplyPike.
Software Engineer
I had a 45 minute interview with the CTO. I thought it would just be a chat, but it turned out to be a system design interview. I asked him what the worst part about working there was, and he told me it's when they don't hit their performance metrics because then he doesn't get his bonus.
- Can you design a system for parsing PDFs?
- What is the worst part about working there?
Software Engineer
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.
- What is the difference between a List and a Map, and how's a hashmap implemented at a high level?
Software Engineer
The interview was in 3 parts: first a 30-minute call to chat about my past work and some general tech questions about it. Then I had a take-home coding challenge that took me about 2 hours. Finally, I went onsite for a technical interview covering different areas like CS fundamentals, how to design software, and system architecture. I didn't get an offer in the end, but it was a good experience overall. I learned about the company and their tech stack, which sounded awesome. The people interviewing me were friendly and kept things pretty relaxed.
- Review fundamental data structures.
- Get ready to explain various concepts in detail.
SupplyPike Software Engineer 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 →“Could you explain what big-O complexities are?”
Read reports →“Can you explain what an array is?”
Read reports →“Can you design a system for parsing PDFs?”
Read report →“What is the worst part about working there?”
Read report →“Tell me about a programming problem involving sorting trucks.”
Read report →Formats, difficulty and experience
Across all 7 SupplyPike interview reports.