ZapLabs logo

ZapLabs Interview Questions
& Process

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

Based on 25 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
44% Positive experience

Which role are you interviewing for?

11 roles · 25 reports

Candidate interview experiences

First-hand accounts from people who interviewed at ZapLabs.

Showing 4 of 25
ZapLabs logo
ZapLabs

Front End Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding Presentation

The interview process was pretty fast and easy. I applied, and a recruiter called me the next day to set up an initial ~15 min chat. That was just to go over the company and role and see if it felt right for both of us. A couple days later, the recruiter called again to schedule a technical interview over Google Hangouts with two devs. It lasted about an hour. We spent the first 10-15 mins on general JS and CSS stuff. Then, they gave me an image and asked me to build a basic page layout with HTML, CSS, and JS in CodePen within 10-15 mins. After that, they showed me a nested JSON object from an API and asked me to write code to map keys from one object to values in another, also taking about 15 mins. The devs were nice and helpful, explaining things when I asked. Then, I got a call to set up an on-site interview for later that week. It was about 4 hours long and had a few parts. First, two front-end engineers asked more JS/CSS questions (like using vanilla JS for event listeners, event delegation, AJAX/fetch) and gave me two code snippets to predict the output, including ones with setTimeout and variable scope issues. The rest of the interviews were non-technical chats with people from product, QA, and design. I got a call with a job offer a few days later after a holiday weekend, and I took it.

Confirmed questions4 questions
  • Can you tell me about the tools you use for debugging JavaScript?
  • What is your understanding of the fetch API?
  • What functionality does the ~ CSS selector provide?
ZapLabs logo
ZapLabs

Java Developer

Engineering

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Coding Technical Behavioral

The interview process was pretty standard. First, there was a Skype interview where I was asked two coding questions. Then, I had an onsite interview with nine people. Most of the interviewers were friendly, but one was very rude and unprofessional. She gave me a linked list problem to solve on a whiteboard. After a few minutes, she started talking to her colleague, which was very disturbing. She didn't understand the code and wouldn't let me explain. At the end, when she asked if I had any questions, I asked about new products, and she responded rudely, implying it was a strange question and that I had no respect for the company.

Confirmed questions4 questions
  • Questions about algorithms.
  • Java programs focusing on linked lists.
  • Java programs focusing on stacks.
ZapLabs logo
ZapLabs

Software Engineer

Engineering

Entry Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

Had a phone call with the recruiter, then a one-hour technical interview. The technical interview had some basic JS and CSS questions and shared-screen coding challenges. The technical interview was pretty easy, like a fizz-buzz level. A week later, I got rejected, they said I missed a question, but I don't remember missing anything or the interviewer mentioning it. It felt like a waste of time, with seemingly random judgments from subpar engineers asking really basic questions to check if you're a 'real' engineer.

Confirmed questions2 questions
  • How would you use CSS to align elements?
  • Can you explain async JavaScript concepts like setTimeout?
ZapLabs logo
ZapLabs

Operations Manager

Operations

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Phone screen Onsite Background check
Interview formats
Behavioral Technical

Applied and got a quick call from a recruiter. That went well so I had a follow up call with the hiring manager. Then I was invited for an on-site with 4 people from different departments. Bad part was towards the end, I was supposed to meet with the hiring manager but the recruiter said he was unavailable and apologized for the screw-up. Big red flag and wasted my time preparing and traveling. Never heard back from them after the interview. Good thing I found a better job shortly after.

Confirmed questions1 question
  • Could you explain your interest in ZapLabs?

ZapLabs Interview Questions

Quoted word for word from ZapLabs interview reports.

What if you could remove one character from a string – how would you then check if it's a palindrome?

Read reports

How would you remove duplicates from an integer array and return a new one?

Read report

Build a basic Android app that fetches and displays data from a mock REST API in a list with images and text.

Read report

Can you solve the duplicate numbers in a string problem, aiming for an optimized solution with a hashset instead of nested loops?

Read report

Could you write the code to generate a Fibonacci series?

Read report

Formats, difficulty and experience

Across all 25 ZapLabs interview reports.

Interview formats

Technical 37.3%
Behavioral 28.8%
Coding 28.8%
System Design 3.4%
Presentation 1.7%

Interview difficulty

Easy 28%
Average 72%
Difficult 0%

Candidate experience

Positive 44%
Neutral 20%
Negative 36%

Reports by job function

Engineering 20
Analytics 2
Sales 1
Research 1
Operations 1