
ManageGo Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at ManageGo.
Software Developer
So I applied and they hit me up to set up a phone interview with the hiring manager. It was pretty standard, they asked about my work history and if I knew the tech stack they needed. After that, they asked me to come in and do a test project. It was a good test, actually, pretty smart way to check people out. I did it at their office and got paid for my time. It took a bit longer than they thought, maybe their time estimate was a little off. Then, a lead dev called me to talk about the project. They decided not to hire me because I wasn't super familiar with NHibernate, which was a big deal for them. They said I should reapply when I'm more solid on the tech stack and we ended on good terms.
- Can you share your previous experience with specific APIs?
Software Engineer
I interviewed with ManageGo back in Sept 2017. The hiring manager and app architect did the interview but they barely spoke English and didn't really know how interviews are done in the West. They made me an offer then, but I said no because they were unprofessional. Then, in March 2018, someone from ManageGo kept pushing me to reconsider. I met with the hiring manager again and we both seemed interested in moving forward. He then asked me to do an on-site software exercise. The exercise involved a software project and a list of features to add. Usually, take-home exercises are either super simple with the goal of seeing if you can make a production-ready app (looking for good design, validation, error handling, unit tests, etc.) or they have lots of functionality and the goal is to see if you can build an end-to-end app, even if imperfect. The code they gave me was messy, and the requirements were vague, so I figured they wanted the second type. Even just to get it working, it took me about 7 hours. To make it production-ready would have taken maybe 3 days. After I finished, I talked to the hiring manager about salary and start date. The next day, the app architect emailed me a code review criticizing my design. I was asked to respond to each point. I basically said, 'Yeah, that's valid, I wasn't building a production app.' Since then, I haven't heard anything. And by the way, doing the exercise at their office meant I saw their workspace - cramped with sales and customer support, which is pretty depressing. Edit: After I wrote this, someone from ManageGo harassed me to remove it. Then they claimed they hadn't decided, and finally sent a rejection email.
- Can you explain what try/catch/finally blocks are?
- Do memory leaks happen in .NET?
- Write a SQL query to find the start and end points of gaps in a sorted integer column.
Software Engineer
The interview experience wasn't the best. The company seemed a bit all over the place and not super ready for the interviews. The person interviewing me didn't seem too thrilled about finding new people. If I had been offered the job, I would've passed.
- Questions about Javascript
- Questions about React
- Questions about Redux
ManageGo Software Engineer Interview Questions
Quoted word for word from ManageGo interview reports.
“Write a SQL query to find the start and end points of gaps in a sorted integer column.”
Read reports →“Do memory leaks happen in .NET?”
Read reports →“Can you explain what try/catch/finally blocks are?”
Read reports →“Questions about HTML”
Read reports →“Questions about Redux”
Read report →“Questions about CSS”
Read report →“Questions about React”
Read report →“Questions about Javascript”
Read report →“They asked about frameworks and other domain knowledge trivia, including old ways of using React.”
Read report →Formats, difficulty and experience
Across all 6 ManageGo interview reports.