Tegus Software Engineer Interview Questions
& Process

It took 3 weeks and 4 rounds total to get through the interview process. I started with a phone screening where they asked some basic questions to get to know me. Then, I had to complete a take home assignment to check my skills. After that, there were 2 technical interviews, one focused on design and the other on debugging. The last round was an interview with the hiring manager. Honestly, it was one of the best interview processes I've experienced. They were really good about keeping me updated on my application status and answering any questions I had. Everyone I talked to was great, happy to help out, and seemed to really respect my time.

I first had a call with a recruiter, then an engineering manager did a technical interview with me. It was a pretty standard API and string handling question. The recruiter reached out again to schedule a final meeting with the manager, but then I got ghosted.

The interview process started with a recruiter phone screen, followed by a coding exercise with the director of engineering. Then there was a round of interviews covering systems design, a meet & greet with product/design folks, and another coding interview. Everyone was nice. My main feedback is that the Lead SWE role seemed designed to promote internal engineers without making them managers or staff ICs. The role was presented as a path to either EM or Staff IC, but the actual responsibilities were unclear. Oddly, there were no questions about management, people skills, or conflict resolution, despite the role having direct reports. It makes me question how much they value good management. This, combined with a 'work hard play hard' vibe, suggests it's good for ambitious younger engineers wanting to make a name for themselves. If you prioritize work-life balance and strong management that prevents burnout, this might not be ideal. Overall, it was a good experience, though.