Lendio logo

Lendio 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

3.3 Rounds average
Average Typical difficulty
77.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Lendio.

Showing 3 of 9
Lendio logo
Lendio

Software Developer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The interview process at Lendio was very smooth. They seemed to care about culture as much as technical ability. I felt like I could relate with their "Humble & Hungry" mantra, and the interview process gave me a full transparency view into the company. I came away from my first interview knowing my standing, what to expect, the values of the company, and pretty much anything else I would have cared to know. The rest of the interviews solidified my first impressions about the culture of the company, and made me genuinely believe that Lendio was committed to professional development.

Confirmed questions1 question
  • Reflecting on your career as a software developer, what's a significant lesson you've learned as you've grown professionally?
Lendio logo
Lendio

Software Engineer

Engineering

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Offer
Interview formats
Behavioral Coding

I spent a lot of time thinking about how to write about this interview experience, and honestly, I really liked most of it. The people I talked to were super friendly and made things feel pretty relaxed. What really made me want to share, though, was how things ended – it felt kinda confusing and didn't really match up with what you'd expect from a company that calls itself a 'top workplace'. Right after I applied, I got an email to hop on a Zoom call with someone from Lendio. It was pretty chill, mostly just getting to know each other stuff. Then, they set up a call for the next week with the head of the Technical department. That call was cool too; I liked the vibe and how he let me talk about myself and what I've done. We got into their tech stack, and he mentioned Laravel. I knew of it but hadn't coded with it directly, which was fine since the job description said direct experience wasn't a must. I did mention I'd used Symfony a lot, which is pretty similar and would make picking up Laravel easier. After we finished, he said I'd hear back in a few days. But then, I got another email from him asking me to do a coding assignment by Friday at 1 PM. It was Tuesday afternoon, and since I have a full-time job, I'd only be able to work on it in the evenings. He said the point was to see if I could learn the framework, which seemed fair given I hadn't used it before. I was actually kinda excited to try out their stack. The assignment was to build a full CRUD app on the front-end and back-end using Vue and Laravel. They didn't give many instructions, just to build something I'd enjoy and that would show my skills. I managed to finish it by Thursday night and put the code on Github Friday morning before work. I didn't hear anything until the next Wednesday when I got a super generic email saying they were going with other candidates. Of course, I was bummed, but I wanted to be graceful and maybe learn something, so I replied asking if they could give me any pointers for future job searches. I never got a response. I get that they can't always give personal feedback, but it felt like, this late in the game and after asking me to use my personal time, a little bit of explanation would have been nice. It's totally fine that I didn't get the job – that happens – but it felt really cold and impersonal for a company that talks so much about having a great culture for customers and employees.

Confirmed questions6 questions
  • Can you tell me about the projects you have been involved with?
  • What are some of the technologies you have used?
  • Could you describe your experience with Symfony?
Lendio logo
Lendio

Software Engineer

Engineering

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Onsite Onsite
Interview formats
Behavioral Behavioral

Started with a recruiter screen. Then I met two engineering managers in the Lehi office for an hour-long chat. It was more of a discussion about my past projects and how I collaborated with others and tackled challenges, with no whiteboarding. The final round was with Brian Hosie, the head of Engineering. We had a good conversation about Lendio, the importance of culture, and my potential role. No whiteboarding here either, as they prioritize cultural fit and ensuring good team dynamics over technical skills, even if you haven't used their specific tech stack.

Confirmed questions4 questions
  • Can you share an instance where you dealt with a conflict among team members?
  • Could you elaborate on the projects you've worked on?
  • Describe your experience with projects you've undertaken.

Lendio Software Engineer Interview Questions

Quoted word for word from Lendio interview reports.

How would you approach learning a new framework like Laravel?

Read reports

What are the most crucial qualities you seek in a potential employer?

Read report

Tell me about your experience with test-driven development.

Read report

Reflecting on your career as a software developer, what's a significant lesson you've learned as you've grown professionally?

Read report

Formats, difficulty and experience

Across all 9 Lendio interview reports.

Interview formats

Behavioral 66.7%
Technical 27.8%
Coding 5.6%

Interview difficulty

Easy 22.2%
Average 66.7%
Difficult 11.1%

Candidate experience

Positive 77.8%
Neutral 22.2%