Envié una solicitud electrónica. Acudí a una entrevista en Veeam Software en ene 2026
Entrevista
The technical interview is completely unrelevant to the job title.
There were no questions about the high-level architecture knowledge (Like Microservices, Communication between them, etc.), no questions about the more low-level architecture (Like DDD, idempotency, outboxes).
There were only questions about some kind of useless knowledge, which can be checked/googled at any second.
TLDR waste of time, unfortunately
Preguntas de entrevista [1]
Pregunta 1
By having the interface X, a class Y that implements it, and a class Z that extends the class Y + overrides one of the methods using override, and the second one using new, Tell which method will be called if ... Bunch of different combos of those things.
Thank you for posting your feedback and we´re sorry to hear that the interview process did not match your expectations.
We appreciate that you have taken the time to bring to our attention your concerns with the interview process, and we will use your input to improve it.
Thank you and we wish you all the best.
Experiencia positiva
Entrevista difícil
Solicitud
Envié una solicitud electrónica. El proceso duró 4 días. Acudí a una entrevista en Veeam Software (Praga) en abr 2026
Entrevista
Phone screening via HR. They somehow ask if you intend to do additional jobs in case you start working for Veeam
An online test where there is mostly actual code snippets that you try to pick from a multi choice answers.
On technical interview online I was asked boxing/unboxing scenarios. In a second question there was a class implementation that you are expected complete. Classes itself likely getting derived from IEnumerable
Respuesta de Veeam Software
1mo
Thank you very much for choosing to interview with Veeam Software. We appreciate the time and effort you've spent for this process, and we wish you all the best in your job search.
One of the rare company who still starts with test task, but that's ok. The main thing is that the task is too big for test, require much time, strict rules and strict technologies. After I suggested a decision, spent 3 hours for that, I was asked to continue with it. I asked them to discuss it by voice, because I didn't have enouph time and was rejected because it would wasting time for the companie's developer. Well, I glad that I spent only 3 hour for company, that don't respect my time. And you don't even know would it be interesting project or company for you, because test task was given before the intoductory interview. Interview process is just wasting your time, hope the company will change it once.
Preguntas de entrevista [1]
Pregunta 1
Test task was suggested before the introduction call
