Rewarding work environment
Rewarding work environment
Transparent comp and processes Fast, efficient interview process Smart people - even as a senior eng there is a lot of learning that you can do The work is impactful and rewarding, making a noticeable difference for customers
Codebase is pretty large and can be hard to ramp up on. Maintenance of older products can hamper progress on new initiatives.
Dedicate a bit more time to maintenance and improvement of existing product areas, e.g. addressing tech debt.
Additional Ratings
Was this helpful?
Vanta Interview Experiences
Senior Software Engineer
I applied online. The process took 2 weeks. For the live-coding exercise, I was given a lot of materials and even an example video for how to prepare for the interview beforehand. That was nice. Upon joining the CoderPad, I was given a straightforw
Senior Software Engineer
The process took 2 weeks. I applied online, and the recruiter reached out. We had a great conversation about Vanta and my background during the phone interview. For the onsite interviews: * Practical Coding (1.5 hours) * Principles Interview * Syst
Senior Software Engineer
I applied online. Another candidate mentioned this, but it bears repeating: the first interview is a coding screen conducted with another developer. They provide a two-part problem: * Part One is a dense, "real-world" scenario that ultimately boils
Senior Software Engineer
June 19, 2023I applied online. The process took 2 weeks. For the live-coding exercise, I was given a lot of materials and even an example video for how to prepare for the interview beforehand. That was nice. Upon joining the CoderPad, I was given a straightforw
Senior Software Engineer
November 8, 2023The process took 2 weeks. I applied online, and the recruiter reached out. We had a great conversation about Vanta and my background during the phone interview. For the onsite interviews: * Practical Coding (1.5 hours) * Principles Interview * Syst
Senior Software Engineer
August 19, 2025I applied online. Another candidate mentioned this, but it bears repeating: the first interview is a coding screen conducted with another developer. They provide a two-part problem: * Part One is a dense, "real-world" scenario that ultimately boils
