Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en Veeva Systems en jul 2023
Entrevista
Initial 30-minute phone interview followed by 2 1 1/2 hour interviews. The initial interview was a basic HR/Recruiter interview. The second interview was 2-part. Part one with the Director of Engineering, part 2 was a technical interview with a Senior Software Engineer.
Preguntas de entrevista [1]
Pregunta 1
The first recruiter interview was very basic questions about your background and why you were interested. The interview with the director of engineering was a little more focused with still the basic standard interview questions like "what is your proudest career moment", and a few more questions directly related to the job. The technical interviewer, since I was interviewing for a C# position, was looking for very specific answers to his questions. First, he asked the difference between abstract classes and interfaces, then the difference between reference and value, then what static classes vs. singleton classes were. Then he wanted me to describe the MVVM framework, and he wanted to know what interface that classes should inherit to avoid hash collisions when using objects as Dictionary keys. He asked about data triggers, data binding, He asked what ascynchronous methods do; he wanted to know about the Dispatcher class. He gave me a snippet of code, something like Task.Delay(1000).CompleteAsync and asked me to explain what it did.
Solicité el puesto por otro medio. Acudí a una entrevista en Veeva Systems (Toronto, ON) en may 2026
Entrevista
Everyone I talked to in the process seemed very genuine and down to earth, so that part was good. The process was a bit long and specific to Java so I had to relearn that after several years. The coding question during the onsite was an algorithm I learned in undergrad, and had never touched again, so I don’t think it gave great signal. It was either you studied that specific algorithm or you didn’t, and you couldn’t brute-force it. I did not enjoy that. The system design problem was also strange. It started out coding a toy algorithm for a specific request assignment problem, and then about designing a real-world algorithm for the actual problem. I also don’t know what signal they were trying to get out of that. I was expecting a standard architecture design problem, not that curveball. I don’t know how to rate the interview difficulty. It was just strange. I came away expecting a rejection and received one about a week later.
Preguntas de entrevista [1]
Pregunta 1
“System design”: write code to efficiently assign requests to “workers”. Then create an algorithm that would do this in real life.
Envié una solicitud electrónica. Acudí a una entrevista en Veeva Systems (Londres, Inglaterra) en ene 2026
Entrevista
First round is the hiring manager round.
Second round is the technical coding round, asked to build a basic UI component.
Questions were vague but easy. They didn’t seem very interested, which makes me think if they were actually looking to hire anyone!
had a first call with recruiter and he says his feedback is super positive but haven't get any follow up after that.
was asked about my working experience, salary expectation and a couple of basic technical questions.
Preguntas de entrevista [1]
Pregunta 1
your working experience for last couple of years
some basic technical questions