The interview process was a little bit janky, not the best. My first interview was a non-technical behavioral interview where the interviewer asked questions like "Why Veeva?" and "What skills do you bring?"
After that, I talked to an older gentleman, and he asked me an easy question about checking for palindromes.
After that, the interview got kind of weird. The CodePen link that he gave me just didn't work for the second part of the interview.
I could not read the text on the page because it had a weird glitch; the text would appear on the page twice. So, I had to use my own editor and then copy and paste my code (every five or so minutes) onto the CodePen page that I could not see.
It was a weird experience and made the interview very challenging because there was not a very good way for me to convey my thoughts in real time. On top of that, the interviewer wasn't very responsive. It was really hard to converse with him and get his response or his thoughts.
These two things combined made for a very boring interview where I was just pushing code into an editor and trying my best to explain what I was doing, but I could not do it as effectively as I would have liked.
Palindrome Checker, and read in a file.
Cluster together all last names into an ArrayList.
General questions about Hash Tables, BSTs, and their runtime.
The following metrics were computed from 4 interview experiences for the Veeva Systems Software Engineer New Grad role in United States.
Veeva Systems's interview process for their Software Engineer New Grad roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Veeva Systems's Software Engineer New Grad interview process in United States.