
OpenGov Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 43 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at OpenGov.
Software Engineer
The interview process felt a bit too academic and boring, making me lose interest halfway through. The questions were about abstract ideas without any real-world connection or reason, even when I asked for more info. For example, during a search bar task, the interviewer really drilled down on how to test things: "Why did you pick this approach? What other testing methods are there? Can you recall the syntax for writing tests?" With today's AI tools, focusing on memorizing syntax feels old-fashioned and not how engineers actually work. Honestly, it didn't feel like a true test of problem-solving for a senior role.
- What steps do you take prior to designing a component?
- Could you design a search bar?
- And can you write the test cases for that search bar design?
Software Engineer
Interviewing at OpenGov was a pleasant experience - the company prides itself on its values and the employees seem excited to work on a product that sees immediate impact to people's lives. The entire process took about 6 weeks. The first interview was with Nadine (recruiter). The second interview was a 1hr technical interview in javascript with two software engineers (2 LC questions - 1 easy, 1 medium). Third interview was with the senior director of engineering and this was a culture fit/behavioral standard interview. The fourth interview was coding up a React app with two software engineers. Here they test for your React and HTML skills. The final interview was with the architect and this was a basic back and forth system design interview. Though I did not go with the offer for personal reasons, OpenGov seemed like a close-knit fast paced company where one can expect to make great progress in their software engineering career.
- Can you solve the Two Sum problem?
- Can you solve the Letter Combinations of a Telephone Number problem?
- What would you do if a coworker was going down a path that you knew wouldn't work out?
Software Engineer
The interview process took place over 3 days and had 5 rounds. It began with an HR screener, followed by a technical screener, then a coding interview. The coding interview focused more on practical applications rather than algorithms and data structures. The last two rounds were behavioral interviews. I found everyone I met to be engaging and easy to talk to, with whom I had good conversations. They all seemed well-rounded and driven. What really stood out was how involved the recruiter was throughout the whole thing, offering advice at different stages and giving good feedback afterward.
- Can you tell me about your experience with Javascript?
- How would you describe your communication skills?
- What are your long-term career aspirations?
OpenGov Software Engineer Interview Questions
Quoted word for word from OpenGov interview reports.
“What is the purpose of asynchronous services or event-driven architectures?”
Read reports →“Can you find two numbers in an array that add up to a specific target value?”
Read reports →“How would you shorten a long URL and then display a mapping of the original long URL to its shortened version?”
Read reports →“What are the ideal use cases and limitations for GraphQL?”
Read reports →“Can you solve the Letter Combinations of a Telephone Number problem?”
Read report →“Could you build a React App that shortens URLs?”
Read report →“Can you explain a JavaScript concept involving return functions that invoke other functions?”
Read report →“How would you build a basic React application that interacts with APIs?”
Read report →“Can you design a system to track fitness movements and exercises?”
Read report →Formats, difficulty and experience
Across all 43 OpenGov interview reports.