Software Engineer II applicants have rated the interview process at OpenGov with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 63.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer II roles take an average of 26 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at OpenGov overall takes an average of 25 days.
Common stages of the interview process at OpenGov as a Software Engineer II according to 6 Glassdoor interviews include:
Phone interview: 29%
One on one interview: 21%
Group panel interview: 21%
Skills test: 14%
Other: 7%
Presentation: 7%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 4 days. I interviewed at OpenGov in Mar 2025
Interview
The interviewer didn't show up. I waited in the Zoom meeting for 20 minutes of the 30 allocated minutes for the interview, and they never showed up. I emailed them after 5 minutes of waiting and asked if they needed to reschedule, to which I got no response.
Other Software Engineer II Interview Reviews for OpenGov
I applied online. The process took 4 weeks. I interviewed at OpenGov (Atlanta, GA) in Apr 2025
Interview
I recently went through OpenGov’s interview process, and I have to say, it was one of the most thorough and well-structured experiences I’ve had. The process included an initial screening, three technical interviews, and a behavioral interview. While it was rigorous, the team made sure I felt supported and valued every step of the way.
The recruiters and interviewers were incredibly professional, communicative, and welcoming. They took the time to answer all of my questions thoroughly, which gave me a clear understanding of both the role and OpenGov’s culture. I appreciated how comfortable and confident they made me feel throughout the process.
Overall, I had a great experience interviewing with OpenGov. Regardless of the outcome, I walked away with a very positive impression of the company and its team.
Interview questions [1]
Question 1
System Design How would you about designing a file service? ex Dropbox
My recruiters, Judith and Manuela were great. I was thrown off by the interview question in the coding round. The question itself was easy; I had clarified with the recruiter that the interview would focus on JavaScript. Since OpenGov's tech stack uses TypeScript, I assumed JavaScript would be applicable in the interview. However, when the interview began, it turned out to be an OOP problem in Java. I asked if I could use JavaScript or Python, but he declined. I believe this negatively impacted my score, even though he mentioned he was ultimately looking for my "thought process." I get pretty nervous during technical interviews, but I felt I had the correct thought process throughout the interview, the slight deviation in programming language in an interview setting caused me to overthink and ultimately led me to fail an otherwise easy interview question.