Jamf Interview Questions
& Process

It was a pretty smooth interview process. I started with a recruiter phone screen, then went through a couple more interview stages. These included a behavioural chat with the hiring manager, and then a technical interview with another manager and some of the senior folks on the team.

The interview process at Jamf had three main parts: first, a chat with the recruiter, then an interview with the hiring manager, and finally, a case presentation for the manager and channel director. It felt like there might have been another step after that. The recruiter was nice and easy to talk to, but the rest of it felt like way too much and not very personal or understanding. The interviewers seemed a bit cold, and they didn't really try to make it a comfortable experience, which is a bummer considering how much time and effort candidates have to put into preparing. One thing I've noticed in tech recruiting generally, and this might or might not be the case at Jamf, is that people who get referred sometimes get a leg up. Referrals can give candidates insider info on how things work, what's expected, or even clues for case studies, making it unfair for those without referrals. I can't say for sure if that happened here, but it's something to think about if a company wants to be fair in hiring. Also, when I presented the case, I was told I didn't focus enough on onboarding or explain why the customer was in their situation. These details weren't clearly laid out in the instructions, so it was tough to nail their expectations. The company says it's forward-thinking and has strong values, but the interview process didn't really match that vibe. It felt stiff, too focused on everyone being the same, and not as creative or inclusive as I'd hoped. It seemed more about fitting their specific mold than appreciating different ways of thinking. Honestly, I think they could make the process simpler to ease the pressure on candidates. A little more warmth would be great (not even a smile)—acknowledging the work candidates put in and making sure everyone has the same info to keep things fair. Jamf has a good reputation, but the hiring experience didn't quite live up to their stated progressive values.

The interview journey with Jamf was really smooth. It started with a chat with a really great Sr. Corporate Recruiter who asked about my background and talked about Jamf's benefits. I was upfront about being in final stages with another company. The next day, I heard back from Jamf about moving forward to an interview with the hiring manager, which I was excited about because Jamf's mission and values really resonated with me. The hiring manager shared insights into Jamf's projects, challenges, and how my role could help address them. She was professional and explained the next steps clearly, including who I might meet next, making me feel like I could make a real contribution. That same night, I actually put together a mock-up of solutions for some of the discussed issues in Confluence, ready to present to the directors. Sadly, the next day I found out they were moving forward with other candidates. Despite that, the interview experience itself was fantastic – informative, professional, and quick. Jamf's transparency was unmatched; they followed up promptly, avoiding the typical waiting game, which I really appreciated as it meant not going back to square one.

The interview process had 3 rounds including the phone screen. All rounds were fine, except for some details concerning the final panel. They were nice but asked a lot of questions that seemed to be setting up for failure. I ended up getting a shortlisted rejection. Very odd as they were only asking for 1 year of experience in multiple toolsets in the initial job description while the panel interviewers were clearly asking mid-level to senior related questions. The panelists also mentioned that the initial job description included more than just FedRAMP standards as it is a general cybersecurity engineering position.