
mHelpDesk Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Which role are you interviewing for?
7 roles · 13 reportsCandidate interview experiences
First-hand accounts from people who interviewed at mHelpDesk.
Product Designer
First, an HR person called me. Then, I spoke with the head of the department. After that, I came in for an in-person interview where I met with several different people. The HR person I interviewed with was really responsive, kind, and personable. The head of the department I was interviewing with was the same, and they answered all my questions quickly and kindly too. The CEO, an incredibly inspiring woman, also spent a good amount of time chatting with me. Everyone involved really went the extra mile to talk with me and be available. Honestly, it's the best interview process I've ever been a part of.
- Can you describe how you manage disagreements with developers and engineers?
Operations Lead
I was contacted on LinkedIn by HR and the hiring manager to talk about the position. We had a phone call where they told me the basics of what they were looking for. Then, another call was set up with the Head of Engineering to discuss the role more deeply. That call was about 45-50 minutes long, covering the environment, the job duties, and some general questions about my current job and experience. I asked about the salary and exact title, but they didn't give me an answer, saying HR should have covered that. After checking with HR, I still didn't get a clear answer on pay, just that it was 'competitive,' and the title was undecided. A few days later, HR called to set up an in-person interview at their HQ. I went in and met the Head of Engineering, the CIO, and some engineering team members. It was a one-on-one with the Head of Engineering and then a panel interview with the CIO and the team. The interview took over 2 hours, with typical IT questions and more specific details about what they needed for the role. It was a good, professional interview, and I felt all my questions were answered. The Head of Engineering said I'd hear back in a few days about the next steps. A week passed with no word, so I contacted HR. They said the Head of Engineering would reach out soon and asked how I felt about the interview. I never heard back from mHelpDesk, so I assume the job was filled. The whole process took over 3 weeks. It wasn't a bad experience overall, but since the company is small and growing, their process and communication could be better.
- Can you tell me about your experience monitoring and troubleshooting servers?
- What technologies have you worked with?
- Describe your process for setting up a new server.
Director of Product Management
The interview process was really professional and respectful. They kept their word and everyone I talked to was genuinely interested in discussing the role. It was a mix of phone chats, one-on-one meetings, and group interviews. They didn't ask basic resume questions, which felt like they actually read my resume beforehand. Everyone seemed to get the company's goals, challenges, and what this job is all about. The questions made me think and required some prep, touching on the job itself, how I'd fit the company, and the overall culture. Every person on the panel was someone I would be working with, and they were all keen on finding the right fit.
- Can you share some mobile apps you love and explain what made them successful?
- What apps do you find yourself using most often, and what aspects of their design or functionality do you think they executed well?
- Tell me about your favorite mobile applications and what, in your opinion, they did exceptionally well.
Software Engineer
The whole interview process was pretty smooth and I liked how fast they answered my questions. It started with a phone screen, then a phone technical interview with some engineers. After that, I went to their HQ for an on-site where I met with different people from the company, like engineers, PMs, and directors, in either one-on-one or group settings. They also had me do a project beforehand, which I then had to talk about during the on-site. Finally, there was a last HR call to wrap things up.
- Can you explain what a deadlock is?
- Could you describe dependency injection on the Android client side?
- What are the differences between single and factory definitions?
mHelpDesk Interview Questions
Quoted word for word from mHelpDesk interview reports.
“What are the differences between single and factory definitions?”
Read reports →“Can you explain what a deadlock is?”
Read reports →“Could you describe dependency injection on the Android client side?”
Read reports →“What apps do you find yourself using most often, and what aspects of their design or functionality do you think they executed well?”
Read reports →“Are you familiar with Mhelpdesk?”
Read report →“Can you share some mobile apps you love and explain what made them successful?”
Read report →“Describe your process for setting up a new server.”
Read report →“Are you familiar with AWS?”
Read report →“Tell me about your favorite mobile applications and what, in your opinion, they did exceptionally well.”
Read report →Formats, difficulty and experience
Across all 13 mHelpDesk interview reports.