Real, anonymous reports from people who interviewed for Software Engineer at Wärtsilä, newest first and distilled into what to expect across the loop.
I started with an assignment rather than a live conversation. I was given a navigation route calculation task, completed it, and submitted it over email. After my submission was approved, the process moved forward and they scheduled an interview on Teams a few weeks later.
After an intro to the project side with the project manager and developers, the conversation quickly turned technical. I introduced myself, then the questions went hard into C++ topics. They kept me on OOP and general C++ fundamentals, and the DSA questions pulled in data-structure thinking rather than just recalling syntax.
Candidates often start with a practical assignment related to the role, which they must complete and submit before moving to the interview stage. This initial task is crucial for progressing in the hiring process.
The technical interviews are rigorous, often diving deep into C++ topics, data structures, and algorithms, with a strong emphasis on reasoning under pressure and understanding core concepts rather than just syntax.
Candidates frequently report a lack of communication after interviews, leading to feelings of uncertainty and frustration regarding their application status. Clear follow-up is often missing.
The interview process is generally structured, with clear stages that include introductions, technical discussions, and assessments, which helps candidates understand what to expect.
Some interviews include practical assessments of domain-specific knowledge, such as interpreting technical diagrams, which test candidates' understanding of the relevant systems and components.
The atmosphere of interviews can vary significantly; while some are professional and respectful, others may feel rushed or disrespectful, impacting the overall candidate experience.