Technossus Interview Questions
& Process

The recruiting process was pretty standard. I was contacted by an in-house recruiter who was able to answer all my questions about the role and the company. Following that, they set up a technical interview, then a culture/fit interview, and finally, I had a closing conversation with the CEO.

The interview process was quite thorough and comprehensive. It involved two interview rounds, with each one lasting approximately one and a half hours. I found the interviews to be very positive, and I felt comfortable with the CEO and the rest of the team who interviewed me, as they seemed well-prepared with their questions. They questioned me extensively on various aspects, including my previous work history, my strengths and weaknesses, my accomplishments, and my interests.

The company was super quick to respond after I applied. The whole process took about 4 months, which I found out later was because of internal planning delays and a management reorg that would affect who I reported to. I kept following up, especially after the first in-person interview went well, but I did feel stuck sometimes. Once the final interview was set, I met with the management team. I had questions ready about the company, operations, growth strategy, how they stack up against competitors, the biggest growth challenges, and the types of clients I'd be managing. The talk was real, and I appreciated that they didn't try to hype up the company too much. I explained how my skills could help them meet their goals. They made an offer at the end of the meeting, and I actually started right away to get into some key planning sessions. I felt valued and part of the team immediately.

It was a 1:1 interview at their Irvine Office. The interview felt disjointed and awkward. The interviewer asked questions that seemed inappropriate or irrelevant for a professional engineering role, like coding a palindrome. They didn't ask anything about the work environment, industry expertise, or architecture. Instead, the focus was on coding on a whiteboard. It felt like an interview for someone fresh out of college. In today's world, focusing on syntax that can be looked up and coding from memory on a whiteboard isn't professional.