Goal

This interview is a conversation about your work, your thinking, and your technical skills. We designed it to be low-effort to prepare because we will understand you much better talking about actual work than taking apart an assignment. Don't build anything new or spend days getting ready but bring something you already know well.

Interview structure [60 minutes]

• Introduction & general questions [10 minutes]
• Conversation about a project you brought [25 minutes]
• More about the role & Kombo [15 minutes]
• Questions from you and next steps [10 minutes]

Preparation

Pick one project that you worked on and that you're proud of. You'll have 5 minutes to introduce it to us, then we'll spend 20 minutes on a conversation about it.

We see the best projects to be from work, or hobby projects that made it into production and got real usage. Vibe-coded/CRUD apps for small problems usually don’t work well for this interview.

A few things to keep in mind:

• (Ideally) Have the codebase accessible so you can share your screen and show us code.
• You should know this project well enough that we can have a real conversation about it. Why you built it, what you decided along the way, what the hard parts were.
• It should be something with enough substance that we can go deep. A weekend CRUD app won't give us much to talk about.

If you really feel like you won’t be able to show anything, please reach out to us.

Further steps

After the interview, we will decide within the next 1-2 days if we will move forward. The last step is usually the on-site. For the on-site, you will come into our office for one day and work with us on a real project from our real codebase. The day is compensated, we hope that makes it easier if you have to take a holiday.

More about Kombo