The first interview I had was a video call with a person from the recruiting department. The questions asked were strictly behavioral (e.g., my interest in Veeva, my best programming languages, my interests, etc.).
The second interview I had was a video call about a week later that lasted 90 minutes. I had around an hour to complete the coding challenge.
The interview was nice and friendly. The interviewer stepped out of the room for a couple of minutes but was back shortly. With the interviewer's help, I was able to work through some small issues I was having and managed to complete the problem. After solving the problem, I asked the interviewer some questions about their experience with the company. I was also asked about some basic OOP concepts and trivial details about Java HashMaps.
The interview was a good experience. I'm not really sure why I didn't move forward in the interview process.
What are polymorphism, abstraction, inheritance, and encapsulation?
What is the difference between an abstract class and an interface?
What does the protected keyword do?
What is the heap in Java?
How does a Java HashMap work? What is the best-case lookup time? Worst case?
Given a list of Person objects, group all Person objects that have the same first name. Two first names can be the same if they are aliases of each other (e.g., Bob and Robert, Elizabeth and Liz, Chris and Christopher).
Person objects consist of firstName and lastName Strings, and have get() methods for each respective variable.
The following metrics were computed from 1 interview experience for the Veeva Systems Associate Software Engineer, New Grad role in United States.
Veeva Systems's interview process for their Associate Software Engineer, New Grad roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Veeva Systems's Associate Software Engineer, New Grad interview process in United States.