Ping Identity Qa Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Ping Identity.
Ping Identity
Associate QA Engineer
Entry Easy Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Phone screen Take home Onsite
Interview formats
Technical Coding Behavioral
The hiring process started with an aptitude/IQ test, it had 50 questions and was not difficult but I was told not to spend too much time on each. After that, there was a phone interview with HR from head office, where they asked about my resume and it was a quick process with fast replies. Then I had another phone interview with the local team lead, this one had simple questions mainly about web security. Following that, I had a remote assignment using Junit. The final stage was an on-site panel interview that lasted about 2.5 hours with 3 Devs, 3 QAs, and the team lead. They asked questions about my remote assignment and resume, and everyone was very relaxed and friendly during this part. The whole process took about a month, and they were very fast with responses.
Confirmed questions2 questions
- Can you explain the difference between HTTP and HTTPs?
- What do you know about Oauth?
Ping Identity
Senior QA Manager
Senior Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Recruiter call
Interview formats
Technical Behavioral
I applied online and after a few days, I was invited to take an online cognitive assessment. Days later, a recruiter reached out saying they wanted to proceed with the next interviews based on my test results. I gave them my availability. A few days later, I got a message saying, 'I will reach out to you at 4pm.' The scheduled call never happened. When I contacted the recruiter, they said they had emailed earlier to let me know the position was moving in a different direction. I'm really disappointed with the lack of transparency in the recruitment process and the wasted time with emails and tests if the position might be closed or changed.
Confirmed questions1 question
- What is your availability to speak?
Ping Identity
Senior QA Engineer
Senior Average Positive experience Decline offer 3 rounds
Interview process
Take home Technical screen Panel
Interview formats
Technical Coding Behavioral
They sent over two tests before the actual interview, one assessing personality and the other an IQ test. The interview itself was split into three parts: first, a chat with the tech manager and a QA Engineer, then a technical task, and finally a long panel interview that lasted 3 hours with two people interviewing me each hour. The technical task involved writing unit tests in Java for a custom application that had some bugs intentionally placed within it. This was quite interesting for a QA role, especially since unit tests are typically written by developers.
Confirmed questions1 question
- Is it possible to have multiple assertions within a single automated test?
Ping Identity Qa Engineer Interview Questions
Quoted word for word from Ping Identity interview reports.
“Can you explain the difference between HTTP and HTTPs?”
Read reports →“Is it possible to have multiple assertions within a single automated test?”
Read reports →“What do you know about Oauth?”
Read reports →“What is your availability to speak?”
Read reports →“Describe a situation where you had to bypass your management structure to get approval to advance an initiative.”
Read report →“Can you tell me about your experience with test automation tools, frameworks, and security testing?”
Read report →Formats, difficulty and experience
Across all 7 Ping Identity interview reports.