Real, anonymous reports from people who interviewed for Software Engineer at Lucid Software, newest first and distilled into what to expect across the loop.
My first step was an online assessment, and it quickly turned into a LeetCode-style process where coding showed up across most rounds. I remember having multiple programming questions that leaned into algorithms and class/object design, including game-related logic—one of those setups where the code actually had to work and not just sketch the idea.
After I applied, the process kicked off with a recruiter-style pre-screen through CodeSignal, focused on general coding skills. Once I passed that, I moved into a virtual coding interview and then into the later stages with multiple interviews centered on algorithms and class modeling. Overall it felt like a pretty structured gauntlet rather than anything open-ended.
The interview process typically begins with an online assessment, followed by multiple technical interviews over Zoom, often spanning several weeks. Candidates noted a structured progression through coding challenges, design discussions, and behavioral interviews.
Candidates faced a variety of coding challenges, primarily LeetCode-style problems, with a significant focus on algorithms and game-related logic. The coding interviews often required real-time coding while being observed, which added pressure.
A strong emphasis was placed on class design and object-oriented programming, with candidates expected to demonstrate clean and efficient code structure. Many found this aspect particularly challenging under time constraints.
Behavioral interviews were integrated into the process, often focusing on candidates' past experiences and problem-solving approaches. Interviewers were generally described as friendly and supportive, fostering a communicative environment.
Candidates reported a high level of difficulty, particularly with time management during coding tasks and the pressure of live coding sessions. Many felt that the intensity of the interviews was a significant factor in their performance.
Several candidates expressed a desire for more practice with game-related logic and class design prior to the interviews, as well as better pacing during coding tasks to allow for thoughtful design and implementation.