Zoom phone screen with HR recruiter.

Take-home online assessment on CodeSignal.

Team day: a four-hour, five-interview process in one day over Zoom.

• First was a coffee chat with new hires. Be prepared to vibe well with the young people here; they're mostly looking for fit.
• Next were two technical interviews.
• Next is a meeting with the technical manager. I felt like this one was mostly to see how you think and approach problems. Personally, I think this is the most important interview. I spent a lot of it talking about technical problems I unraveled and what I learned in the process. Try not to brag, but show off your experiences in a way that shows you appreciate that you don't know much still, but are eager to learn more under the manager. Listen very carefully to how the manager responds to your stories and be quick to elaborate more on how your experiences are relevant to what they're saying, or how enthusiastic you are for exactly what they are mentioning right now. He also asked some behavioral questions when there were lulls in our conversation, like what got you interested in CS and what was your favorite class.
• Lastly was an interview with the HR person. Tons of behavioral questions here, like what are some experiences in your life that shaped you, what is something you're most proud of, and what do you like to do in your free time besides coding.

Then there were questions related to career outlook, like where you see yourself in five years and why Veeva (this one is really important).

The coding questions were not really LeetCode-style questions. You didn't have to know very much about data structures or algorithms, but you should be able to write code quickly and accurately.

They expected you to iterate through the code, and they would do this with you in a pair-programming fashion. Communication is very important here. The main thing they are looking for is how adeptly you think. They would present a new edge case, for example, and want to see how logically you can reason, like, "Hm, this edge case wasn't really handled by my logic here, so if I add something like this... this should work."

What they don't want to see is you read the problem and immediately code the optimal dynamic programming solution. All that tells them is that you've seen the problem before.

The actual questions were an "integer to Roman numeral" problem and a simulation of "Conway's Game of Life."

For the second problem, I didn't even use the optimal data structure, but I communicated all my thought processes. So, when the interviewer revealed the optimal solution, I was able to have a fluent conversation to show my understanding.