Lendbuzz Interview Questions
& Process

So I had 4 interviews in total, and 3 of them were basically testing the same thing. Classic startup move. The first was with the recruiter, which was standard. We chatted about my background, if I knew about the company, and why I was interested. The second interview was also pretty standard: a technical interview with a medium Leetcode problem and some SQL questions. Then they set up a third interview. The recruiter told me it would be about ML concepts and probability, but it turned out to be another python coding test. After that, they scheduled a fourth interview, saying it would be about analytical concepts. Surprise! It was actually a third python coding test. They never actually tested my ML knowledge, which makes sense because it seemed like a Data Analyst role pretending to be an ML Engineer role, and the pay was pretty bad for an 8-month commitment. Doesn't seem like they offer return positions either. This whole process was a major time sink during my midterms because I prepped for what they said they'd test, but they kept throwing curveballs. Honestly, I wouldn't have taken the job even if they offered it because I saw too many red flags with the team and the company. Watch out for startups, they tend to be like this!

First, you'll likely have a phone or video chat with a recruiter. They'll go over your background, why you're interested in this job, and if you're a good match. They might ask about your past work, what you want in your career, and if your salary and timing expectations fit what they're offering. For technical jobs, you'll probably have to do a coding test, a case study, or some kind of technical check to show what you can do. This usually means solving problems with data structures, algorithms, or general problem-solving, often on sites like HackerRank or CodeSignal.

The interview process started with a call with HR, which was okay, but they wanted to schedule the next steps quickly. Then there was a Tech Screen with the Backend Lead, which seemed alright. It involved 3 questions: an easy one about merging strings by alternating them, an SQL question easily solved with JOINS and GroupBY, and a coding question about calculating the active monthly price for subscriptions. After that, I had an interview with the Director. He was a few minutes late and asked if I had time after the interview to work on a System Design question together, getting annoyed when I said I had other commitments. He had poor time management, spending 45 minutes of the hour discussing my background and then rushing a System Design problem in the last 15 minutes, arguing about design choices. I was told by the recruiter it would be a behavioral round, so the System Design part was unexpected. It felt like the company doesn't value time, with late interviewers and unexpected calls. The Director's interview was a major red flag; he seemed to talk a big game despite limited experience and lacking basic database knowledge. Overall, it felt like a waste of time and energy.

HR call first, then Director Phone Interview, then Technical interview. The HR part was good at the start. First phone interview wasn't that professional, felt like they were avoiding questions. Technical interview was okay, asked some background questions and a Leetcode problem. The architecture guy seemed serious. They never replied about why I didn't move forward even though I asked, which felt unprofessional, especially for this type of role. The experience questions were also not great, jumping between topics instead of focusing on one or two, and not letting me finish my thoughts. Overall, the process could have been more professional for a company of this size.