Goal

Overall, the goal of this interview is for us to gain confidence that your technical skills and the technical skills required for the position are a match.

Many other companies have a technical take home challenge or coding screen at this point in their interviewing process. However, we are aware that these can be very time-intensive or stressful and thus, we have designed this interview for us to gain confidence about your technical skills in the leanest way possible. We hope the interview is a fun experience for you!

Interview structure [60 minutes]

• Introduction [5 minutes]
  • Get to know the interviewers (Aike and someone from the engineering team)
  • Overview of the interview structure
• General questions [10-15 minutes]
• Code walkthrough and questions [30-40 minutes]
• Questions from you and next steps [5-10 minutes]

Preparation

General questions

You don’t need to prepare anything for the general questions; we will just ask you some general things about your background as a software engineer.

Code walkthrough

You need to prepare for the code walkthrough and should do so by considering a few things. The project and code you are showing us..

• should represent your skills, especially those we are looking for, as well as possible.
• can be anything from work, a solo hobby project, or something you did with a friend.
• should be complex or large enough that we can discuss architectural tradeoffs or interesting product decisions you took (simple CRUD apps usually don’t work as well for this)
• if other people contributed to this project too, you can show which parts you owned and built.
• ideally showcases how you write code that you consider “good quality.”