
Verkada Solutions Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 39 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Verkada.
Solutions Engineer
The interview process was really messy and had way too many interviews. I get that sales engineering needs tech/networking knowledge, but honestly, the company doesn't make devices that really need super deep networking skills, in my opinion. They're just regular IoT devices, so the most complex troubleshooting would probably be at layer 2, and never anything with routing, because the customer handles that. But the expectations are way too high for the pay offered, making this job kind of pointless and a waste of time. Just wanted to let others know there are better, more worthwhile opportunities out there.
- Could you explain the differences between TCP and UDP protocols?
- Describe the DNS resolution process.
- Walk me through the DHCP request and offer sequence.
Solutions Engineer
So my experience was pretty much what others have said. It's a 4 stage process: First, a recruiter screening. Then, two 30-minute technical screenings. The final stage is an onsite visit to HQ. There, I had to do a presentation to a panel, another technical screening, and then individual interviews with about 3-5 people, lasting around 5 hours total. Everything was great until after the HQ visit. Verkada never told me I wasn't moving forward, and I had to chase them for an answer myself. This felt disrespectful, especially after I traveled out of state (they cover flights and hotel, but you pay for other transportation and expenses) and prepped a whole presentation. When I finally got an answer, they said I was out because of a lack of networking experience. That's fine, most of the team has 5+ years in that area. But I had made it clear my background isn't network engineering, which should have been obvious from my resume. Overall, the experience was good, except for those two major issues. If your background is in network engineering, this might be a great place for you.
- How would you explain DNS at a high level?
- Can you go into detail about DHCP and DHCP Relay?
- What's your high-level understanding of NAT?
Solutions Engineer
I had three interviews over the phone, starting with a recruiter chat and then two with senior managers. The last one was in person and included a presentation and a facility tour. The whole thing was super fast, they kept me in the loop, and it all went smoothly. It was a really enjoyable and worthwhile experience for me.
- Be ready to discuss network fundamentals like the TCP/IP model, TCP handshake, DHCP, TLS/SSL, and VLANs, including how traffic moves across a network, going several layers deep and explaining your reasoning.
Verkada Solutions Engineer Interview Questions
Quoted word for word from Verkada interview reports.
“How would a service like Netflix distinguish between different users who share the same IP address?”
Read reports →“If UDP is chosen, is ensuring complete and ordered data transmission not a concern?”
Read reports →“What are the drawbacks of running multiple services like DNS and DHCP on a single device?”
Read reports →“For a large business network with hundreds of LANs, what would be the recommended number of DHCP servers?”
Read reports →“How does DHCP work, and what is the DORA Process?”
Read report →“Can you explain the difference in purpose between VLANs and subnets within a network?”
Read report →“How does a device establish communication over a network or the internet?”
Read report →“Describe the distinctions between broadcast domains, VLANs, and subnets, including scenarios for their use.”
Read report →“Can you explain what a DNS is in your own words?”
Read report →Formats, difficulty and experience
Across all 39 Verkada interview reports.