Wix logo

Wix Backend Engineer Interview Questions
& Process

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

Based on 16 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
62.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Wix.

Showing 3 of 16
Wix logo
Wix

Backend Developer

Engineering · a year ago

Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Onsite Background check
Interview formats
Behavioral Technical Coding System Design

We started with a 30-minute video screening with the team lead. Then, a 90-minute video call where we discussed my past projects and their architecture, along with a simple live coding challenge, with the team lead and a guild member. The next step was another 90-minute video session focused on a coding exercise with a guild member. After that, we had a 90-minute in-person meeting to go over system design with a director and a guild member. Finally, a 60-minute in-person chat with HR.

Confirmed questions1 question
  • Can you design an event-driven architecture system that incorporates an event bus and webhooks?
Wix logo
Wix

Backend Engineer

Engineering · a year ago

Mid Difficult Neutral experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Take home Onsite
Interview formats
Behavioral Technical Coding System Design

So, I went through 5 stages at Wix. First, an HR screening call to talk about my background and if I'm a good fit. Then, a technical leader interview, about 30 mins, to dig into my tech experience from past jobs. After that, a technical interview with the Server Guild. They gave an intro to the company and the guild, then we talked about my past projects, especially one I liked. I had to explain it well, including problems and solutions, and use Excalidraw to show my thinking. Then a quick coding bit on Coderpad. Next was a coding challenge. I got a problem beforehand to review and set up my dev environment. It was a home assignment using the GitHub Query API, where I had to write code to read a file of queries, run them, and show the results and count. I had an hour to code it, then we discussed my solution on Zoom. They asked how I'd change it for parallel control. I sent the solution through WeTransfer. The last interview was system design. We talked about a project I did, focusing on the design and architecture. They wanted to know how I design systems for specific needs, my knowledge of distributed systems and OS. They also asked about implementing rate control for a mailing service. But then they realized my profile wasn't exactly what they needed, so the interview wrapped up.

Confirmed questions1 question
  • How would you implement a Rate Control for a Mailing Service ?
Wix logo
Wix

Senior Backend Developer

Engineering · more than a year ago

Senior Average Neutral experience No offer 5 rounds
Interview process
Phone screen Technical screen Take home Technical screen Recruiter call
Interview formats
Technical Coding System Design Behavioral

The interview process started with a phone interview that included a short design question. This was followed by a technical interview where I was asked about a project I developed and given a coding question. Next, there was a home assignment that took about 1.5 hours to complete. After that, I had a system design question round. Finally, there was an HR interview. I was told I didn't get the job after the HR interview due to technical reasons, and that a developer would contact me with details. But no one ever got back to me. The interviewers were professional and pleasant, but I was disappointed by the lack of follow-up, which I didn't expect from this company. This led to a neutral experience.

Confirmed questions2 questions
  • Can you describe a project you developed?
  • Could you implement an LRU cache?

Wix Backend Engineer Interview Questions

Quoted word for word from Wix interview reports.

Implement a function that generates the power set of a given set.

Read reports

How would you serialize and de-serialize a binary search tree?

Read reports

Could you explain why req.body is preferred over req.params when making a POST request?

Read reports

Can you design an event-driven architecture system that incorporates an event bus and webhooks?

Read report

How would you implement a Rate Control for a Mailing Service ?

Read report

Could you share some architectural insights on designing Twitter?

Read report

What are your thoughts on designing Twitter's architecture?

Read report

Formats, difficulty and experience

Across all 16 Wix interview reports.

Interview formats

Technical 28.6%
Behavioral 24.5%
Coding 24.5%
System Design 18.4%
Presentation 4.1%

Interview difficulty

Easy 6.2%
Average 56.2%
Difficult 37.5%

Candidate experience

Neutral 18.8%
Positive 62.5%
Negative 18.8%