Locus Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Locus.
Locus
Software Engineer
Senior Average Negative experience Accept offer 4 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Coding Technical System Design Behavioral
I did one coding round, then a take home LLD, followed by a HLD interview, and finally a culture fit part. Be warned, they are not honest about the culture or benefits. They claim unlimited leave but my leaves were never approved and I always had to beg. The HR and recruitment people definitely lie to get you to join, so stay away.
Confirmed questions4 questions
- Can you design a Low-Level Design for a Google Maps-like application?
- Tell me about your cultural fit.
- What are the benefits?
Locus
Software Engineer, Backend
Entry Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Onsite Presentation
Interview formats
Coding Technical Presentation
Applied online and got a response in 24 hours. First, had to complete a Role Based Auth system task within 24 hours. Moved on to the next round, which was a telephonic interview the following week with quick feedback. The final round was at their office. A task was given that involved research, design, and implementation, with ample time provided. Got stuck on some parts and couldn't finish it. Received detailed feedback on the entire performance, highlighting areas for improvement, which was appreciated. Wasn't selected but found it a valuable learning experience.
Confirmed questions2 questions
- Can you design an in-memory role-based authentication system?
- Design and implement a system after researching it.
Locus
Software Development Engineer
Mid Average Positive experience Accept offer 3 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Technical Coding System Design Behavioral
First, there was an assignment to complete in 1 day about consuming an API. They usually provide feedback within a week. Next, I had a System Design round that lasted over 2 hours, focusing on the low-level design of components. I might have had to write pseudocode for some components. We also discussed the approaches I took for the assignment. Finally, I had a discussion with the hiring manager, which included some technical parts.
Confirmed questions2 questions
- Can you design a backend system that exposes REST endpoints, ensuring the data is paged?
- How would you design a cache that uses a time-based eviction policy?
Locus Software Engineer Interview Questions
Quoted word for word from Locus interview reports.
“Could you explain why using the index as a list key in React is generally not recommended?”
Read reports →“What are the fundamental concepts of databases?”
Read reports →“How would you design a cache that uses a time-based eviction policy?”
Read reports →“How does the unlimited leave policy work?”
Read reports →“What can be said about this?”
Read report →“What are some ReactJs concepts?”
Read report →“Can you design an in-memory role-based authentication system?”
Read report →“Can you design a Low-Level Design for a Google Maps-like application?”
Read report →“Design and implement a system after researching it.”
Read report →Formats, difficulty and experience
Across all 11 Locus interview reports.