Duco Software Engineer Interview Questions
& Process

I had 4 interviews. 2 technical interviews, 1 technical test, and 1 HR interview. These interviews were well-structured, pleasant, and well-communicated. The only reason I had a neutral experience instead of a positive one is that they ghosted me afterward instead of emailing me that I didn't get the job.

After the first phone screen, I got a take-home coding challenge. It was interesting, not too hard to finish, but it had hidden complexity if you wanted to do it perfectly. They reviewed my submission fast and I was invited for an in-person interview a few days later. The F2F interview was about 2.5 hours and started with a chat with the hiring manager about my past experience, like how I handled production bugs or decisions I made that fixed issues. Then, I spent 1.5 hours with two developers where we went over my code challenge, followed by a pair programming session where I had to code a debounce function. This task was tricky, but one developer offered help and shared ideas. The other dev didn't do much. After that, there were more general questions about their system architecture and problem-solving approaches. Finally, I met with three lead developers for a few more questions. I got feedback quickly and received compliments, but no offer because the role's seniority wasn't quite what they needed. Everyone was nice, so the overall experience was good.

Applied through an agency and heard back in less than a day. I wanted to move things along quickly, so they scheduled a phone interview for the very next day. It was a general screening call. They got back to me again in under 24 hours. Then I had to do an online test, which I finished in a day, and after that, they invited me for an interview later that same week I applied. The on-site day had two in-person interviews and a technical problem to work through.