Lucid Software logo

Lucid Software Qa Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Lucid Software.

Showing 3 of 15
Lucid Software logo
Lucid Software

QA Specialist

Engineering · more than a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Other

This was an awful experience. I've gone through the questionnaire and prepped for it, using my own time, three times now. Then, they told me they can't hire in my state because they aren't set up to do business there. They asked if I would consider relocating. This is extremely unprofessional. Why waste so much time if location is an issue? They should have checked this first. I applied because the job said US-eligible, with no info on ineligible states. Stop wasting people's time and check eligibility beforehand.

Confirmed questions2 questions
  • Questions asked in a questionnaire to test creativity and use cases.
  • Logic questions to test creativity and use cases.
Lucid Software logo
Lucid Software

QA Specialist

Engineering · more than a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Group
Interview formats
Behavioral Technical Group

I first talked with some managers who wanted to see how I explained technical processes and my approach to testing stuff. After that, I had a couple of group interviews with the team, and we talked about things like how I disagree with people, how I manage multiple projects, and so on.

Confirmed questions1 question
  • Can you share an instance where you had a disagreement with a manager?
Lucid Software logo
Lucid Software

Quality Assurance Engineer

Engineering

Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Take home Onsite
Interview formats
Behavioral Technical Coding

The interview process was pretty standard. It started with a recruiter phone screen, mainly confirming I was a normal person and didn't lie on my resume. Then, there was a take-home written exercise asking conceptual questions about how I'd test real-world items like a jacket. The final round involved panel interviews with team members and the team lead/director, including live debugging of their product. I was told I didn't catch all testable items in the exercise with the team lead and didn't get an offer.

Confirmed questions1 question
  • How would you test a jacket?

Lucid Software Qa Engineer Interview Questions

Quoted word for word from Lucid Software interview reports.

Is it acceptable for the bottle to have a hole? Explain why.

Read reports

Can you think of any unconventional uses for a kitchen knife?

Read reports

Formats, difficulty and experience

Across all 15 Lucid Software interview reports.

Interview formats

Technical 40%
Behavioral 40%
Other 11.4%
Coding 2.9%
Presentation 2.9%

Interview difficulty

Easy 26.7%
Average 60%
Difficult 13.3%

Candidate experience

Neutral 26.7%
Negative 33.3%
Positive 40%