dbt Labs Interview Questions
& Process

The whole hiring journey from application to offer took about 1.5 months and had multiple steps. It kicked off with a recruiter call where we chatted about my background and availability, which was super nice and set a good vibe. Then, I interviewed with the hiring manager, who dug into my knowledge of dbt Labs, my fit with the team, and my professional history. They were really approachable. After that, I got a technical challenge with three parts that I had about four days to complete. While working on it, I also did some dbt Academy courses. I documented my work with screenshots from a sandbox. The next meeting with the manager involved me explaining my technical assessment solutions, where I struggled a bit, and other ways I could have solved it, plus showing how I troubleshoot in general. The final interviews happened all on one day and covered things like handling pressure, feedback, teamwork, and dealing with unhappy customers. Everyone I met was cool, professional, and friendly, making it way less stressful than I expected. Honestly, it was a great experience, I felt really good about it throughout and loved talking to the team. The hardest part was the wait for the final decision, but patience paid off when I got the offer!

The interview process was smooth and efficient - I had about 4 interviews over a 2 week time period. Challenging in the sense that I took time to prepare examples ahead of time based on who I was speaking with and interviewers asked thought provoking questions with follow up to dive deeper. Got a great sense of what company culture was like throughout the process, as well as what it would be like to work alongside those who interviewed me!

The recruitment process felt pretty disrespectful. Recruiters seem to just scan resumes for keywords instead of reading them properly. They use Zoom calls, which they admit are for an AI to transcribe and summarize for a manager. The recruiter seemed bored and just asked really general questions, like 'tell me more about your programming experience,' probably to make sure the AI recorded enough. Then, they'd say you applied for a Python role but you'd actually be rewriting the codebase in Go/Rust, which is wild. When I asked about work-life balance, the answers felt dishonest and vague.

So I went through the whole thing: recruiter screen, then the hiring manager, then a loop with 4 interviews, and finally a leadership interview. Each step was a gate. The leadership one got pushed back twice, which made me think they might've already picked someone but still saw me through since I passed everything else, or so the recruiter said. It was super weird though, because in the leadership chat, the interviewer was all like 'I'm leaning towards you' and 'I want you on my team.' But then, just hours later, I got a rejection. Total head-scratcher.