Lucid Software Interview Questions

Based on what I heard from others that are familiar with Lucid Software, there is a high attrition rate at the company. If true, I'm not sure what the specific reason(s) are but the conversation I had with a recruiter in the initial round made it clear they didn't have anything concrete for the job I was interviewing for. They were not able to provide a targeted start date, a budget for the salary, or any specifics about the team or the need they were looking to fill. It was apparent that they were just collecting potential candidates for a future need. While this may be normal practice, it's a red flag since they not only lack transparency but they take advantage of candidates' time by making it appear there is an actual role to be filled rather than being upfront.

OA: multiple algorithm questions 1h VO: design and implement several interfaces of a mini game based on source codes 1h + 1h back-to-back final round VO: algorithm questions, bahavioral questions and OOD desion

I applied online with a referral then HR reached out to me. Then they scheduled an interview and did the first round. However, HR ghosted me in the meantime. Later, he apologized for doing so, as he was busy with some deadlines.

In the first round, a basic problem statement is given which you have to solve in an hr. After that an interviewer will come and make you run the code against some test cases. Some more DSA questions

Pretty standard process. With increasing difficulty each step. The steps are the following: - Phone screen with recruiter - Interview with Manager - Interview with VP - Demo Generally it was a positive experience.

1st portion was a questionnaire 2nd portion was a phone screening with a member of their talent team I was told the 3rd and 4th rounds were to be interviews with the QA team, etc.

The recruiter calls to give you a run down of the interview process. This is where you can ask clarifying questions about what to expect and how to prepare. The next step is completing a coding challenge within 10 days of receiving the challenge. No time limit. The next round is a one hour coding challenge with a software engineer. There are three challenges. After the hour is up, the engineer will ask you to walk them through your code and will ask how you would change your code with requirement changes. The first two challenges were easy. The last one took some understanding. My mistake, I spent too much time reading through the code. Instead, have the engineer remind you where the code you are concerned with starts. If needed have the engineer remind you what the rest of the code does. This was as far as I made it. It was my first interview in the industry.

I interviewed through to the 2nd stage - portfolio presentation. I declined to go further. I was uninspired by the interviewers and their perspective, and how inside the box they where, but I declined because I didn't get any sense they had any DEI or gender awareness. I sensed there are likely gender issues at the company based on my interview.

Two rounds over zoom. The first being a 1.5 hour coding exercise. The second consisting of two 1 hour sub-sections. The first of which covering algorithms, the second on class modeling.

Hardcore questions, it is like leetcode difficult and they developed their own questions. There is a online assembly before you get the on-site interview. People are pretty nice, should expect a long interview.