
Storyblocks Software Engineer 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
Candidate interview experiences
First-hand accounts from people who interviewed at Storyblocks.
Software Engineer
A recruiter contacted me about a job. I met with a lead engineer for coffee and some light technical questions. We talked about my background and what technologies I'm interested in. Then I went to their office for four technical interviews and lunch. The problems were tough but enjoyable. The office vibe was super relaxed, and everyone seemed happy. You can expect questions about algorithms, object-oriented programming, and Clean Code principles.
- Can you expect questions concerning algorithms, object oriented programming, and Clean Code concepts?
- Can you expect questions concerning algorithms, object oriented programming, and Clean Code concepts?
- Can you expect questions concerning algorithms, object oriented programming, and Clean Code concepts?
Software Engineer
Got contacted by a recruiter initially. First up was a phone screening call with an engineer. Then, I had an onsite interview that lasted about 5-6 hours. It included several 1:1 interviews and some pairing/whiteboard sessions with company engineers. I also had a nice offsite lunch with three people from the company and got a tour of the office. They let me know their decision within a couple of days after the onsite.
- Questions on general problem solving abilities
- Questions involving whiteboarding
- Questions that are coding problems
Software Engineer
The interview process was pretty straightforward, with a good mix of questions. It felt respectful and friendly. There were two interviews focused on culture and one technical interview. All the interviews were designed well.
- What are your thoughts on diversity?
Storyblocks Software Engineer Interview Questions
Quoted word for word from Storyblocks interview reports.
“Was there a second system design session, even though the details aren't recalled?”
Read reports →“For system design, was there a session focused on designing a feature flag service using a SQL DB, emphasizing DB design?”
Read reports →“Was there a coding/algorithmic question on the second phone round involving Levenshtein distance and strings, but without actual coding?”
Read reports →“Did the virtual on-site include algorithmic/LeetCode style sessions (easy/medium), like one problem involving balancing parentheses?”
Read reports →“Can you expect questions concerning algorithms, object oriented programming, and Clean Code concepts?”
Read report →“What are your thoughts on diversity?”
Read report →“Did you have a SQL database design question covering relational data modeling, design, and SQL clauses like select, where, join, and handling different relationship types like one-to-many and many-to-many?”
Read report →“Can you describe a situation where you worked with a stack?”
Read report →Formats, difficulty and experience
Across all 5 Storyblocks interview reports.