Veepee Interview Questions
& Process

Premier appel téléphonique avec les RH, ils étaient sympas et m'ont vite mise à l'aise. C'était surtout pour vérifier mes motivations, mon parcours et il y avait quelques questions en anglais. Puis un deuxième et dernier entretien avec la responsable, assez long et pour pas grand-chose au final, avec peu de questions sur mon parcours mais beaucoup de questions techniques, sur la méthodologie et l'organisation du travail.

I was contacted on LinkedIn for some initial screening questions. After that, I had an interview with a lead project owner, which went well. They then scheduled a final interview. I was told it was me and one other candidate, and I would hear back in a week. They asked me to let them know if I had another offer so they could potentially speed things up. I did get another offer and told them, but I never heard back from them. It was a total lack of respect for my time.

The interview process at Veepee was disappointing and lacked professionalism. First, an HR Screening, which felt very superficial — there were no questions about my motivation or why I was interested in the company. The HR person had their camera off the entire time, which made the conversation impersonal and disengaging. Then, a First Technical Interview, which was more of a discussion around my background and experience rather than a technical assessment. Unfortunately, the interviewer didn’t look at the camera at all and was visibly focused on another screen, which was distracting. Even more unprofessional, he used a vape during the call. Finally, the Second Technical Interview, which was the most uncomfortable session. Again, the camera was off on their side. It started with very basic, unclear questions about networking and service management in non-cloud environments. The way the questions were asked was confusing and lacked structure. Eventually, we covered configuration management with Ansible and IaC with Terraform — topics where I gave detailed answers, possibly too much. The interview went over time (1.5 hours instead of 1 hour), and I left with the impression that the interviewer wasn’t aligned with the SRE domain. At the end, I received a generic rejection email saying that my "experience does not match," without clear feedback. In reality, it felt like they were looking more for a SysOps profile with a strong traditional networking background — not someone with SRE expertise. No SRE-related questions (like incident management, monitoring, SLOs/SLIs, or DevOps culture) were asked at any point.

The recruitment process was frustrating, and the managers' attitude was disappointing. It started well with a 30-minute HR interview, which was well-conducted and professional, done by an intern. The English discussion was smooth and structured. However, the interview with the managers was a completely different experience. A technical exercise was imposed without any prior mention, showing a lack of transparency and organization in the process. Furthermore, one of the managers was not a good listener and was particularly condescending, making the exchange unpleasant and unconstructive.