Wish logo
WishSoftware Engineer
Updated May 15, 2024

Wish Software Engineer Interview Experiences 2026

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

Get your personalized Wish Software 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
> 1 year
Difficult Neutral Toronto, ON

I started with an HR call, which felt fine and straightforward. After that, I had a programming challenge with an engineer in a remote setup. The tasks were centered on binary trees and graphs, and while the overall question wasn’t described as wildly complex, I struggled more than I expected with how the interviewer framed and explained it—the follow-up questions were hard to follow, which made it difficult to stay fully confident.

When the next round came, it was back to LeetCode-style problems, and this time it was genuinely hard—two LeetCode “hard” questions. I couldn’t get to a correct solution on the main problem, even though the interviewer was kind and helped walk me through parts of the reasoning. The rest of the interaction felt friendly, but ultimately the experience left me feeling like the process was more about following the right thread than just knowing the topic.
> 1 year
Difficult Negative Toronto, ON

I went through a pretty structured sequence that felt like a typical “full cycle” for software engineering. After initial conversations, I met a hiring manager first, then I had a technical round where the focus was my background and experience in a discussion format. From there it turned into a more hands-on track: coding round #1, then systems design, then a troubleshooting section that was scenario-based.

The process kept shifting between different types of evaluation, and I remember the culture-fit portion being behavioral. After that, I had a second coding round. The difficulty level felt demanding overall, but the interviewers were engaged and the process was organized enough that I could follow where I was in the loop. I left with the sense that the bar wasn’t just “can you code,” but “can you think through real scenarios,” while also communicating clearly during the troubleshooting and system design pieces.

Unlock every Software Engineer interview experience

Real Software 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.

What to expect

Distilled from the reports

Interview Structure & Flow

The interview process typically involves an initial HR screen followed by multiple technical rounds, including coding, systems design, and behavioral discussions. Candidates noted that the structure varied but often included a mix of LeetCode-style problems and practical coding tasks.

HR screenTechnical roundsBehavioral

Technical / Coding Screen

Candidates faced a range of technical challenges, primarily focused on data structures and algorithms, with some experiencing high-pressure coding sessions that emphasized performance and correctness. The difficulty varied, with some describing the problems as 'hard' and others noting a lack of guidance during the coding tasks.

Data structuresAlgorithmsLeetCode

Behavioral & Values Assessment

Behavioral questions were common, often focusing on past experiences and cultural fit, but some candidates felt the tone was overly critical or dismissive. The assessment of values seemed inconsistent, with some candidates feeling judged on personal biases rather than their skills.

Behavioral questionsCultural fitCritical tone

Communication & Feedback

Candidates reported mixed experiences regarding communication, with some appreciating timely updates while others faced significant delays or a complete lack of follow-up after interviews. This inconsistency contributed to feelings of frustration and uncertainty about their standing in the process.

CommunicationFeedbackTimeliness

Interview Difficulty & Expectations

The overall difficulty of the interviews was perceived as demanding, especially in technical rounds, but candidates also noted a lack of clarity on what the interviewers valued. Some felt the interviews were more about proving knowledge than demonstrating problem-solving skills.

Interview difficultyExpectationsProblem-solving

Candidate Experience & Environment

The candidate experience varied widely, with some reporting a structured and respectful process while others encountered disorganization and unprofessional behavior from interviewers. This inconsistency affected candidates' perceptions of the company culture and their overall impression of the interview process.

Candidate experienceProfessionalismCompany culture