DoiT Software Engineer Interview Questions
& Process

The interview started with a call with Oscar where I was given details about the recruitment process and told I'd get feedback after each stage. This was followed by a technical interview focusing on my experience, Go principles, channels, and goroutines. Unexpectedly, I was then asked to do a live coding task using a text editor, as Oscar hadn't mentioned this beforehand and I didn't have an IDE available. There were no questions about design patterns or architecture. The interviewers were quite introverted, which contrasted with my open personality. I also observed some communication issues when one interviewer tried to explain a task, suggesting they could improve how they ask questions. Furthermore, I didn't receive the promised feedback, even after reaching out separately, leaving me with mixed feelings.

So, the first bit was a 30-min chat with a recruiter. They gave me the lowdown on the job and I got to ask my questions. The recruiter also dropped some hints on how to prep for the next stage – basically, be ready to chat about past projects, the tech involved, and any tricky technical stuff you ran into. Then, I had a meeting with the engineering director. This part was way more technical, digging into my previous projects and some broader topics. I also got to ask some deep-dive questions about how things work, the team, and where the company and product are headed. There was a bit of a wait before I could lock in a time for the technical interview. That interview was with two senior folks from the team. They also zeroed in on my past projects, the hurdles I faced, and what I might have done differently. They even threw in some code examples for me to explain. The whole thing wrapped up with another call from the recruiter, an offer, and then some back-and-forth on the salary and start date.

So, there were three interviews in total. The first two interviews were pretty much the same, focusing on my past experience and why I was interested in DoiT. The last interview was more technical.