Zulily logo
ZulilySoftware Engineer
Updated Apr 18, 2024

Zulily Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Zulily, newest first and distilled into what to expect across the loop.

Get your personalized Zulily Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
> 1 year
Average Neutral Seattle, WA

I started with a recruiter phone screen, and about a week later I was pulled into a technical session and then straight into an onsite day. The onsite was a marathon: five back-to-back interviews without much breathing room. Three rounds were coding, and the problems felt like medium LeetCode-style tasks. There was also a behavioral round where they asked questions about how I work and what kind of situations I’ve handled before, and the last part was system design.

Overall the difficulty felt average, but the pacing made it mentally heavy. The format was consistent and structured—alternating between coding and non-coding discussion—so I could tell what they were evaluating at each step. Interviews were largely straightforward, and even when the questions were challenging, the flow was predictable enough that I didn’t feel completely thrown off.
> 1 year
Average Positive United States

My process began with a recruiter conversation, then I had a call with the hiring manager. After that, the full loop felt classic and tightly packed: two coding rounds, one system design round, and then an extra round focused on PM/culture fit. One coding round skewed toward front-end, while the other leaned more into data structures and algorithms.

When I reached the onsite stage, the day followed a familiar cadence—multiple technical conversations plus one behavioral discussion with a director-level interviewer. A few interviewers were friendly and easy to talk to, but the hiring manager’s style stood out. There was a lot of self-focus and bragging during the interaction, and it threw me off because I felt like I was being judged less on how I thought and more on whether I matched their preferred vibe. Even so, I kept my approach grounded in how I’d solve the problems rather than trying to second-guess what they wanted.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Timeline

The interview process typically starts with a recruiter call followed by a technical phone screen, leading into a full-day onsite with multiple rounds, often including coding, system design, and behavioral interviews. Candidates should expect a tightly packed schedule, often with five or more interviews in a single day.

Recruiter callOnsiteInterview rounds

Coding & Technical Evaluation

Candidates will face multiple coding rounds focused on algorithms and data structures, often resembling medium-level LeetCode problems. Expect a mix of coding challenges and system design discussions, with varying levels of difficulty and expectations based on the interviewer's style.

AlgorithmsData structuresLeetCode

Behavioral & Cultural Fit

Behavioral interviews are a significant part of the process, assessing candidates' past experiences and cultural fit. Interviewers may focus on communication style and team dynamics, which can heavily influence the outcome, sometimes overshadowing technical performance.

BehavioralCultural fitCommunication

Interviewer Dynamics

The demeanor and engagement level of interviewers can vary significantly, impacting the candidate's experience. Some candidates reported friendly and supportive interactions, while others faced interruptions or a lack of engagement, which affected their performance and overall impression of the process.

Interviewer behaviorEngagementSupportive

Feedback & Communication

Candidates often experienced delays in feedback and communication throughout the process, leading to frustration and uncertainty. Clear and timely communication from recruiters and interviewers is inconsistent, with some candidates feeling left in the dark post-interview.

FeedbackCommunicationFollow-up

Overall Difficulty & Outcome

The overall difficulty of the interviews is generally perceived as average, but candidates often felt that their technical abilities were not the sole focus of the evaluation. Many left without offers, feeling that subjective fit assessments played a significant role in the decision-making process.

DifficultyOutcomeSubjective fit