Solutions Engineer applicants have rated the interview process at V7 with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Solutions Engineer roles take an average of 42 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at V7 overall takes an average of 24 days.
Common stages of the interview process at V7 as a Solutions Engineer according to 1 Glassdoor interviews include:
Phone interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at V7 (New York, NY) in Apr 2026
Interview
There is a recruiter screen first and then there is a round where you have to demo building an agent with a test case given. They give you access to the V7 software and documentation beforehand so really familiarize yourself with everything because you have to do it while sharing your screen. Then, you need to live code an API integration, so make sure you have your terminal set up and ready to go before the interview. I wasn't well-prepared but they were nice about it and gave me post-interview feedback, which I appreciated.
I applied through a recruiter. The process took 6 weeks. I interviewed at V7 (London, England) in Apr 2024
Interview
1. Recruiter call
2. CEO interview, some technical questions, mostly non-technical
3. Interview with one of the solution engineers, general interview.
4. Technical test interview, this was essentially a 1 hr coding exercise. Task was to build a API in python to interact with the APIs in the product - show that you can build a integration MVP. I found this to be a confusing exercise but then again I failed it so maybe that's a reflection of my skills rather than the interview setup. I had already before the interview built the integrations on a test setup to familiarize myself with the products APIs but I still didn't understand the use case but I am not a developer per se.
5. Interview with CTO, again some technical questions but mostly non-technical, what are your motivations type chat.
6. Interview with CRO, mostly around working with the sales team etc.