Lucid logo

Lucid Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 56 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
55.4% Positive experience

Which role are you interviewing for?

25 roles · 56 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Lucid.

Showing 4 of 56
Lucid logo
Lucid

Recruiter

HR · nearly a year ago

Senior Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

I had an initial interview with the Hiring Manager, who oversees the Hardware Engineering Recruiters. There were about 15 recruiters on that team at the time. After that, I interviewed with one of the Sourcers, and we talked about sourcing and searching for candidates.

Confirmed questions1 question
  • What sets your recruiting approach apart or makes it unique?
Lucid logo
Lucid

Software Engineer

Engineering · nearly a year ago

Entry Difficult Positive experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Coding Technical

It started with an online assessment (OA) that had 4 scored questions. After that, there was a coding interview. The coding interview had 2 warm-up questions, and then I had to finish implementing a game. Unfortunately, I didn't get past this stage. The interviewer was really nice, though.

Confirmed questions1 question
  • Can you implement a game in Python?
Lucid logo
Lucid

Studio Manager

Operations · more than a year ago

Mid Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

The interview process was not very enjoyable. The initial recruiter call was nice, but after that, each interview was arranged via email by a different recruiter who wouldn't reply to emails. One recruiter suggested texting with questions, but I never got a response. Two interviewers seemed unqualified; one was unprepared, and another had only been with the company two weeks and wasn't even scheduled for the call. It's hard to interview for a mid-senior role with only two weeks of experience. Near the end, the original recruiter said I didn't get the job because an interviewer felt I didn't have a 'plan of business to address showroom challenges.' This question was never asked, and it doesn't make sense as a candidate wouldn't know the specific challenges. The recruiter promised to follow up after I mentioned this but never did. Overall, it was a bad experience.

Confirmed questions1 question
  • What makes you want to join Lucid?
Lucid logo
Lucid

Corporate Paralegal

Legal

Mid Difficult Positive experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Behavioral Technical

I had a really good time interviewing with Lucid. The Senior Talent Acquisition associate contacted me about 2 weeks after I applied online. The interviews included a 45-min phone call with the associate, which had some technical questions, followed by two 30-min interviews in the second round, and then two more 30-min interviews in the final round. They were nice enough to speed things up for me since I was interviewing elsewhere too. I couldn't have had a better experience. Everyone I met was nice and seemed like they would be great coworkers. I was offered the job the same day over the phone after my last interview. They offered competitive pay, good benefits, and great learning programs, but I unfortunately got a better offer and had to take it.

Confirmed questions3 questions
  • Tell me about your strengths.
  • What makes you want to work at Lucid?
  • Could you go over your resume and background?

Lucid Interview Questions

Quoted word for word from Lucid interview reports.

What's the reason behind not using dynamic memory allocation in embedded systems?

Read reports

Why is dynamic memory allocation used in general OS but not typically in RTOS?

Read reports

Can you explain CAN communication and how a CAN node detects arbitration loss?

Read reports

Could you draw a UML diagram for your favorite board game?

Read report

Could you describe LIN communication and the roles of master and slave devices?

Read report

How many petrol pumps did you see on your way to the office?

Read report

Formats, difficulty and experience

Across all 56 Lucid interview reports.

Interview formats

Behavioral 41.4%
Technical 35.1%
Coding 8.1%
Presentation 5.4%
Other 4.5%

Interview difficulty

Easy 25%
Average 58.9%
Difficult 16.1%

Candidate experience

Positive 55.4%
Neutral 14.3%
Negative 30.4%

Reports by job function

Engineering 14
Sales 11
Analytics 10
Operations 8
HR 3
Other 3