
GoGuardian Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at GoGuardian.
Software Engineer
They reached out about the role and set up a technical interview. The first one got cancelled last minute and rescheduled for the next day. For the second attempt, I was on time but nobody showed up. I contacted HR, but she didn't respond right away. About 30 minutes later, she got back to me saying a production issue caused the cancellation, and I wasn't told ahead of time. She said it would be rescheduled, but I never heard back. Honestly, it felt pretty unprofessional.
- Can you tell me about your experience with Go?
Software Engineer
So I got reached out by the hiring team on LinkedIn. First, there was an HR screen. Then, a 90-minute session going deep into my resume and a live coding challenge. After that, a 120-minute interview focusing on architecture and system design. We scheduled a 90-minute interview via G Meet with engineering team members, specifically one hiring manager and one engineer. The first part was about my resume, and the second was live coding, like LeetCode easy (flood fill). Then there was a week break on my end to schedule the next interview. I got feedback the next day about a 90-minute interview. The first half of that 2-hour interview was split between system design and architecture. Overall a great experience, though the offer was a bit low. It was odd that there was no info on the strike price of options.
- Can you explain how to solve the Fill Bucket problem, similar to a LeetCode style?
- How would you design Instagram from scratch, covering all its parts?
- Tell me about your resume.
Software Engineer
The interview process was pretty standard: first a phone screening about my background. Then a 1-hour technical round where I did a coding exercise with a Sr. Software Engineer. After that, a long 6-hour virtual on-site interview that covered everything: Front End, Back end, System Design, QA, Product/Project Management, and DB Design. Honestly, their recruitment process was terrible though! I specifically told the recruiter multiple times on the phone screening that I didn't have much industrial experience with Reactjs. They said it was okay because they had other teams needing backend engineers and I'd learn Reactjs on the job. But then, after I spent 6 hours interviewing, they rejected me for not being good enough at REACTJS. It seems like there was zero communication between the recruiter and the team. They could have easily cut me after the first call, but instead, they wasted my time and now expect me to re-apply in 6 months. No way! Thanks. For the GoGuardian team, please improve your internal communication and make sure your recruiters actually know what the teams are looking for and what the job description entails.
- Coding exercise: Print out a 2D matrix with some string manipulation
- Coding exercise: Flood Fill
- Backend question: Leetcode easy/medium Maximum Level Sum of a Binary Tree
GoGuardian Software Engineer Interview Questions
Quoted word for word from GoGuardian interview reports.
“Design the System of GoGuardian Admin and client portal”
Read reports →“How would you design Instagram from scratch, covering all its parts?”
Read reports →“Can you do a pair programming exercise in React where you create a bulleted list using props?”
Read reports →“Can you explain how to solve the Fill Bucket problem, similar to a LeetCode style?”
Read reports →“Tell me about your thoughts on architecture.”
Read report →“What are your thoughts on handling databases, specifically SQL versus Non-Relational?”
Read report →“Do you know SQL?”
Read report →“Can you tell me about your experience with Go?”
Read report →“What's your general knowledge of data structures and frameworks?”
Read report →Formats, difficulty and experience
Across all 10 GoGuardian interview reports.