Real, anonymous reports from people who interviewed for Software Engineer at Wix, newest first and distilled into what to expect across the loop.
I went through a relatively comfortable early-stage process for a Software Engineer role, and I was not ultimately advanced.
I went through a kickstart-program style path centered on a longer coding exam, with a tougher experience overall and an early cutoff.
The interview process typically begins with a friendly recruiter screen focused on background and cultural fit, often followed by a technical background discussion with a hiring manager or team lead. Candidates should prepare to articulate their experience and alignment with the company's values.
Candidates can expect multiple coding assessments, often in a LeetCode-style format, with varying difficulty levels. Preparation should include practicing algorithm problems and coding under time constraints, as performance in these rounds is critical for advancement.
Technical interviews often involve live coding sessions and problem-solving discussions, with a focus on JavaScript fundamentals and system design. Candidates should be ready to explain their thought process and demonstrate coding skills in real-time.
Some candidates may encounter take-home assignments that require completing coding tasks within a specified timeframe. It's important to carefully read the instructions and ensure that submissions align with expectations to avoid misunderstandings.
Later stages often include system design interviews where candidates must demonstrate their ability to architect solutions for real-world applications. Clear communication and a structured approach to design are essential for success in these discussions.
Candidates frequently report a lack of feedback after interviews, which can be frustrating. However, some candidates do receive actionable insights post-interview, making it beneficial to follow up for feedback regardless of the outcome.