Real, anonymous reports from people who interviewed for Software Engineer at Mistral Solutions, newest first and distilled into what to expect across the loop.
My interview route was straightforward but very technical, and it leaned heavily on analog and digital foundations rather than anything like long system design. I remember going in with the expectation of software-focused questions, but the flow was broader: there was clear emphasis on electronic fundamentals, including topics like analog behavior and digital circuit reasoning, and it also pulled in embedded understanding.
I went through an aptitude-heavy online process that quickly pushed me into core software and C fundamentals, with hardware only if I chose it. The first round had a mix of time-boxed aptitude questions and domain-specific MCQs; for the software track it covered basics like pointers, functions, recursion, and output-style questions, along with bit/shift operators and small logic problems. A few questions even had negative marking, so I felt the pressure to be careful rather than just guess.
The interviews emphasize a strong foundation in electronics, particularly analog and digital concepts, alongside core software skills, especially in C programming. Candidates should be prepared for questions that integrate theory with practical applications, especially in embedded systems.
Candidates typically undergo an initial online assessment that includes aptitude tests and coding challenges, focusing on C fundamentals, data structures, and logic problems. Expect to face time constraints and negative marking in some assessments, which adds pressure to perform accurately.
The interview process is often structured in multiple stages, starting from online assessments to technical interviews and concluding with HR discussions. This layered approach allows for a comprehensive evaluation of both technical skills and cultural fit.
Throughout the interview process, there is a significant focus on communication skills and behavioral fit, particularly in HR rounds and group discussions. Candidates should be ready to articulate their thought processes and experiences clearly, especially under pressure.
Candidates are expected to demonstrate a deep understanding of technical concepts, particularly in electronics and C programming, rather than surface-level knowledge. The interviews often probe into specific projects and require candidates to connect their academic background to practical scenarios.
The overall difficulty of the interview process is perceived as average to high, with candidates noting the importance of preparation and stamina throughout multiple rounds. Many candidates reported feeling challenged but appreciated the structured nature of the evaluations.
