Initial phone conversation with hiring manager.
Phone conversation with lead engineer on team to discuss role and ask questions.
Take-home assignment:
A very odd interview occurred, wherein the lead engineer provided an overview of the architecture and systems the team uses. They then explained issues with their configuration and engineering practices and asked how I would fix problems or better handle processes.
The lead admitted that the team was learning as they went and might not have implemented best practices or possessed the skills to do so. They also could not explain how they tested their application and infrastructure through a normal CI/CD process. These were major red flags.
For some reason, I continued with the process and was given a take-home assignment. This involved building an application incorporating a LeetCode-style algorithm. Additionally, I was asked to configure and create architecture diagrams for a very specific use case the team works on.
After successfully writing the algorithm and application, along with diagrams, I was followed up with shortly. I received a decline to move forward because my expectations did not align with theirs.
The following metrics were computed from 27 interview experiences for the Veeva Systems Senior Software Engineer role in United States.
Veeva Systems's interview process for their Senior Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Veeva Systems's Senior Software Engineer interview process in United States.