Lovable Product Engineer Interview Experience
Lovable · Software Engineer
At Lovable, what I thought was a recruiter call suddenly became an on the spot TypeScript coding test. He shared his screen, pointed at a bunch of functions, and I had to explain what would happen without even touching the code.
Interview process
I got into Lovable through a referral and only did two rounds before the process stopped. The first was a very casual chat with one of the founders, and it felt more like a conversation about AI, vision, and zero-to-one building than a formal interview. Then I had what I assumed was a recruiter screen, but it turned into a live TypeScript code walkthrough with an external recruiter and I had not been told that in advance. I did solve the exercise, but I was very upfront that I'm not an expert in TypeScript. After that I got a generic rejection, and my read was that they specifically needed someone very strong in that stack.
Interview rounds · 2
- 1
Phone screen
BehavioralArtificial IntelligenceProject DiscussionI first had a very casual, very friendly chat with one of the founders. It felt more like a genuine conversation about why they're building this, what AI could make possible, and whether I had real zero-to-one experience than a hard screen. I also felt like they were selling me a bit on how fast and crazy everything was.
Q1. Tell me about your background and what you've built from zero to one.
How they answeredI talked about having founding experience and that I've been in situations where nobody else was going to ship the feature for me, so I had to do the whole thing and make sure it was right. My angle was that I can operate in messy zero-to-one work, not just hand off specs or stay in one lane. I got the sense that part landed well with them.
Q2. What are you interested in around AI, and what questions do you have about our vision?
How they answeredWe mostly talked about what I was interested in and the possibilities with AI. I asked them about their vision, what challenges they thought were coming, and how far they thought this could really go. It didn't feel competitive at all. It felt like a real conversation about interest and direction, and a bit like they were trying to hype me on how fast they were building.
Follow-up questions- What do you think our challenges are going to be?
- How far do you think this can go?
- 2
Technical round
TechnicalCodingConceptWhat I thought was a recruiter call turned into an on-the-spot coding screen with an external recruiter. He was pretty cold and poker-faced, and there was no heads-up that I'd be tested live in TypeScript. The exercise itself was basic code-to-meaning, but the surprise and their obvious need for a TypeScript expert made the round feel much harsher than it needed to be.
Q1. Walk me through what this TypeScript code will do.
How they answeredHe shared his screen and showed me one function calling another and another, and I had to explain what would happen. I talked through it step by step, saying if this is true then this happens, and so on. It was basically a for-loop-type flow checking a boolean and storing a variable. I solved the puzzle, but I was upfront that I wasn't sure about some TypeScript-specific behavior, especially something that looked singleton-like. I can code in other languages, but I was clearly not a TypeScript expert.
Follow-up questions- What happens when this function calls the next one?
- What does this boolean check do?
- What is this stored variable doing?
Tips from the candidate
I'd go in assuming this role is much more engineering-heavy than the title makes it sound. I'd also clarify the exact format of every round ahead of time, because in my case the so-called recruiter call was actually a live coding screen in TypeScript with no warning. If you're not already very comfortable reading and explaining TypeScript on the fly, I'd either prep that specifically or call it out early. For the founder chat, I'd lean hard into zero-to-one stories and why you like building in ambiguous environments, because that seemed to resonate much more than polished strategy talk.
Company culture
My read is that they're hiring like a very fast-moving AI startup that cares first about execution. The founder conversation was friendly and vision-heavy, but the actual filter felt like 'can this person just get it done, fast, in our stack.' They seemed to use an external recruiter for screening, which was unusual, and the process felt a bit scrappy because the technical part wasn't clearly signposted. I also got the strong impression they want people who are willing to put in a lot of energy and hours. More broadly, this matched what I've seen this year where companies say they want product or design hybrids, but in practice they really want someone who's 80% or more builder.