The interview process was overall professional and technically focused. I had a live coding session on a shared screen with two interviewers, where I typed the solutions directly on my laptop while they observed and asked follow-up questions. What They Asked: Most questions were in C and C++, covering low-level behavior and understanding of how the language works “under the hood.” Examples of the questions/topics I was asked: Code-reading questions such as: “What will happen when this function runs?” – focusing on pointers, references, and memory behavior. A conceptual C question: a function receiving a pointer to a double. The discussion centered on ownership, side-effects, and best practices. I explained that passing a raw pointer to a function can make ownership unclear — Overall Impression: The interviewers were friendly and focused on understanding how I think about code correctness, memory, and best practices in C/C++. The questions were fair, practical, and aligned with real embedded/system-level development challenges.

I was rejected without any explanation, despite the fact that my skills are very similar to those requested. I interpret it as disrespect not to explain to the candidate the reason for rejection, since you do not understand what the problem is in the lack of great experience, skills or gender.