I applied online. The process took 4 weeks.
I had a great feeling with all the people I met during this process. Pennylane is made up of kind people. You can sense a drive for efficiency during the interviews (fairly condensed, highly structured formats that focus on the essentials). The process starts with a screening interview. I then received a homework assignment to complete within a week, with AI tools allowed on the condition that I described the methodology used. I had a technical debrief with a software engineer, where I had to explain my code in detail with some probing questions on certain technical and architectural choices. I had a 15-minute feedback call with the recruiter a few days later. Next was an interview with a PM, followed by another debrief. In my case, the process stopped after that. My feedback is therefore very positive, but I would suggest two improvements: 1 - have multiple interviewers during the interview to limit bias. 2 - if possible, swap the homework and the Product interview: as a candidate, you spend many more hours on the homework. Given the time investment required for the homework, I would have preferred to fail early 😉. Otherwise, it was perfect!
What is the complexity of this algorithm? What is its impact on memory if the input grows? How could you have done things differently to limit the performance impact?
The following metrics were computed from 15 interview experiences for the Pennylane Engineering Manager role.
Pennylane's interview process for their Engineering Manager roles is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Pennylane's Engineering Manager interview process.