<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> This was heavily inspired by what Theo describes in this video and the document he sent to Dan Abramov to prepare their mock interview.
</aside>
Hello dear candidate,
Congratulations on making it to our technical interview!
At Memory, we want to make sure our interview process is optimised towards helping you to succeed. We expect different candidates to have different methods that best showcase their strengths.
An important note: we do not evaluate the same skillsets depending on the seniority levels.
To illustrate that, a junior will be juged on their ability to understand what’s being asked and to implement it while respecting the constraints.
A senior on the other hand, will be juged on their ability to understand the problem behind what’s being asked, their ability to design multiple solutions and think short / mid / long term.
A lead or architect, on their side, will be asked to prioritize things like ease of understanding / maintenance / use.
During the interview, that may lead us to derive from pure coding to discussing design and architecture or have you drawing some schemas to make it clear for us what solution you’re thinking about.
With that in mind, we've introduced 3 different paths for our technical interviews. Please read these ahead of your interview and let us know what path you'd like to take!