Real, anonymous reports from people who interviewed for Software Engineer at Landis+Gyr, newest first and distilled into what to expect across the loop.
I went through a short, practical interview that leaned heavily on fundamentals and quick communication. After a simple initial scheduling step, I joined a one-hour session with a developer where the questions were programming-language agnostic and stayed pretty basic, with a live coding component that felt more like an easy LeetCode problem than anything open-ended. Along the way, there were behavioral questions mixed in, and the rest of the technical questions were mostly pulled directly from the job description.
My process felt like two online rounds spaced a couple of weeks apart, with the stakes never quite feeling “make or break,” but still clearly focused on fundamentals. The first step was a technical coding round centered on DSA-style topics like arrays and strings. After that, I moved into a second technical discussion that covered .NET Core concepts and databases, and then the round closed with an HR component aimed at communication and behavioral fit.
The interview process typically consists of multiple rounds, starting with a written assessment followed by technical interviews and concluding with an HR round. The structure is generally straightforward, moving from online assessments to in-person discussions, often within a single day.
Candidates can expect a strong emphasis on technical skills, particularly in core programming concepts such as OOP, .NET, and data structures. Live coding exercises and theoretical questions are common, with a focus on problem-solving and clarity in explanations rather than memorization.
The HR rounds often focus on communication skills, cultural fit, and salary discussions. Candidates should prepare for behavioral questions that assess alignment with company values and their ability to articulate their experiences and motivations.
The tone of interviews tends to be conversational rather than adversarial, with interviewers encouraging candidates to explain their thought processes. However, some candidates reported experiences where the environment felt condescending or overly critical.
Candidates often experience a quick turnaround from interview to offer, but there are reports of delays in communication post-interview, particularly regarding offer letters and documentation requests. Candidates should be prepared for potential waiting periods after the interview process.
Candidates reflect that focusing on fundamental concepts and clear communication is crucial for success. Many suggest practicing coding problems and being ready to discuss theoretical concepts in depth, as well as preparing for potential logistical discussions during HR rounds.