The interview process structure, in order, was:

• 1 HR Call
• 1 OA (Online Assessment)
• 1 Hiring Manager Match Call
• 1 Team Day (4 interviews back-to-back)

Apparently, there was another call with the Head of Recruiting during the offer stage, but I didn't make it there.

Experience:

While some interviewers were nice, some seemed uninterested or just plain rude. One interviewer started responding to emails halfway through the interview. Another interviewer tried to poke holes in points on my resume and debate me on seemingly random topics. Because of this, I only had 15 minutes to complete the technical problem of the interview.

Tips:

Just remember that the technical portion is not as important as the behavioral. Don't try to woo this company by saying that you're interested in learning or exploring; this can look like you'll want to leave in a few years. They care more about longevity and your traits that indicate you'll want to stay in the role for a long time. Also, make sure you have 101 reasons for 'Why Veeva?'

Summary:

So many rounds, and for what? Why ask so many technical questions when they don't seem to matter much? Please ensure your interviewers know how to hold a conversation. It felt like a waste of time.

Every coding question (unless specified) was in Java.

• Trying to figure out the purpose of a very poorly written function, refactoring it, and writing tests for it.
• Implement a graph to model connections between various cities. Then write a function to find the shortest path between two cities. Then write a function to find all cities that are equidistant to City A and City B.

Interview C:

• LC: Validate Parentheses, Word Break
• Questions on JavaScript (== vs ===, etc.)
• Questions on React
• Writing a basic SQL query (grouping, etc.)