Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Veeva Systems
Entrevista
1st round: Initial call with a manager. Felt positive.
2nd round: In-person Interview with another manager. We discussed my past experience and my opinions on SaaS platform. Felt good.
3rd round: In-person tech interview. I solved one LC Medium problem and a system design problem related to DB design. Two interviewers were supportive and the conversation flowed smoothly. We had a long, engaging discussion that ended with laughter.
4th round: In-person behavioral interview. The interviewer offered no greeting or farewell and started by requesting a detailed account of my work history from my first job onward.
The interviewer maintained a poker face throughout the interview. The conversation was challenging, and the questions felt irrelevant to the position, as if he were seeking a co-founder rather than a candidate.
He would pause for extended periods without reason or reaction to my answers, giving me the impression he had taken a dislike to me. The interview took an hour but felt like a-century long. At the end, he simply said, "That's all for today's interview," without making eye contact, so I left.
He did share some opinions with me, but the overall experience was negative.
5th round: A brief online video conference where we discussed the feedback from the previous interviewer and my salary expectations.
Preguntas de entrevista [3]
Pregunta 1
If two previous employers offered you a position, which would you choose?
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
