Lovevery logo

Lovevery Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 35 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
48.6% Positive experience

Which role are you interviewing for?

13 roles · 35 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Lovevery.

Showing 4 of 35
Lovevery logo
Lovevery

Data Engineer

Engineering · a year ago

Senior Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Offer
Interview formats
Technical Coding

I spoke with HR on Tuesday and was really impressed. They wanted to move quickly. The next day, I had a technical interview and a test that I finished by Sunday. Then, we had three meetings at the start of next week, and by the end of that week, I got the offer. The whole thing was fast, organized, and respectful. The test was fun and challenging, letting me show my Data Engineer skills. Everyone I met was nice and asked good questions to assess my profile.

Confirmed questions4 questions
  • Can you discuss interesting projects from your past, particularly your most recent role?
  • Let's dive into PySpark, specifically regarding shuffle issues.
  • Tell me about your experience with AWS and Terraform.
Lovevery logo
Lovevery

Influencer Marketing Specialist

Marketing · a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

I was reached out to on LinkedIn by the company's talent lead, J, who thought I'd be a great fit. I did an interview with her, and then got invited to interview with A, the director of partnerships. They told me I'd move on to meet the influencer marketing team and a co-founder. I emailed the recruiter to get A's contact info to send a thank you, but she took four days to reply. She then told me A didn't think my experience was strong enough and they were moving forward with other candidates. This was disappointing as it came within a week of a holiday, and after I was told I was advancing. The role remained unfilled two months later. Getting honest and timely feedback would have made this a better experience. The interview was pretty standard, but the interviewers seemed a bit unseasoned, so the first 10-15 minutes felt like just warming up, making the interviews run over time.

Confirmed questions1 question
  • What motivates your interest in joining Lovevery?
Lovevery logo
Lovevery

Video Producer

Marketing · more than a year ago

Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

Had a Zoom screening with HR (15-20 mins) followed by a brief interview with the Team Lead (20 mins). Then, there was a more operational and detailed interview with the Team Lead. IMPORTANTLY, halfway through the interview process, the role changed from temporary to full-time. I wasn't told by HR, and during my 3rd interview with the head of the team, I found out about the change. This made me look unprepared. The interviewer was surprised I hadn't been notified, asked if this news affected my salary requirements, and wanted an estimate right away. After that, the HR person I was originally talking to didn't reply until I got a rejection email.

Confirmed questions1 question
  • What motivated you to apply to Lovevery?
Lovevery logo
Lovevery

Software Engineer

Engineering · more than a year ago

Senior Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding

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.

Confirmed questions4 questions
  • Given this problem, how would you approach fixing it?
  • Could you discuss your thoughts on class libraries?
  • What are your thoughts on GraphQL?

Lovevery Interview Questions

Quoted word for word from Lovevery interview reports.

Formats, difficulty and experience

Across all 35 Lovevery interview reports.

Interview formats

Behavioral 43.6%
Technical 32.1%
Coding 7.7%
Other 6.4%
Presentation 6.4%

Interview difficulty

Easy 8.6%
Average 77.1%
Difficult 14.3%

Candidate experience

Neutral 25.7%
Negative 25.7%
Positive 48.6%

Reports by job function

Marketing 13
Engineering 12
Design 4
Operations 3
Other 2
Product 1