Lalamove Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Lalamove.
Lalamove
Software Engineer
Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding Technical
I applied for a graduate software engineer role. After an initial HR call, I was given a take-home assignment. This involved creating a command-line interface simulator for Uber, and I had the flexibility to choose the backend technology. Later, I had to discuss the technical choices I made.
Confirmed questions2 questions
- Could you build a CLI simulator for Uber with a backend of your choice?
- Can you explain the technical decisions you made for the Uber CLI simulator?
Lalamove
Software Engineer
Intern Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Recruiter call Onsite
Interview formats
Coding Behavioral Technical
There were several interview stages. It started with a coding interview. After that, an HR interview focused on personality and cultural fit. The last interview was with the team lead, covering both technical abilities and personality.
Confirmed questions3 questions
- What technical skills did you acquire during your studies?
- Can you describe your personality and cultural alignment?
- Could you discuss your overall skills, encompassing both technical and personal aspects?
Lalamove
Senior Software Engineer
Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Technical screen
Interview formats
Behavioral Technical Coding
This company is a waste of time, I interviewed at over 10 places this month and this was the most unprofessional. The first round was a 30 min HR call to go over basic info and ask about Kafka. The second round was a coding test, the problem could be found on GitHub, it was general and not related to the next stage. The third round had two engineers who kept their cameras off, they asked random questions not related to my CV or the job description, one engineer seemed unsure of what he was asking. The fourth round was with a tech manager who asked about midnight operations and on-call experience. Everything seemed fine and they said they'd give feedback in two days. The HR person disappeared after the final round.
Confirmed questions4 questions
- What is Kafka?
- Coding test problem from GitHub?
- Questions unrelated to CV and JD?
Lalamove Software Engineer Interview Questions
Quoted word for word from Lalamove interview reports.
“What is Kafka?”
Read reports →“What is a callback function?”
Read reports →“Could you build a sorter using Go?”
Read reports →“When designing microservices, what key considerations do you take into account?”
Read reports →“Could you build a CLI simulator for Uber with a backend of your choice?”
Read report →“Could you walk me through how Kafka operates?”
Read report →“If users complain about slow API performance, what steps would you take?”
Read report →“Coding test problem from GitHub?”
Read report →“Can you explain the technical decisions you made for the Uber CLI simulator?”
Read report →Formats, difficulty and experience
Across all 19 Lalamove interview reports.