Metabase (CA) interview questions

The interview process began with an initial debug session. If you pass this stage, it is followed by a series of panel interviews focused heavily on practical, on-the-job scenarios rather than just abstract technical questions. The loop consisted of three distinct panels: Communication, Troubleshooting (with a focus on database infrastructure), and SQL. The team seems to be looking for someone relatively technical who has a deep understanding of the infrastructure realm.

1. Candidates apply and are screened based on whether their background meets the minimum requirements. Saying why the role is interesting and supplying a LinkedIn profile go a long way. 2. Candidates go through a **short written assessment** to calibrate a specific set of technical skills. 3. If that’s a 👍, there’s a **hiring manager screen**. It’s not a particularly qualifying conversation, but more of a fit evaluation (what the candidate wants, what Metabase needs and can offer). 4. If that’s a 👍, the candidate moves to **panel interviews** with different people, scheduled asynchronously. Once the interviews happen, the team meets to debrief. 5. If that’s a 👍, we move to a **take-home assignment**, shared at the time, to be delivered asynchronously. Once it’s sent, the team meets to debrief. 6. If that’s a 👍, since it’s extremely rare for a submission to be a slam dunk, we may have a live conversation to **dive deep into the take-home submission**. Whether to move forward is a hiring manager decision. 7. If that’s a 👍, there’s a **final conversation with our CEO**, and we make a final call.