How hard are Wix interviews for a Full Stack Engineer, and what difficulty do candidates report?

Candidates commonly report Wix interviews for Full Stack Engineer roles as difficult. In the collected candidate-reported results, the most common difficulty level is listed as “difficult,” with 46 reported interviews overall.

What is the interview process loop for Wix Full Stack Engineer candidates?

The process starts with an initial screening call to evaluate fit, then moves into technical assessments. Those assessments can include online coding exams and hands-on sessions, and you may need to solve problems in real time or complete take-home assignments. Later stages can include group interactions or more intimate technical discussions with engineers and team leads, and you may be asked to build something from scratch like a testing library or a UI component.

What topics are most likely tested in Wix interviews for Full Stack Engineer?

Expect heavy focus on JavaScript and algorithmic problem solving, with recurring themes like memoization or caching. Common algorithm patterns include grid and graph style problems such as “Number of Islands” and “Rotting Oranges,” plus related validity checks like “Brackets / Valid Parentheses.” React also shows up in the top topics list.

What kinds of coding questions should I practice for Wix Full Stack Engineer interviews?

Practice for matrix and grid traversal style problems, such as “Count Islands in Grid” and “Grid Simulation Propagation.” More broadly, the process also includes examples like rotting oranges or similar multi-source grid propagation simulations, and it may involve real-time problem solving or take-home work.

How many interview rounds and what is the offer rate for Wix Full Stack Engineer roles?

The dataset shows 46 reported interviews, but it does not provide a nonzero offer rate. Offer rate is shown as 0 in the provided results, so you should not assume typical positive offer outcomes from this specific dataset.

What pay should I expect for Wix Full Stack Engineer interviews?

The provided information includes interview process and tested topics, but it does not include compensation figures for Wix Full Stack Engineer candidates. Because no pay numbers are given, you should not rely on this material for an expected salary range.

WixFull Stack Engineer

Updated Jan 19, 2026

Wix Full Stack Engineer Interview Experiences 2026

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

Get your personalized Wix Full Stack 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

9 months ago

Average Positive Tel Aviv-Yafo

My interview journey started with a take-home that I had to complete during specific evening hours, and it took several hours. I then moved into a structured multi-stage evaluation where the next round was a LeetCode-based algorithmic test. After that, I got a hands-on development session on a coding platform that included an AI assistant inside the environment; I remember the interviewer explicitly preferring the integrated tool and steering me away from outside documentation or other external AI.

The hands-on segment combined coding with explaining my approach. I had to work through the task while talking through how I used the AI assistant and what I was implementing. After the coding portion, there was a system design discussion that asked about architecture at a higher level, and then I reached a final HR interview for cultural fit.

> 1 year

Difficult Positive Israel

My technical interview journey started normally enough: I went into an interview round with three LeetCode/JavaScript-style understanding questions. It felt like they were checking that I could reason about code and interpret what was being asked, not just recite solutions.

Then the process shifted into a longer, heavier chunk. I had a big assignment that lasted about three hours, preceded by a short preparation window. The task was to build a basic web element from scratch in the language I chose, and it was the part that demanded the most focus. I remember trying to get my bearings quickly, because even though the end goal sounded straightforward, the implementation work took longer than I expected.

Unlock every Full Stack Engineer interview experience

Real Full Stack 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.