Framer interview questions

The process started off really well. The first couple of steps were smooth and positive. The interviewers were friendly, well-spoken, and the conversations flowed naturally. That changed dramatically in the third step. From the moment the call began, red flags appeared. The interviewers looked bored and disengaged, almost as if they’d been pulled into the call last-minute or woken from a nap. They seemed completely unprepared, asked no meaningful follow-ups, and stuck rigidly to a script of predefined questions. It was clear they were only interested in very specific answers that matched their checklist, rather than engaging in a real conversation or assessing broader potential. I find it disappointing that a company like Framer, which prides itself on craft and user experience, doesn’t put more care into its hiring process. Poorly trained interviewers don’t just miss out on good candidates, they also leave a lasting negative impression of the company. In the end, I was told I lacked the required technical skills for the role. Fair enough. But after that train wreck of an interview, I wouldn't have wanted the job anyway.

I went through several stages of the interview process. The first stage was an HR interview, where we discussed my current role, salary, and position expectations, as well as questions about the team and the company. The second stage was a coding interview, which involved solving a simple algorithm problem that gradually increased in complexity. The third stage was a technical interview focused on fundamental questions about React and TypeScript. I feel I didn’t perform as well as I could have during this stage, and ultimately, the company decided not to move forward. In general, I found the overall process to be very well organized. Communication was clear and professional throughout all stages, and the experience was generally positive despite the outcome.