I applied online. The process took 3 weeks.
Bottom line: I wouldn't recommend investing your time here. I was rejected primarily for not implementing features, such as search and filtering, that were never listed in the case study requirements. Candidates put significant unpaid hours into these case studies, only to be graded against criteria that were never written down.
More detail: The process had multiple rounds including a take-home case study and a debrief, and to their credit they gave feedback after each stage. But the requirements were not clearly communicated. I built exactly what the brief specified, cleanly and documented, and was then marked down for scope that was never stated. You can't read the interviewer's mind, and building unrequested features can just as easily be seen as a red flag, so there's no safe way to guess what they actually want. If unlisted features or product initiative are part of the evaluation, that should be in the brief. The people were professional and communicative, but the process itself wasted my time, and I'd expect it to waste yours.
If you had two more weeks, what would you add? How would you evaluate feature prioritisation?
The following metrics were computed from 4 interview experiences for the Pennylane Frontend Engineer role.
Pennylane's interview process for their Frontend Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Pennylane's Frontend Engineer interview process.