Real, anonymous reports from people who interviewed for Software Engineer at Veeam, newest first and distilled into what to expect across the loop.
I went through a longer, multi-round process where the structure felt mostly standard even as it dragged on. After an initial recruiter touchpoint, I ended up with about five rounds total, including a coding-pad style test, a hiring manager conversation, then technical interviews (followed by a system design round). The whole thing felt like it was moving forward in a controlled way, and I was even informed that I had cleared all stages and could move my candidacy ahead.
I had a fairly straightforward start: an intro call with recruiting, and then I went into a single programming interview that lasted about two hours. I’d been contacted by recruiting directly, so I didn’t have to do extra pre-work hack-style tests beforehand.
The interview process typically involves multiple stages, starting with a recruiter call, followed by a technical assessment, and then several technical interviews that may include coding and system design discussions. Candidates should be prepared for a structured yet sometimes lengthy process that can vary in the number of rounds.
Candidates can expect a strong emphasis on technical skills, particularly in C# and problem-solving related to concurrency and parallelization. Interviews may include live coding sessions and theoretical questions that require a deep understanding of language mechanics and system fundamentals.
Communication throughout the process can be inconsistent, with some candidates experiencing long periods of silence or unclear feedback after interviews. It's advisable to proactively follow up for updates and clarity on next steps.
Behavioral interviews may focus on cultural fit and alignment with company values, often involving discussions with team leads or managers. Candidates should be ready to articulate their thought processes and how they align with the company's mission.
The interviews can be quite demanding, with expectations for candidates to demonstrate not only coding skills but also a deep understanding of underlying principles and best practices in software engineering. Candidates should prepare for detailed questions that probe their technical knowledge.
Candidates have reported mixed experiences, with some feeling that the process was well-organized and others expressing frustration over perceived inefficiencies and lack of respect for their time. It's important to maintain a positive mindset and manage expectations throughout the process.