
Lovevery Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Lovevery.
Software Engineer
This company was specifically looking for Ruby developers. The technical discussions focused heavily on RoR, including topics like migrating from monoliths to microservices, architectural decisions, and design choices. The recruiter who contacted me was helpful in preparing me for these discussions. I wasn't asked to do any live coding; instead, there was a take-home assignment. While it was quite challenging and took a lot of time, it was a well-designed exercise that we later used as a basis for our conversations. The entire process, from start to finish, was remarkably fast, and they were very respectful of my other commitments and managed expectations well throughout. Although I didn't complete the final stages because I accepted another job offer, I have a great deal of respect for how efficiently they ran their hiring process.
- Given this problem, how would you approach fixing it?
- Could you discuss your thoughts on class libraries?
- What are your thoughts on GraphQL?
Software Engineer
The interview process involved a screening, followed by an interview with the hiring manager. Then there was a coding homework assignment. After that, I had four interviews covering both technical and non-technical aspects. The final stage was a live coding exercise. I didn't get an offer, and the feedback was that I lacked the technical skills they needed, specifically in implementation. I did complete the skills assessment without any issues. It seems the live coding exercise was the deciding factor, especially since the 'final interview' was described as 'light technical,' which wasn't accurate. Live coding interviews can disadvantage certain groups due to performance anxiety and aren't representative of typical work environments. It's also unclear what the benefit was of the coding assessment being a surprise; transparency would be better. The other interviews were standard and went well, and they were good at communicating next steps.
- Can you describe your technical background?
Software Engineer
The whole interview process, from the first chat with the recruiters to the last interview, felt really welcoming, like Lovevery was a place I'd fit right in. Everyone was respectful and treated me like a person. It was more of a conversation than just an evaluation, and I felt welcomed. A notable moment was right before my final interview with the VP; I lost power at home. I let them know immediately, and they were totally understanding. Luckily, the power came back on, and we could do the interview. Their flexibility showed me the company culture firsthand. It's not often you feel so supported as a candidate, but Lovevery made me feel seen throughout the entire experience.
- Can you demonstrate your approach to solving an algorithmic problem using TDD, emphasizing your testing, naming, and problem-solving strategies?
- Could you walk us through your previous work experiences?
- How do you approach collaboration within a team?
Lovevery Software Engineer Interview Questions
Quoted word for word from Lovevery interview reports.
“What are your thoughts on GraphQL?”
Read reports →“Could you design APIs for a comments posting feature?”
Read reports →“Could you discuss your thoughts on class libraries?”
Read reports →“How do you collaborate and communicate effectively with a Designer?”
Read reports →“Do you have any questions related to SQL?”
Read report →“Were there any business transactions you handled using Boomi?”
Read report →“What are your thoughts on system design principles and practices?”
Read report →“Did you work with Netsuite for business transactions?”
Read report →“Given this problem, how would you approach fixing it?”
Read report →Formats, difficulty and experience
Across all 9 Lovevery interview reports.