Real, anonymous reports from people who interviewed for Software Engineer at Lucid Software, newest first and distilled into what to expect across the loop.
Get your personalized Lucid Software 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.
After applying, I started with a CodeSignal pre-screen focused on general coding framework skills. A short time later, I moved into a virtual coding interview, and then the process narrowed down into a final stretch of several interviews focused on algorithm work and object-oriented modeling.
The part that stood out to me was how the final stage felt like a true sprint: back-to-back sessions centered on LeetCode-style problems and then class design, with the OOP component coming up explicitly as its own chunk rather than being folded into coding. Overall, the questions weren’t framed as puzzle-box trickery so much as timed implementation and clean reasoning, and it made the whole process feel structured and fairly demanding even though the overall difficulty landed around average. I didn’t end up getting an offer, but I walked away feeling like the expectations were clear and consistently aligned across the later rounds.
8 months ago
Average Positive Raleigh, NC
My process felt compact but intense. After the initial steps, the interview sequence ended up including a first round where I worked on two easy LeetCode-style problems and then finished part of a small game implementation.
The final stage was split into two one-hour blocks. The first block was two medium LeetCode problems to solve within an hour. The second block shifted from algorithms to OOP-focused work: class design and behavioral questions running together, with the class design being the hardest part to get right under the clock.
8 months ago
Difficult Positive United States
My interview journey started with an OA and then moved into a multi-part sequence where everything ramped up into more involved technical work. The ne…
8 months ago
Difficult Positive Salt Lake City, UT
I got far enough to experience an early coding-style step and then a second, more holistic conversation with an engineer, but the process was clearly …
9 months ago
Difficult Positive United States
My first step was a technical screening, and then I moved into a final round that featured three engineers. That last round was an advanced, live codi…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Assessment
Candidates typically start with an online assessment that includes a mix of easy to hard coding questions, often featuring LeetCode-style problems and game design tasks. This stage serves as a gatekeeper to the subsequent rounds, emphasizing the importance of completing tasks within the time limit.
Online AssessmentLeetCodeGame Design
Technical Interviews
The technical interviews are structured into multiple parts, often including a combination of algorithmic problems and object-oriented programming (OOP) design challenges. Candidates should expect to demonstrate both coding skills and the ability to articulate their thought process under time constraints.
Technical InterviewOOP DesignAlgorithm Problems
Behavioral Interviews
Behavioral interviews are integrated into the process, often occurring alongside technical discussions. Candidates may receive a list of example questions in advance, allowing them to prepare effectively for these conversational segments.
Behavioral InterviewSTAR MethodCommunication
Live Coding Experience
Some candidates experience live coding sessions where they solve problems in real-time while being observed by interviewers. This format requires candidates to explain their reasoning and approach as they work, adding a layer of pressure to perform accurately and efficiently.
Live CodingReal-Time Problem SolvingPressure
Class Design Focus
A significant emphasis is placed on class design and object-oriented modeling, often as a separate segment in the final rounds. Candidates should be prepared to articulate their design choices and demonstrate clean, structured code under time constraints.
Class DesignOOPStructured Code
Overall Experience & Feedback
Candidates report a generally structured and demanding interview process, with a focus on both technical skills and communication. While many do not receive offers, they often appreciate the clarity of expectations and the respectful atmosphere throughout the interviews.