highlevel Interview Questions
& Process

The interview process was quite lengthy, spanning about a month. It began with a technical screen focusing on Javascript, rated as easy to moderate. This was followed by a take-home assignment that took a couple of days to complete. Then, there was a round reviewing Javascript, React, and the assignment. The fourth round was with the hiring manager. The fifth round again involved Javascript, React, and Vuejs. Finally, there was a sixth round, another hiring manager discussion, but this time focused solely on AI. After this, there was no response from HR, and I didn't receive any calls. It's frustrating when HR doesn't provide any feedback after such a long process, especially if the vacancy is uncertain. Why waste candidates' time?

I interviewed with HighLevel for the Lead Tableau Developer role and it was a really bad experience. It kicked off on January 21, 2026, and had four rounds, which included a technical assignment - kinda surprising given the role needed 9+ years of experience. I did all stages professionally and got good feedback from the first three. The last round was a cultural fit chat with the Head of HR on March 2, 2026, and that went fine. But after that, they just went silent. I reached out to my HR contact multiple times via LinkedIn, email, and phone, but nothing. No rejection, no feedback, no closure after almost six weeks of going through their process. To top it off, I saw the same job reposted on LinkedIn, which makes me wonder about how honest and respectful they are to candidates who put in a lot of time. The hiring process really shows a company's culture, and HighLevel's lack of communication, long waits between stages, and total silence after the final interview show they don't respect candidates' time and effort. I really hope they get better at recruiting and at least let candidates know where they stand after multiple rounds. Advice to Management: Talk to candidates more and give updates on time. Ghosting people after assignments and multiple interviews ruins the company's reputation and trust.

The process was pretty standard with three rounds. The first round focused on your past work experience and how well you understand a recent product, and it had 3-4 interviewers. The second round involved discussing projects, and you got to choose which ones. This also had a panel of 3-4 people, and in my case, it was the same folks as the first round. I think the third round was an assignment with a presentation. The second round was a bit tough for me because the interviewers were very solution-focused. During a product improvement case study, one asked why a solution wasn't built earlier. For an insurance-tech case study focused on customers, some interviewers were more concerned about the insurance companies, which made me question their customer empathy. Another case study I presented was about first-day uninstalls, but surprisingly, they focused on an unrelated metric with many variables. It seems like you have to align with their project management and solution preferences. If you approach things with a customer and problem-first mindset, you'll likely run into ego issues. A tip: Ask the TA for a good mix of product people and to include a senior person for the role you're applying for. If you're genuinely interested in solving problems, this might not be the company, at least based on my interview.

You start with an initial screening which is a 30-45 min chat with a recruiter or HR. They'll ask about your background, experience, what you're doing now, and where you want to go in your career. They'll also give you the lowdown on the company, the role, and what they're looking for. Expect some basic questions about leading teams, if you know the tech stack, and about projects you've done. Then there's a technical interview that's 60-90 mins with some senior engineers or other engineering managers. This part has two chunks: System Design, where you'll need to design a scalable system for a problem they give you, talking about microservices, databases, caching, and scaling. And then a Coding Challenge, where you'll solve algorithmic or real-world coding problems, so bring your A-game with data structures, algorithms, and problem-solving.