Overall, I enjoyed my time working at Veeva for a few years.
Very customer-focused (in terms of values, "employee success" comes after "customer success"), so there's a big focus on churning out features, perhaps at the expense of quality, writing test code, etc.
Not exactly sure how people go about self-improvement or doing too many new / innovative things. But it's fine if you're fine with being a code monkey, which most people are kind of okay with.
As the code base grows, code maintenance and production issue troubleshooting becomes trickier.
Somewhat questionable work-life balance - it's up to the engineer to set some self-restrictions and work boundaries, because there is always more work to be done.
I was sent a coding assessment. It was a very difficult problem, considering it was for a new grad role. I ended up failing the assessment. It was a HackerRank-style problem.
The interview process began with an HR screen, followed by a discussion with the hiring manager. Next were two paired programming sessions. Both engineers were surprisingly friendly and easy to talk to. These sessions featured problems that were pe
There was an initial screen interview with the recruiter, asking basic qualifying questions and general behavioral questions. Afterwards, there was an online assessment portion, which was given on a website called Codingame.
I was sent a coding assessment. It was a very difficult problem, considering it was for a new grad role. I ended up failing the assessment. It was a HackerRank-style problem.
The interview process began with an HR screen, followed by a discussion with the hiring manager. Next were two paired programming sessions. Both engineers were surprisingly friendly and easy to talk to. These sessions featured problems that were pe
There was an initial screen interview with the recruiter, asking basic qualifying questions and general behavioral questions. Afterwards, there was an online assessment portion, which was given on a website called Codingame.