Vannevar Labs logo

Vannevar Labs Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 35 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
34.3% Positive experience

Which role are you interviewing for?

9 roles · 35 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Vannevar Labs.

Showing 4 of 35
Vannevar Labs logo
Vannevar Labs

Strategy and Business Operations

Operations · nearly a year ago

Mid Difficult Negative experience Accept offer 2 rounds
Interview process
Take home Presentation
Interview formats
Case Presentation

The interviewers were nice, but the process was lengthy and lacked transparency. The case study was particularly problematic. It was presented as a simple task, but its scope and detail were so close to their ongoing projects that it seemed like they used candidate work for their own benefit. This was hard to overlook during the interview. If you go forward, ask them directly how they plan to use your submission. Candidates should know this upfront before investing significant time in work that might help the company beyond just evaluation.

Confirmed questions1 question
  • Walk me through how you would tackle a wide-ranging issue concerning the team's current initiatives.
Vannevar Labs logo
Vannevar Labs

Forward Deployed Engineer

Engineering · nearly a year ago

Mid Difficult Neutral experience No offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen Take home Presentation Group Onsite
Interview formats
Behavioral Technical Coding System Design Presentation

I went through seven rounds for a remote role, with a potential next step involving senior leadership. The whole thing was remote and ran pretty professionally. The team seemed really mission-driven and experienced. First, an HR recruiter chat to see if it was a mutual fit. Then, the Hiring Manager talked about the day-to-day stuff and team dynamics. After that, a technical interview with a senior engineer, which felt more like pair programming. Then a quick check-in with the recruiter about next steps, mentioning the next four interviews would be back-to-back. Next was a frontend/React round where I had to debug a form and display API data; the data handling part had some tricky edge cases. Following that, I did a presentation of a past project, which led to a good discussion with thoughtful questions. Then came a system design interview, focusing on a high-scale content and user interaction system, which was broad and allowed for creative solutions. Finally, a behavioral interview covering collaboration, problem-solving, and ego. Got a generic rejection email afterward, and the promised feedback didn't happen, which was a bummer after investing so much time. But overall, it was a well-run process, and I'd still consider the company because of its mission.

Confirmed questions4 questions
  • How would you design a content management system to display diverse content with daily additions, making it easy for users to find relevant pieces? Detail the system, database, and UI.
  • Debug a React form with common errors and issues in CoderPad.
  • Use chart components to visualize API data in CoderPad.
Vannevar Labs logo
Vannevar Labs

Senior Software Engineer

Engineering · nearly a year ago

Senior Average Positive experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Presentation
Interview formats
Technical Coding System Design Behavioral Presentation

The interview process started with a recruiter screening call, followed by an interview with the hiring manager. Then there was a live coding interview, a systems design interview, and lastly, a behavioral interview. Although I didn't get an offer, I had a positive experience overall. The React interview was fair and well-designed, but I struggled because I didn't remember the syntax, even though I knew what to do. The interviewer was nice, patient, and professional. My only issue was the use of Typescript, which wasn't mentioned in the job description and was said to be optional beforehand. The systems design interview was a bit strange; the interviewer didn't give clear instructions on the goal, so I had to ask many questions to figure it out. I started with a general solution, but when I tried to go deeper, they shifted the focus to another high-level topic, so we stayed high-level the whole time. I was later told I didn't go deep enough, which was confusing and indicated a communication issue. The interviewer was pleasant but offered no guidance or feedback during the session. I had to sign an NDA before meeting the hiring manager, though I'm not sure why as nothing sensitive was discussed. A big thanks to the recruiter for providing feedback, which contributes to my positive impression of the company despite not getting an offer. I'd consider reapplying in the future.

Confirmed questions1 question
  • Could you design their flagship product, including a database schema and UI design?
Vannevar Labs logo
Vannevar Labs

Signal Processing Engineer

Engineering · a year ago

Mid Difficult Negative experience No offer 8 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check Offer
Interview formats
Technical Coding Presentation

It was a totally weird interview process. I had 8 chats with HR and engineers over two months. There was also a take-home where I had to dig into some RF data they gave. A Zoom interview followed, where I had to talk about how to solve real-time signal processing problems on edge devices. These questions were basically simplified versions of the main problem they're tackling. Even talked to the CEO, who seemed keen to hire me. They gave me an informal offer, then bailed at the last second with no explanation. They ghosted me when I asked why. Really badly done. The company seems to have leadership and org problems. The actual work sounds cool, but management seems really indecisive.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Vannevar Labs Interview Questions

Quoted word for word from Vannevar Labs interview reports.

Solve an algorithm problem, aiming for an O(1) time complexity using CoderPad.

Read reports

Can you design a system for ingesting news articles with images, storing them, and enabling user queries?

Read reports

How can we make a customer extremely enthusiastic about our product, even irrationally so?

Read reports

Can you solve a Leetcode problem that uses a queue data structure?

Read report

What was your reasoning for attending your specific university?

Read report

Formats, difficulty and experience

Across all 35 Vannevar Labs interview reports.

Interview formats

Behavioral 36.4%
Technical 21.6%
Presentation 18.2%
Coding 10.2%
System Design 8%

Interview difficulty

Easy 17.1%
Average 51.4%
Difficult 31.4%

Candidate experience

Negative 37.1%
Positive 34.3%
Neutral 28.6%

Reports by job function

Engineering 15
Operations 6
Sales 5
HR 4
Other 2
Design 2