I was initially approached by the HR person at the company on LinkedIn regarding the role.
The process then went as follows:
The process itself was quite quick, as I managed to get through it in less than 2 weeks, and could schedule more than one interview in the same day.
After a couple of working days, I was told they went for a different candidate.
The interview process was overall nice - people were great, friendly, and quite responsive to email communication.
Couple of sour points:
The tech interviews were essentially reading off of a script of pre-made questions; this is not bad per-se, but it partially killed the vibe of the discussion during the interviews. There are many better ways to segway between different questions seamlessly, rather than a meagre "ok - next question";
After the rejection email - which specified that the interviewers too had a positive experience with my process - I was essentially ghosted by the HR person when asked for any sort of feedback. This significantly lowered my appreciation for the company and the process, from a positive experience to overall neutral.
What is the difference between strong and eventual consistency? How does eventual consistency affect the design of your architecture?
Can you explain what a CDN is?
How do you personally tell when a piece of code is "tested enough"?
What are your takes on monolith vs. microservice architecture?
The following metrics were computed from 1 interview experience for the Framer Senior Backend Engineer role in Tunisia.
Framer's interview process for their Senior Backend Engineer roles in Tunisia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Framer's Senior Backend Engineer interview process in Tunisia.