Zwift logo

Zwift Interview Questions
& Process

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

Based on 64 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
60.9% Positive experience

Which role are you interviewing for?

29 roles · 64 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Zwift.

Showing 4 of 64
Zwift logo
Zwift

CRM Marketing

Marketing · nearly a year ago

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

The interviewers kept asking why I wanted to join Zwift and this particular marketing role. They didn't really dive into my past work experience, so I had to bring up my own projects myself. After two interview rounds, I got an automated rejection email, which felt pretty disrespectful. I also have a feeling this job posting might have been a ghost job.

Confirmed questions1 question
  • Can you explain how your personal interests and hobbies connect with the responsibilities of this position at Zwift?
Zwift logo
Zwift

iOS Engineer

Engineering · nearly a year ago

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

I was first contacted by the recruiter. Then, I had a 45-minute behavioral interview with the hiring manager. After that, there was a 45-minute technical interview with two engineers. The technical challenge involved making a request to a weather API to check if it was raining in a chosen language. It seemed pretty simple, but unfortunately, I didn't get past this stage.

Confirmed questions7 questions
  • Can you tell me about a time you dealt with a challenging teammate?
  • What is one area you are currently focused on improving?
  • Share an instance where you encountered and resolved a difficult problem.
Zwift logo
Zwift

Logistics Analyst

Operations · a year ago

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

So I went through this whole interview thing for this company, it was like four rounds long, and it didn't work out. The second round with the hiring manager was a real bummer. It felt like she had already decided or was just being super rude and unprofessional, which made things awkward and killed my motivation. Even though I felt like it was a dead end, they still wanted me to talk to more people. It felt like a waste of my time, especially since I had to take off work for it. If they had made up their mind, they should have just ended it then instead of dragging it out. It just left a bad taste in my mouth about how they hire people, like they weren't upfront, empathetic, or respectful of my time. I won't be applying there again and would tell others to be careful about spending their time on it.

Confirmed questions1 question
  • Can you explain how your background and experience relate to this specific job position?
Zwift logo
Zwift

Software Engineer

Engineering · more than a year ago

Senior Difficult Negative experience Decline offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Group Presentation Offer
Interview formats
Behavioral Technical Coding System Design

Started with a recruiter chat, then met with a senior engineering manager. Next, there was a tech screening with two software engineers, followed by a technical interview with two other software engineers. After that, I had a product meeting with a technical product manager and a product manager, which was my favorite part because they were enthusiastic about their work. Then came a leadership meeting with two engineering managers, though I found it a bit unhelpful as they weren't clear on evaluation criteria or 1-1 cadence, possibly due to being new. Finally, I had a wrap-up with the senior engineering manager, which was frustrating because they couldn't meet my previously discussed salary range despite initial assurances. The technical interviews were tough, focusing on algorithms that didn't feel super relevant to daily tasks, though the second coding interview was better paced and more practical, involving organizing fetched data into columns. The initial screening felt like a rapid-fire test of knowledge.

Confirmed questions6 questions
  • Can you explain the time complexity of this?
  • Could you describe how you'd organize fetched data into columns of equal length?
  • How would you build a CSS view to display organized columns of information?

Zwift Interview Questions

Quoted word for word from Zwift interview reports.

Given the code `var arr = [1, 2, 3]; for (var i = 0; i < arr.length; i++) setTimeout(()=>console.log(arr[i]), 1000)`, what will be printed to the console?

Read reports

Implement a feature using a weather API to check for rain in your preferred programming language.

Read reports

How would you build a CSS view to display organized columns of information?

Read report

What are the differences between MVVM and MVC, and how would you incorporate caching into a project?

Read report

What defines an 11-star e-commerce experience in your view?

Read report

Formats, difficulty and experience

Across all 64 Zwift interview reports.

Interview formats

Behavioral 47%
Technical 32.8%
Coding 6.7%
Presentation 6%
Other 3.7%

Interview difficulty

Easy 21.9%
Average 70.3%
Difficult 7.8%

Candidate experience

Negative 23.4%
Positive 60.9%
Neutral 15.6%

Reports by job function

Engineering 32
Operations 8
HR 7
Analytics 4
Other 4
Marketing 3