Technossus Software Engineer Interview Questions
& Process

the interview was over video and we mostly talked about SQL and Angular. a senior engineer and an HR person were there the whole time. the difficulty was average

It started with a hiring manager screen, then three rounds with increasingly senior tech people. After that, I had a 1:1 with the client I'd be working for. The client's questions were more about me – how I think, work, and what I've done, rather than specific problem-solving. It was a relaxed chat. Interestingly, the client asked the tougher technical questions, not Technossus. I just stayed myself throughout, answering honestly and admitting when I didn't know something, offering my best guess. I got an offer for a contract-to-hire role, which is their usual start to see if I fit before converting. I passed on it because I dislike contract-to-hire and the initial salary was less than I'm making now. They came back with a better salary and direct hire, but it still wasn't enough for me to switch jobs for such a small increase. They knew my preferences and salary expectations beforehand but still low-balled the offer, which left a bad impression. They seem like good people I would have enjoyed working with, but they just wouldn't meet my salary needs. Maybe as a consultancy, they aim to keep costs lower for higher profits. I declined the final offer.

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.