
Weave Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Weave.
Software Engineer
The interview process is quite straightforward and includes the following stages: DSA Round – Focused on data structures and algorithms. Take-Home Machine Coding Assignment – A practical problem to be implemented independently. Machine Coding Discussion – A detailed walkthrough and discussion of your submitted solution. High-Level Design (HLD) Round – Covers system architecture and design decisions. Behavioral Interview – The final round assessing communication, teamwork, and cultural fit.
- An easy/medium data structures and algorithms question was asked during the DSA round.
- Numerous behavioral questions were posed throughout the entire interview process.
Software Engineer
This was by far the best interview experience I've ever had in my career. It was a very open-ended interview, I didn't even feel like I was being interviewed; instead, it felt like a casual discussion between engineers.
- Regarding data structures, what advantages would using one type (x) over another (y) offer in the context of actual engineering challenges?
Software Engineer
The recruiter reached out and we had a 30 minute phone call. They are currently setting up an office in India but also hiring remote folks across the US. The interview process begins with a 30 minute Google Meet call where the interviewer will share a Hacker Rank link. This link contains a Leetcode easy/medium question that needs to be solved within 30 minutes.
- A Leetcode medium problem involving subarrays was presented.
Weave Software Engineer Interview Questions
Quoted word for word from Weave interview reports.
“Implement a modified Caesar Cipher using reverse engineering on HackerRank.”
Read reports →“Can you describe how to implement a JSON API specification?”
Read reports →“Can you explain how you'd implement concurrency in Go?”
Read reports →“Regarding data structures, what advantages would using one type (x) over another (y) offer in the context of actual engineering challenges?”
Read reports →“Can you tell us about your experience with Golang?”
Read report →“What's your experience with implementing parallelism and concurrency in distributed systems based on your past projects?”
Read report →Formats, difficulty and experience
Across all 8 Weave interview reports.