Stage 1: Hiring Manager interview My first interview was with Mariella. She was very kind, explained the process clearly, and was very helpful throughout the different stages. Stage 2: Technical assessment The second stage was a technical assessment. The instructions mentioned that it should take around one hour to complete. Stage 3: Technical review After that, I had an interview with Fabrizio, where we reviewed what I had done in the technical assessment. He was very friendly, easy to talk to, and gave off very good vibes. Overall, this part of the process was very positive. Stage 4: System design interview The final stage was the system design interview, and this is where the experience became uncomfortable. The interview was with Chris, and it was the only interview in the process that was not recorded. From the beginning, the atmosphere felt strange—not necessarily hostile, but definitely uncomfortable and not very welcoming. During the interview, there was no positive feedback at any point, and the attitude felt quite apathetic. Overall, it was a poor experience, especially compared to the previous stages. Overall experience: In general, the process was good, especially the first stages with Mariella and Fabrizio. However, the last interview was a negative experience and affected my overall perception of the process.

4 levels for senior software engineer, it is good, more involved technical questions and coding rounds, panel was good asking different set of questions, and also have been interviewing different projects took the interview call.

My interview opens with a discussion on technical decisions. Instead of just "What is a class?", the interviewer asks: "Why choose C++ over a managed language like Java or Python for your last project?"I focus my answer on predictable performance and fine-grained memory control. I explain that for our low-latency data processor, the overhead of a Garbage Collector (GC) was unacceptable. This leads naturally into a discussion on RAII (Resource Acquisition Is Initialization). I explain that by tying resource lifespan to object lifetime, C++ allows for deterministic cleanup without the need for manual free() calls or a GC.