Wix.Com Software Engineer interview typically runs 4 rounds: recruiter call, technical coding interview, project deep-dive, design/HR. It usually takes about 2-4 weeks and is notably coding-heavy and somewhat ambiguous.
$140K
Avg. Base Comp
$177K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
We’ve seen Wix lean heavily toward candidates who can turn a prompt into working code quickly, especially when the problem is framed as a small product or UI feature rather than a pure algorithm exercise. Multiple candidates reported closures, currying, memoization, and function chaining showing up alongside classic tree and grid problems, which tells us the team cares about whether you can move fluidly between JavaScript fundamentals and implementation details. The recurring pattern is not just correctness, but whether you can keep your solution clean under pressure when the interviewer keeps the scope intentionally broad.
A second theme is that Wix seems to value engineers who can reason from incomplete or slightly awkward requirements. Our candidates repeatedly described prompts like implementing a Snake game, a shopping cart for an early-stage product, or a React card game, and the harder part was often translating the ask into a sensible structure. That’s where tradeoff clarity matters: interviewers appeared to probe whether a solution was overcomplicated, and several candidates felt the conversation shifted toward judging design judgment more than raw coding ability. We’ve also seen a few reports of interviewers being terse or interruptive, so candidates who stay calm and keep narrowing the problem with precise questions tend to do better.
The strongest signal across experiences is that Wix rewards people who are comfortable with practical algorithmic implementation: parent-pointer LCA, 2D matrix search, BFS/DFS-style spreads, and timed coding tasks all came up repeatedly. In other words, this is not a process where polished theory alone carries you; the bar is whether you can produce reliable code in a messy, time-boxed setting and explain why your approach fits the constraints.
Synthetized from 4 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Wix.Com process.
After a recruiter call, I had a 1.5 hour first interview with two engineers from Wix. They spent a few minutes introducing themselves and explaining how their teams are organized, including the Guild structure, which was a nice way to set the context before jumping into coding. The interview was fully live-coding and had three questions. The first was to implement sum(n)(m) and then use it in a specific loop-style example, so it was really testing function chaining and how comfortably I could work with closures. The second was to build a generic memo function, and the third was a lowest common ancestor problem where you only have parent pointers, so you need to solve it in O(h) time and O(1) space. That last one was the hardest part for me because it was less about tree traversal and more about reasoning from parent links only.
I also had a separate conversation where they asked me to walk through a project, but that part felt awkward because I was interrupted a lot and it was hard to finish my answers. The coding itself was not especially difficult, but the overall vibe made the process feel a bit strange. I didn’t move forward after that round, and the recruiter later called me back, plus one of the interviewers followed up with detailed feedback, which I appreciated. My main takeaway is to be very sharp on closures/memoization and to practice LCA with parent pointers specifically, since that was the most distinctive algorithm question they asked.
Prep tip from this candidate
Practice implementing closure-based functions like sum(n)(m) and a generic memoizer in a live-coding setting. Also drill lowest common ancestor when you only have parent pointers, because they wanted O(h) time and O(1) space.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Wix.Com
Migrating a social network's data from a document database to a relational database for better data metrics
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Random SQL Sample | |
| Minimum Change | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top 3 Users | |
| Prime to N | |
| The Brackets Problem | |
| Find the Missing Number | |
| Upsell Transactions | |
| Monthly Customer Report | |
| P-value to a Layman | |
| Scrambled Tickets | |
| First Touch Attribution | |
| Hurdles In Data Projects | |
| Download Facts | |
| Google Maps Improvement | |
| Job Recommendation | |
| Bagging vs Boosting | |
| Employee Project Budgets |
Synthesized from candidate reports. Individual experiences may vary.
The process typically starts with a recruiter call to introduce the role and gauge basic fit. In some cases, the recruiter also follows up later with next steps or feedback after a technical round.
Candidates meet with one or two engineers, sometimes including a developer and an architect, for a live technical interview. This round often mixes JavaScript fundamentals with algorithm questions such as closures, currying, memoization, and tree or array problems.
A major part of the process is a timed coding exercise, often on Zoom or in a classroom setting. Candidates solve several LeetCode-style problems and may also build small implementations like a Snake game, Pac-Man, a React card game, or other UI-heavy tasks under time pressure.
Some candidates are asked to walk through a past project and then answer a design question. Examples include designing shopping cart functionality for an early-stage Wix product, with interviewers probing tradeoffs and implementation choices.
After the technical rounds, candidates may have an HR conversation. This appears to be a later-stage discussion following the main technical evaluation rather than an early screening step.