
Luciq Backend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 22 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Luciq.
Backend Software Engineer Intern
So, first you apply by sending in your CV and filling out a form. Then there's an online assignment, which usually includes a coding task and some multiple-choice questions. After that, you have an HR interview where they ask about your motivation and if you'd be a good fit for the company culture. Finally, there's a technical interview with the engineers, where they'll hit you with problem-solving, system design, or coding questions.
- Questions about database indexing were asked.
- Can you explain the concepts around DB indexing?
- What are the different ways to index a database?
Backend Engineer
I interviewed at Instabug, and the whole thing took about 2 weeks. It started with the HR calling me, then I got a technical task that I had 7 days to complete. The task wasn't too hard but you really needed to know your stuff about databases, concurrency, message queues, ElasticSearch, and a few different languages. After submitting the task, HR set up another call, which was a HR interview. It was pretty chill, and everyone was really nice. The next step was a technical interview that had two parts: a medium-level problem-solving question, and then a design question where we talked about how to solve a backend problem, kinda similar to the task.
- Can you tell me about yourself?
- Why would you choose backend development over frontend?
- What salary are you looking for?
Backend Engineer
I started with an HR chat, then got a technical assignment via email with a week to complete it. Next, I had a technical chat with a senior engineer about the task, where I was asked some algorithms and a design question. Then, I interviewed with the VP of Engineering, which was mainly a general discussion with a few design questions about their current challenges. The final interview was a casual chat with the CTO, with no real questions. The people there are nice, and the office seems great. However, the interviews were spread over two months due to HR delays, making scheduling difficult. The CTO apologized for the delays and said they usually group interviews. He also promised quick feedback, but I still haven't received official communication, even after three months. I only found out I wasn't selected through a friend, which is frustrating given the time invested.
- Asked algorithms and design questions.
- Asked a couple of design questions related to problems they're trying to solve.
Luciq Backend Engineer Interview Questions
Quoted word for word from Luciq interview reports.
“What are the reasons against indexing every column in an SQL table?”
Read reports →“When a workload is executed by multiple processes on the same CPU core, it is called _____ but if it is executed by multiple threads in the same process, it is called ______.”
Read reports →“Can you write a function that retrieves the next event ID for a given token?”
Read reports →“What are the performance impacts of using different indexes?”
Read reports →“What are the different ways to index a database?”
Read report →“Can you write a function that takes a URL and counts the frequency of different domains, and what would happen if this function were running at the same time as other processes?”
Read report →“Can you explain what a race condition is in detail?”
Read report →“How do you choose the right index for a specific situation?”
Read report →“Can you explain the concepts around DB indexing?”
Read report →Formats, difficulty and experience
Across all 22 Luciq interview reports.