Two candidates describe Lucid Motors Product Manager interviews that open with recruiter and hiring manager conversations and lean heavily on behavioral questions. One also reports a full day of product, design and engineering panels.
$131K
Avg. Base Comp
$154K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Two candidates describe Lucid Motors Product Manager interviews, and both include an early recruiter conversation followed by a hiring manager discussion. After that the reports differ, so prepare for either path.
One candidate describes a full day of separate Zoom panel sessions with product, design and engineering. Product covered product sense and execution, design focused on collaboration, and engineering covered technical topics. There was downtime between sessions, and a behavioral round with a VP came last. The candidate got a decision more than a week after the panels. They did not receive an offer.
The other candidate began with a written questionnaire and a 30-minute recruiter screen. The main round was an hour with the hiring manager and a team member, where three finalists were reportedly still in contention. Questions covered product management and technical experience, EV industry work, coding background and whether they had led a development team. An unusual question asked for their favorite non-digital product. This candidate also did not receive an offer.
Both reports are mostly behavioral. Prepare specific stories about products you shipped, how you worked with design and engineering, and decisions you made. Be ready to explain your technical background plainly, and to say why you want to work on vehicles at Lucid. Because the panels may be spread across hours, plan for stamina as well as content. Only two reports match this role, so confirm the exact format with your recruiter.
Synthesized from 6 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.
The conversation I remember most was with the senior recruiter, and not because the questions were hard. It was a 45-minute call, and the recruiter spent about 30 of those minutes talking about themselves, so I had maybe 15 minutes to actually show what I could do. I went in expecting to have to fight for airtime, and I did. The one question I can recall clearly was asking me to tell them about a time I had a difficult interaction with a customer and how, if at all, I resolved it. I'd suggest having a real example ready that you can walk through cleanly. Overall the process was five interviews, which included a recruiter, a senior recruiter, an RM, and an executive. The senior recruiter round was the one that felt off, but the rest of the process kept moving and I ended up accepting an offer.
Prep tip from this candidate
Have a customer conflict story ready with a clear situation, what you did, and how it resolved, since that's the question that came up. If a screen starts running long on the interviewer's side, be ready to steer back to your own experience with a concrete example instead of waiting for an opening.
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
How would you improve Google Maps?
| Question | |
|---|---|
| Duplicate Rows | |
| Losing Users | |
| Merchant Acquisition | |
| International e-Commerce Warehouse | |
| Hurdles In Data Projects | |
| Retailer Data Warehouse | |
| Client Solution Pushback | |
| Bagging vs Boosting | |
| Target Indices | |
| Coefficients of Logistic Regression | |
| Analyzing Churn Behavior | |
| Time on FB Distribution | |
| Ticket Agent Analysis | |
| Classification and Regression | |
| Lasso vs Ridge | |
| Evaluate News | |
| Transformer Encoder Layer | |
| FAQ Matching | |
| String Palindromes | |
| Bootstrapping Confidence Intervals | |
| Testing Constraints | |
| Search Timeout | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Decreasing Tech Debt | |
| Explaining Linear Regression to Different Audiences | |
| Quantify Uncertainty | |
| Linear vs Logistic Regression | |
| Empty Neighborhoods |
Synthesized from candidate reports. Individual experiences may vary.
Both candidates report an early recruiter conversation. One describes a 30-minute screen after a written questionnaire. These conversations focused on background and interest in the role, so you should typically be ready to explain why Lucid and why product management.
One candidate describes a straightforward hiring manager screening. The other describes an hour with the hiring manager and a team member covering technical and product experience, EV industry work, coding background and leading a development team. Expect to need concrete examples rather than a resume summary.
One candidate reports three separate Zoom panel sessions in a single day. Product covered product sense and execution, design covered collaboration, and engineering covered technical topics. Gaps between sessions meant the candidate had to stay sharp for hours. Other candidates may see a different arrangement.
The candidate with the panel day reports a final behavioral interview with a VP, then a wait of over a week for the decision. The other candidate does not describe a later round. Both reports ended without an offer, so treat each stage as a real evaluation.
