Real, anonymous reports from people who interviewed for Software Engineer at WeWork, newest first and distilled into what to expect across the loop.
After a recruiter call to talk through my background and what I was hoping to get from the role, the process moved into a more technical set of interviews. My understanding was that it would stay organized and reasonably balanced, and it did: there was a technical discussion that mixed coding with system design and also pulled in details about a couple of my past projects.
My interview ended up feeling messy and drawn out in the wrong way. I had multiple “drives” scheduled back-to-back in a single day—one was set for 9:00 but didn’t really start until later, and there was another drive scheduled for the afternoon that I ended up canceling because the HR timing was unprofessional.
The interview process typically begins with a recruiter call focused on assessing fit and providing an overview of the role, which is often straightforward and serves as a preliminary filter before deeper technical discussions.
Candidates can expect multiple technical rounds that include LeetCode-style coding questions, focusing on data structures and algorithms, with an emphasis on clarity and correctness under pressure.
Interviews often include system design discussions that require candidates to articulate high-level and low-level design concepts, including architecture, APIs, and scalability considerations, though the clarity of expectations may vary.
Behavioral rounds are structured, often using the STAR method, where candidates share specific past experiences related to teamwork, problem-solving, and handling challenges, contributing to the overall evaluation of fit.
Candidates frequently report frustrations with scheduling and communication, including delays in feedback and disorganized interview timelines, which can detract from the overall experience and clarity of the process.
The overall difficulty of the interviews is perceived as average to high-pressure, with candidates noting varying levels of support and clarity during technical discussions, impacting their performance and confidence.