Shutterstock logo

Shutterstock Interview Questions
& Process

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

Based on 168 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
50.6% Positive experience

Which role are you interviewing for?

30 roles · 168 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Shutterstock.

Showing 4 of 168
Shutterstock logo
Shutterstock

Software Development Engineer in Test

Engineering · nearly a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Technical Coding Behavioral

I had a Zoom screen call where we chatted about general testing principles, the Test pyramid, and different test types. Then, there was an in-person interview (this was before COVID) which included a technical part with system/design on a whiteboard, and also an interview with HR/the Product owner.

Confirmed questions3 questions
  • Can you discuss general testing principles and the Test pyramid, including the different types of tests at each level?
  • Write code to fetch data from an API and compute values from the endpoint. This requires knowledge of async/promise handling.
  • Tell me about your experience with async/promise handling in JavaScript.
Shutterstock logo
Shutterstock

Client Success Manager

Sales · a year ago

Mid Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Background check
Interview formats
Behavioral

The interview process started with a recruiter screening call, which went well and led to an invitation for the next round. The subsequent call with the hiring manager also seemed positive, and I was told I'd proceed to a call with an APAC colleague and hear from the hiring team soon. However, after nearly 10 days of silence, I followed up. I discovered the initial recruiter no longer worked there via an OOO message. After multiple attempts to contact others at the company, I was eventually informed that my candidacy would not be moving forward, contradicting what the hiring manager had implied. This was a disappointing and unprofessional hiring experience, as I felt misled and only received final notification after I initiated contact.

Confirmed questions1 question
  • Can you share an instance where you had to deliver a challenging Quarterly Business Review (QBR)?
Shutterstock logo
Shutterstock

Legal Assistant

Legal · a year ago

Entry Easy Negative experience No offer 6 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Behavioral Technical

This was an unnecessarily long and time-consuming interview process, not recommended. I went through 6 interview rounds: first with HR, who initially said there would only be 3. Then, rounds 2, 3, and 4 were with Senior Contract Managers, and rounds 5 and 6 were with Assistant General Managers. Each interviewer asked very similar questions. It was disappointing to have to repeat myself six times and accommodate their disorganized scheduling and automated calendars. The way this company handles hiring reflects its overall operations, so I'm actually glad I didn't get the job. It was a waste of time for everyone involved.

Confirmed questions1 question
  • Can you tell me about yourself
Shutterstock logo
Shutterstock

Software Engineer

Engineering · a year ago

Entry Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Offer
Interview formats
Behavioral Technical Coding

The process had three rounds, but I only got through two before getting an offer elsewhere. First, there was a short call with HR to talk about Shutterstock and my experience. Then, I interviewed with the Hiring Manager, where I got some behavioral questions, followed by in-depth technical questions and a brief debugging task. The third round was with Engineers and was supposed to be a technical round with a coding problem, but I didn't get to that part.

Confirmed questions4 questions
  • Tell me about yourself and your experience.
  • Can you explain core Java concepts in detail?
  • Could you identify and fix the issue in this code snippet?

Shutterstock Interview Questions

Quoted word for word from Shutterstock interview reports.

How would you implement a trim function if you couldn't use built-in string libraries?

Read reports

Given a search query, how would you rank images like 'beach house' higher than an image of just a door, when both relate to the term 'house'?

Read reports

Given an array of strings like @[@"file2", @"folder22", @"folder10", @"file1", @"folder100", ...], can you describe how you'd write a method or function to sort these strings predictably, for example, getting "file1", "file2", "folder2", "folder10", "folder100" instead of the default "folder10", "folder100", "folder2"?

Read reports

Regarding traditional iOS memory management (not ARC), could you explain the difference between using 'release' and 'autorelease'?

Read reports

Could you implement a simple version of T9, first to complete a word and then to predict a word?

Read report

Can you explain how you would build a HashSet from the ground up?

Read report

Write code to fetch data from an API and compute values from the endpoint. This requires knowledge of async/promise handling.

Read report

Given some data, what is your interpretation and what could be the potential causes?

Read report

Can you implement a simple algorithm, ensure it scales, and conduct O(n) analysis on it?

Read report

Formats, difficulty and experience

Across all 168 Shutterstock interview reports.

Interview formats

Behavioral 44.3%
Technical 30.3%
Coding 9.4%
Presentation 8%
Other 3.4%

Interview difficulty

Easy 23.8%
Average 64.9%
Difficult 11.3%

Candidate experience

Positive 50.6%
Negative 32.7%
Neutral 16.7%

Reports by job function

Engineering 43
Sales 43
Operations 24
Marketing 12
Other 11
Product 10