J'ai postulé via un recruteur. Le processus a pris 4 jours. J'ai passé un entretien chez OpenGov en mars 2025
Entretien
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.
Autres retours d’entretien d’embauche pour un poste comme Software Engineer II chez OpenGov
J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez OpenGov (Atlanta, GA) en avr. 2025
Entretien
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.
Questions d'entretien [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.