Most candidate reports describe a recruiter screen and a hiring manager conversation, then a technical round or team panel. Content varies by role, from object-oriented design to system design and test coverage.
$153K
Avg. Base Comp
$193K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Lucid's software-adjacent interviews, as candidates describe them, usually open with a recruiter call and then a conversation with the hiring manager. The DevOps candidate, however, started directly with the hiring manager. Past that point the loop depends on the role. The accounts here come from interns, a platform validation and test engineer, and a DevOps engineer, so read them as a range of experiences rather than one fixed Software Engineer loop.
The early rounds are conversational and project-focused. The intern candidates describe recruiter calls of about 20 to 25 minutes. In one intern's hiring manager round, the manager wanted to hear what the candidate had built, which languages they used and why they made certain design choices. That candidate was also asked to talk through a project that had not gone well. Another intern was asked how they could help with the team's current problems and why Lucid appealed to them.
The technical content that follows is moderate rather than punishing. One intern saw object-oriented design questions and was asked to write a class that saves data. The validation candidate got a couple of fairly straightforward algorithm problems, then a panel of four or five back-to-back interviews, at least two of them on test case and coverage creation. The DevOps candidate, who received an offer, went from a manager call to a panel covering system design, pattern design and coding, plus questions about tools they had used and their hands-on experience.
Process quality is mixed. The validation candidate had to chase the team for updates and, after being told the team wanted to make an offer, waited more than two months with no final answer. The DevOps candidate heard back from the recruiter quickly. Ask about timelines at each stage and keep a written record of what you are told. Prepare two or three projects you can explain in depth, including what you would change.
Synthesized from 9 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Lucid Motors process.
I went through a four-stage process at Lucid that started with a recruiter screening on LinkedIn. That initial 30-minute call was pretty straightforward—they reviewed my resume and got a sense of my background. About three to four weeks later, I had a 45-minute conversation scheduled with a team lead, though it wrapped up closer to 30 minutes in reality.
The team lead interview felt rushed and somewhat surface-level. We started with the standard walkthrough of my resume and why I was interested in Lucid and the specific role. Then they moved into what they framed as assessing craftsmanship—a concept that seemed central to how they evaluate engineers. The questions were unusual and caught me off guard. They asked me to explain craftsmanship in my own words, even to imagine explaining it to a five-year-old. There were also technical questions around dimensional engineering that referenced specific automotive terminology like fender-to-fascia gaps, door-to-IP distances, and flush tolerances. I got asked about my experience with dimensional cubing and DTS systems, which felt very domain-specific and not something I'd prepared for.
One scenario they posed was interesting but uncomfortable: they described a situation where a MIC part had been drafted with three degrees instead of seven, creating a graining issue, and asked how I'd respond if a dimensional engineer said something wasn't possible. It was clearly testing how I'd handle conflict or constraints, but the framing felt more adversarial than collaborative. They also wanted to know what other products outside of cars I'd seen with exceptional craftsmanship and why.
Overall, the process felt checklist-driven rather than genuinely exploratory. The interactions were transactional, and I didn't come away feeling like they were invested in understanding how I actually work or think. I didn't receive an offer.
Prep tip from this candidate
If interviewing for engineering roles at Lucid, expect deep questions on automotive craftsmanship philosophy and dimensional tolerancing specifics (gaps, flushes, cubing, DTS). Brush up on automotive engineering terminology and be ready to discuss how you handle constraints when dimensional engineers push back on designs.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Lucid Motors
Write a query to return duplicate rows
| Question | |
|---|---|
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| The Brackets Problem | |
| Payment Data Pipeline | |
| International e-Commerce Warehouse | |
| Hurdles In Data Projects | |
| Client Solution Pushback | |
| Ticket Agent Analysis | |
| Target Indices | |
| Evaluate News | |
| Transformer Encoder Layer | |
| FAQ Matching | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Search Timeout | |
| Matrix Multiplication | |
| String Palindromes | |
| Cloud-Agnostic Deployments | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Decreasing Tech Debt | |
| Processing Large CSV | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores |
Synthesized from candidate reports. Individual experiences may vary.
Intern candidates describe a recruiter call of roughly 20 to 25 minutes covering their background, the role and fit with Lucid. The validation candidate's screen focused on their resume and project experience. Have a short account of your experience and a clear reason for wanting to work at Lucid.
One intern described a conversational round about past projects, the languages used and design decisions, including a project that went poorly. Another had a 30-minute behavioral conversation about how they could help with the team's current problems and why Lucid interested them. The DevOps candidate's manager call covered the role, their background and team fit.
One intern reported object-oriented design questions that were not overly difficult, including writing a class to save data. The validation candidate described a coding exercise with a couple of relatively straightforward algorithm problems. Another intern did not advance past the second round, and said the third round would have been a coding interview.
The DevOps candidate, who received an offer, faced a panel covering system design, pattern design and coding, plus questions about tools and hands-on experience. The validation candidate went through four or five back-to-back interviews, at least two on test case and coverage creation. Know your projects well and ask early what each session will cover.
