Zenefits logo

Zenefits Frontend Engineer Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
22.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Zenefits.

Showing 3 of 9
Zenefits logo
Zenefits

Senior UI Developer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Coding Technical Behavioral

The interview process involved a phone call with a recruiter, followed by a remote coding test. The final stage was a full-day onsite interview. During the onsite, the technical focus was on object-oriented JavaScript and CSS layout construction. The onsite had many technical and logistical problems, like the interview room being double-booked. A developer even rudely kicked me out of the room. Asking about regulatory issues was not well-received. I was told I'd hear back in 5 days, but got ghosted for a month until I escalated via email. It was a really bad experience.

Confirmed questions1 question
  • Can you describe how you handle disagreements with team members?
Zenefits logo
Zenefits

UI Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite Technical screen
Interview formats
Technical Coding Presentation

It started with a regular HR phone call, then I had to submit a project. After that, they set up technical video/codepen interviews. Then came 2 one-on-one technical interviews focusing on basic JS concepts, which took about 3 weeks. They initially wanted me to come onsite, but then cancelled it because their employees weren't available. So, instead, they scheduled 2 more technical 2-on-1 screens (weirdly, having two interviewers didn't help and just made it awkward) and then rejected me. It felt like they'd already found someone and were just looking for reasons to say no. No feedback was given either.

Confirmed questions2 questions
  • What are JavaScript closures and context?
  • Can you build these HTML and CSS mockups?
Zenefits logo
Zenefits

UI Engineer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Technical Coding Presentation

I found out about Zenefits through a classmate and applied online. A recruiter got in touch quickly for a first call. After that, I had a technical phone interview where we talked about product/design and JavaScript basics, focusing on real-world uses rather than algorithms. The on-site part involved hands-on coding and chats with the team. I did some whiteboarding, but most coding was practical JS and CSS, and I always ended up with working code. I was expecting more algorithm problems, but enjoyed the collaborative and learning-focused process. The interviewers were great, and I was excited to accept the offer!

Confirmed questions1 question
  • Live coding a UI or mock in JSFiddle/Codepen

Zenefits Frontend Engineer Interview Questions

Quoted word for word from Zenefits interview reports.

Based on the provided javascript code snippet, what value would 'this' resolve to?

Read reports

What is the expected output for 'this' in a given context?

Read reports

Could you explain the concept of 'this' in javascript?

Read report

Can you describe how you handle disagreements with team members?

Read report

Formats, difficulty and experience

Across all 9 Zenefits interview reports.

Interview formats

Coding 34.8%
Technical 34.8%
Behavioral 21.7%
Presentation 8.7%

Interview difficulty

Easy 11.1%
Average 66.7%
Difficult 22.2%

Candidate experience

Negative 44.4%
Neutral 33.3%
Positive 22.2%