Senior Software Engineer 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 63% positive. To compare, the company-average is 63.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 25 days to get hired, when considering 19 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 Senior Software Engineer according to 19 Glassdoor interviews include:
Skills test: 21%
Phone interview: 20%
Group panel interview: 18%
One on one interview: 14%
Background check: 11%
Presentation: 7%
Personality test: 4%
Other: 4%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 4 weeks. I interviewed at OpenGov (Buenos Aires) in Sep 2023
Interview
The interview process was one of the most transparent that I had. Even though it was long, every step was very valuable for me and for the company, which gave to me more clarity on the projects that I might be involved. Recruiting team supported me in all the journey, keeping me updated before and after each interview with clear feedback. As I'm fullstack it required 2 technical interviews for FE and BE. Then Cultural and Architectural as well.
Nothing to complain, great work Opengov.
Interview questions [1]
Question 1
Q: Why OpenGov? Having many options in the market, Why would you like to work with us?
Q: How do you identity as Problem Solver? Taking needed time to find the best approach and dig into every details, or pragmatic offering a quick solution with next steps on how to continue improving it.
Process: 1) HR Interview 2) Director of Engineering Interview 3) Systems Design Interview 4) In Person AI Coding Challenge 5) VP of Engineering Interview.
Before the In Person AI Coding Challenge, I was told that was going to be the last stage. After it, I was ghosted for a week and when I was contacted again, I was told about the need to meet with the VP of Engineering. They were late to that interview and it felt rushed. Received rejection email couple of days later
Interview questions [1]
Question 1
What are you looking for in your next role?
How do you use AI in your day to day?
I applied online. I interviewed at OpenGov (Boston, MA) in Apr 2026
Interview
My experience with OpenGov was very disappointing due to a lack of professionalism and communication throughout the hiring process. The recruiter was highly responsive and persistent when scheduling interviews and requesting information, but once the interviews were completed on their end or they no longer need you, communication stopped entirely.
The interview process itself felt disorganized, with unclear expectations and coordination issues. Despite having what I believed were positive interviews and receiving encouraging feedback during the process, I was ultimately ghosted without any update, rejection, or explanation regarding the outcome.
While I understand that hiring decisions can change, candidates deserve timely and transparent communication. Being left without any follow-up after investing significant time and effort in multiple interviews reflects poorly on the company's recruiting practices.
I applied through a staffing agency. I interviewed at OpenGov (Pune)
Interview
The interview process felt theoretical and lacked engagement, leaving me uninspired midway through. The questions emphasized abstract concepts without clear context or motivation, even after I asked for clarification.
For instance, in a search bar exercise, the interviewer focused heavily on testing approaches: "Why did you choose this method? What are the different ways to test it? Do you remember the syntax for writing test cases?" In today's AI-assisted development landscape, the emphasis on memorizing syntax seems outdated and disconnected from practical engineering workflows.
Overall, it didn't reflect real-world problem-solving for a senior role.