
Lucidworks Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 41 interview experiences · FREE TO READ
Which role are you interviewing for?
17 roles · 41 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Lucidworks.
Analyst
Lucidworks gave me a good interview experience overall. It had 5 interviews, each about 30-45 min. The recruiter was nice and told me what the job would be like. It was cool to meet different people on the team. The process felt fair, didn't take too much time, and the questions were relevant and thoughtful. Mostly behavioral interviews, with one case study in the 4th round. Pretty standard.
- Can you describe a situation where you worked with a dataset that had missing or inconsistent data, and explain how you addressed it?
Devops Engineer
The interview process was smooth and well-structured. It started with an initial HR screening, followed by a technical round where I was asked relevant questions based on my experience. The interviewer was friendly and gave me enough time to explain my thought process. The final round focused more on team fit and project discussions. Overall, it was a positive experience and the communication throughout was clear and timely.
- Were you comfortable with 1-week on-call rotations?
Senior Software Engineer
I interviewed with Lucidworks, and it was a really good experience. The process was straightforward. It started with an intro chat with HR, then a meeting with the hiring manager. After that, there were four more rounds, each half an hour long with different people. It was fast but thorough. They covered a lot without taking too much time. The people were nice too, which made it a pleasant experience. They seem to really value efficiency and professionalism.
- Can you explain what you know about DDD design?
- What's your understanding of Spring Security?
Software Engineer
It was a bloated and unnecessarily complex interview process. Started with an HR call, then a hiring manager call, and then two more calls after that. All calls went great and I got excellent feedback. I was told I'd move to the final step by Tuesday at the latest. Tuesday, Wednesday, and Thursday passed with no response. After I tried to reach the hiring manager, HR sent a generic rejection email with different font types in each paragraph, saying they 'appreciate' my efforts.
- Can you tell me about the tech stacks you use?
- What do you know about what we do here at Lucidworks?
Lucidworks Interview Questions
Quoted word for word from Lucidworks interview reports.
“Could you explain what a daemonset is in Kubernetes?”
Read reports →“How would you compare the similarity between two IP addresses?”
Read reports →“Could you write the code for a search engine?”
Read reports →“Could you explain what ingress is?”
Read reports →“Could you explain networking concepts like switches, hubs, and DNS, and how DNS functions?”
Read report →“Could you describe the technical components of Apache Solr?”
Read report →“Can you explain what ERP is and its functions?”
Read report →“What's your understanding of Spring Security?”
Read report →“Can you tell me about a Bash command related question?”
Read report →Formats, difficulty and experience
Across all 41 Lucidworks interview reports.