At Modash we practice transparency in everthing -- and the hiring process is no different. No secrets, no surprises. Here's what you can expect from the process.

I'll start with an outline:

Outline of the interview process

This is the "TL;DR"

1. 💬 Chat with Kristiine - our Head of People
2. 💻 Coding interview (~1.5hr)
3. 🎨 System design (~1.5hr)
4. 💬 Get to know Avery - our CEO
5. Reference check (~1-2 days)
6. Offer, negotiations, paperwork.
7. 🎉 Let’s rock together!

Now, a little more detail...

Technical interviews at Modash

Say goodbye to pineapple tree sorting and Leet code-style tasks! Our interviews are all about practical challenges and real scenarios, so you can show off your skills in the most relevant way possible. 🌟

We try to mimic as closely as possible tasks as an engineer at Modash: reading, writing coding, and architecting.

This is a good chance for you to see what it’s like to work with us and for us to see what it’s like to work with you. Don’t stress out. Ask questions, think out loud. You can consider us your noob colleagues who are eager to learn. We're going to be like a 2-year-old: why, why, why.

💻 Coding interview

We’ll pick something from our old backlog and put it on your plate.

The first part is about writing code, in which you have to replicate a simple component in HTML + CSS (no JS required). The second part is all about code reading. Most of our time is spent reading code, than writing. Reading through the existing code base, searching through stack-overflow or Google. And yes you are allowed to use Google during our interview. Who doesn’t use it while programming?

📋 System design interview

Why system design interviews? You said it involves day-to-day tasks.

That’s right. From time to time, you’ll have to create technical documents. It involves breaking down requirements and creating appropriate rectangles. This means drawing high-level components and showing how they interact with each other. Imagine system design interviews as a virtual puzzle party, where you're the puzzle master. It's like building a LEGO set for your app's success!

If you do not have any preferences for diagramming tools, we recommend draw.io.

If you haven’t done architecture in a while, we recommend brushing up and checking this free part of the tutorial: Grokking Modern System Design Interview for Engineers & Managers - Learn Interactively

❓FAQ

⌛ How long is the interview process?

We're a small & agile company, and we move fast in our interview processes as well. While we work around your schedule too, the whole interview process is usually completed within a few weeks.

It’s all about finding the right person. We'll start interviewing as soon as the right person reaches us. We don't wait weeks collecting applications before responding.

🧠 How can I prepare for technical interviews?

Regardless of whether it’s a technical interview or not, prepare by getting to know more about the company and the people who are interviewing. Think of the questions you want to ask from them.

Regarding the technical side, we don’t require any 8 weeks of boot camp interview prep. If you reviewed code, wrote code and created cloud architectures you are good to go.

💰What is the compensation like?

Check our careers page. We are transparent and list salaries there.

🌍Where do you do your interviews?

As we’re a remote-first company, we use either Google Meet or Zoom for our interviews. We are flexible so if you have any preference, let the recruiter know.

📧How to apply?

You can apply by sending your application over to Kristiine (Head of People) via email: kristiine@modash.io. If you have any additional questions, you can also do so via email or through Linkedin.

💡Tips and tricks

Practice thinking out loud. For us, it’s not that important to finish the task. We need to understand how you think, how you approach problems, how you Google, how you…

Ask questions. Dunno why, but most people think that if they are interviewed they are not allowed to ask questions. Like they lose points or something. We value and encourage this. In startups, it’s really important to speak up and question the status quo.

Imagine that you are already working with us. You are solving a problem with your colleagues. Helping every creator in the world make a living.