J'ai postulé via une autre source. J'ai passé un entretien chez Veeva Systems (Toronto, ON) en mai 2026
Entretien
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.
Questions d'entretien [1]
Question 1
“System design”: write code to efficiently assign requests to “workers”. Then create an algorithm that would do this in real life.
J'ai postulé en ligne. J'ai passé un entretien chez Veeva Systems (Londres, Angleterre) en janv. 2026
Entretien
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.
Questions d'entretien [1]
Question 1
your working experience for last couple of years
some basic technical questions