LendingTree logo

LendingTree Interview Questions
& Process

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

Based on 66 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
51.5% Positive experience

Which role are you interviewing for?

30 roles · 66 reports

Candidate interview experiences

First-hand accounts from people who interviewed at LendingTree.

Showing 4 of 66
LendingTree logo
LendingTree

Software Engineer

Engineering · half a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral

I had an initial chat with a recruiter, then an interview with the hiring manager. It felt like the hiring manager interview went pretty well, but after that, the recruiter went silent. I even sent an email to follow up on my application status, but got no reply.

Confirmed questions1 question
  • Can you tell me about your past experience as shown on your resume?
LendingTree logo
LendingTree

Product Owner

Product · a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Behavioral Technical

The interview process was really long, and even after they said I did well, they ghosted me. They took ages to respond to anything. The hiring manager seemed totally checked out. They said they needed someone right away but then wouldn't even reply to my emails.

Confirmed questions3 questions
  • What do you know about Agile principles?
  • Can you share some behavioral questions about your experience?
  • How do you assess cultural fit for a role?
LendingTree logo
LendingTree

Associate Product Manager

Product · more than a year ago

Entry Easy Negative experience No offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Behavioral Technical Case

I got referred by a recruiter after doing well in another product interview. Since I already did a recruiter call for a different role, I skipped that and went straight to the hiring manager. We had two 30-minute calls, the first to chat about the job and my background, and the second for my questions and more discussion. Then came the team round: four 30-minute back-to-back calls with different product people. They asked about my experience, product skills, and how I work in a team. I really liked talking to them and felt I'd be a good fit. A week after the team round, I got a verbal offer with good feedback and a promise of a written one in two days. But then, for two weeks, it was just emails saying they were 'working on it.' After that, they stopped responding. My follow-ups were ignored for another two weeks until a different recruiter finally replied. They said they were 'pausing' hiring, even though I'd finished the interviews and had a verbal offer. The job is still up on their site and others, which is wild. It feels like they don't take hiring seriously and just waste people's time. I rearranged my schedule and even took time off for their interviews. It was super disrespectful, and when they said they hoped the experience didn't leave a bad impression, I honestly just laughed.

Confirmed questions3 questions
  • In a scenario, how would you pinpoint a problem and then explain that issue and your proposed solution to your team?
  • How do you go about prioritizing different tasks or projects?
  • How do you handle communication with others when there's a disagreement?
LendingTree logo
LendingTree

Test Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral Presentation

This was pretty straightforward. The first part was a phone chat with the hiring manager where they asked some basic Java questions like about palindromes and the final keyword. I handled those fine. The interview process itself was straightforward. The first part was a technical interview where I was given two strings and had to determine if changing one character in one of them (any number of times) could make them match. The second part involved talking with manual QA managers about the testing process. Finally, I met with the hiring manager to discuss my interests and other things.

Confirmed questions2 questions
  • Given two strings, determine if one character change (potentially in multiple places) can make the strings identical.
  • Can you tell me about your interests?

LendingTree Interview Questions

Quoted word for word from LendingTree interview reports.

Given two strings, determine if one character change (potentially in multiple places) can make the strings identical.

Read reports

Given an array of objects, each with 'name', 'apr', and 'max_credit' keys, how would you sort this array in ascending order based on 'apr'?

Read reports

How would you manually determine if a given string is a palindrome?

Read reports

Can you explain the difference between DELETE and REMOVE in SQL?

Read reports

What troubleshooting steps would you take to find out why a user cannot connect to the internet?

Read report

For the same array of objects, how would you identify the objects where 'apr' falls within a specified range?

Read report

What is the correct method for sharing data between controllers or directives?

Read report

Formats, difficulty and experience

Across all 66 LendingTree interview reports.

Interview formats

Behavioral 45.5%
Technical 29.7%
Coding 9.7%
Case 6.9%
Presentation 4.1%

Interview difficulty

Easy 22.7%
Average 68.2%
Difficult 9.1%

Candidate experience

Negative 28.8%
Positive 51.5%
Neutral 19.7%

Reports by job function

Engineering 20
Marketing 14
Product 9
Sales 7
Operations 5
Analytics 4