Ping Identity Interview Questions
& Process

Had an initial call with the recruitment team about my skills, experience, and salary expectations. Then, I had a call with the head of engineering where we discussed behavioral and some technical aspects, as well as my experiences and skills. The head of engineering mentioned they enjoyed our discussion and would let the recruitment team know about the next stage, but after that, there was radio silence and no replies even after I reached out multiple times.

I recently went through the interview process at Ping Identity. The early stages and the take-home assignment went smoothly. However, after submitting the assignment, communication ceased. I received no feedback, not even a rejection, and my follow-up emails were ignored. This is frustrating because candidates invest significant time and effort, often working after hours, on these tasks. A simple notification would be greatly appreciated. I believe transparency and providing closure are essential in hiring, and I hope companies will prioritize these aspects.

So, my interview process for the Marketing Project Manager gig at Ping Identity was super quick and thorough. I had 4 interviews all in one week: first a phone screen with HR, then I chatted with the Director of Marketing Ops, the Creative Director, and finally the Sr. Director of Marketing Ops and the Director of Digital Strategy. The interviews were pretty average difficulty, and they really dug into my experience with project management tools like Asana and Workfront, how I optimize processes, do automation and capacity planning, and work with creative and digital folks. They also checked for cultural fit and if I was aligned with Ping Identity's vibe. It was all very professional and fast, but it was a bummer the role got reposted right after my last interview while I was waiting to hear back. Overall, a solid and speedy process, but communication after the final interview could've been better.

I went through a 3-round interview process: technical, managerial, and then HR. They really focused on what the job actually required, not just generic stuff. First, there was a recruiter call where they checked my technical skills, work background, and general knowledge. Then, I had to do an offline task: build a webserver from scratch, making sure to set up security and IAM. The second round involved a deep dive into my projects with follow-up questions and scenario-based questions, especially from a customer support angle. The big surprise was a mock customer call with an angry customer and a totally random situation! The third round was with HR, discussing salary, benefits, and when I could start.