
Veza Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 21 interview experiences · FREE TO READ
Which role are you interviewing for?
9 roles · 21 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Veza.
Senior Frontend Engineer
Started with an intro round, then went through 2 tech rounds. The first tech round was a live frontend coding session and the second was a design round. The interviewers were nice. I felt good about the first round and the interviewer let me know I'd be moving on. The second round, I think I did okay, maybe 70/30, could have done better. But after that, crickets. No word from HR at all, total ghosting and no updates.
- Could you do a live coding exercise in React, involving async chunks from a mock API and displaying them in a table?
- Can you answer open-ended questions covering React, Redux, and Context APIs?
- How would you approach a design problem for a generic search box with results?
Commercial Account Executive
A recruiter first reached out. Then, I interviewed with the hiring manager and some of his team members (who are also Account Executives). The recruiter was pretty cagey about the company culture, which seemed off. The sales manager wasn't much better. However, one of the AEs I spoke with was fantastic and seemed to do the work that the first two interviewers should have covered. Honestly, I'd consider joining based on that conversation with the AE. The product sounds great, and the culture question I asked was about product and staff transitions, which apparently isn't a concern anymore. I got the green light from the hiring manager and proceeded. After getting another positive signal, I was ultimately rejected.
- Can you tell me about your professional background based on your resume?
Software Engineer
I was reached out by Veza’s HR, and we set up the interviews. The HR team was very nice and worked with me on timing. System Design Interview: This went well. The interviewer was collaborative and let me know what they were looking for. It felt like a productive chat. Coding Interview: This was totally different. The interviewer didn’t seem into it, and we spent most of the time talking about my previous jobs instead of the coding problem. When they finally gave me the task, it was just a super brief description, like three sentences, with input and output. When I said I wasn’t totally sure I understood the question, the interviewer just said, “How would you replace two chars?”, and didn’t explain more. I didn’t ask to discuss the solution, the requirements were unclear. At that point, I lost interest in solving it and said I didn’t know how to start. This was the weirdest and least structured interview I’ve ever had. After the meeting, I looked at the task and it took me 10 minutes to figure out what they wanted. I admit I might not have solved it, but I would have known where to begin.
- Tell me about system design for a part of a ticketing system.
- Describe your experience with hard LeetCode questions in a coding interview.
- Can you explain how you would replace two characters?
Product Manager
The process started with a recruiter screening to gauge my background. Then, I had an interview with the hiring manager, who is a Sr. Director. Following that, there were three rounds of interviews, and the final one was with the founder. I had a conversation with the Director of Product about my past roles, which was great. Then, an Architect focused on how I work with Engineering; he spoke pretty fast and I had to ask him to repeat himself a few times. The Head of Design interview was also conversational and enjoyable. The founder round started okay, but he got distracted and was looking at his screen a lot, like he was responding to messages instead of listening. This resulted in him asking questions I had already answered. Overall, it was a good experience because they kept me in the loop about everything.
- All the interviews were behavioral, asking about my experience.
Veza Interview Questions
Quoted word for word from Veza interview reports.
“Given an array of integers, find the duplicate elements.”
Read reports →“Can you identify the errors in this code snippet?”
Read reports →“Could you explain the different types in Javascript?”
Read reports →“What drains you?”
Read reports →“Can you explain how you would replace two characters?”
Read report →“How would you approach a design problem for a generic search box with results?”
Read report →“Could you do a live coding exercise in React, involving async chunks from a mock API and displaying them in a table?”
Read report →“What are your thoughts on computer science theory?”
Read report →“Can you share how many offers you've successfully had accepted this year?”
Read report →Formats, difficulty and experience
Across all 21 Veza interview reports.