Okta Test Automation Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Okta.
Okta
Software Development Engineer in Test
Staff Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Background check
Interview formats
Coding Technical Behavioral
Started with an HR screening, then a coding round, and finally a third round that included Quality DNA, Coding, and a Managerial assessment. The coding questions were mostly about manipulating strings, and the Quality DNA part focused on various real-time testing approaches.
Confirmed questions4 questions
- Can you elaborate on different testing approaches, including scenarios?
- Can you elaborate on different testing approaches, including edge test cases?
- Can you elaborate on different testing approaches, including functional testing?
Okta
Senior Software Engineer in Test
Senior Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Background check
Interview formats
Technical Coding Behavioral
I got referred and then immediately got an email for a recruiter screening. After a 30-minute talk about my past experience, they mentioned a 1-hour technical screening, followed by three more technical rounds and a hiring manager round if I passed the screening. A few days later, they set up the 1-hour technical screening, which started with a 5-minute intro and then went straight into a coding exercise where I had to screen share. After that, we did some Selenium coding, and it ended with me asking questions for about 10 minutes.
Confirmed questions5 questions
- Tell me about a LeetCode easy string manipulation problem.
- How do you locate elements using Selenium?
- What's your experience with basic CI/CD?
Okta
Software Development Engineer in Test II
Mid Average Positive experience No offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Coding System Design
The interview panel really drilled down on DevOps stuff, checking both what I know and what I've actually done. They asked a lot about cloud, especially AWS (EC2, S3, IAM) and how it all fits together for big systems. We also talked about CI/CD, like Jenkins and GitHub Actions, and how making things automatic speeds up deployments. I had to explain Docker for containers, Kubernetes for organizing them, and how tools like Prometheus and Grafana help with monitoring. They also brought up networking, Linux commands, and how DevOps works with agile. A few questions were about data structures and algorithms to see how I tackle system problems.
Confirmed questions8 questions
- Can you tell me about your experience with DevOps, both in theory and practice?
- Could you elaborate on AWS services like EC2, S3, and IAM and how they fit into building scalable systems?
- How do CI/CD pipelines, using tools like Jenkins or GitHub Actions, improve deployment efficiency?
Okta Test Automation Engineer Interview Questions
Quoted word for word from Okta interview reports.
“Find all parents of a node in a graph.”
Read reports →“What is Kubernetes used for in terms of container orchestration?”
Read reports →“Can you explain the difference between authentication and authorization?”
Read reports →“How do you locate elements using Selenium?”
Read reports →“How do monitoring tools like Prometheus and Grafana function?”
Read report →“Can you explain how to determine if a number is prime?”
Read report →“How do DevOps principles complement agile development methodologies?”
Read report →“Could you state your version of the Chrome browser WebDriver?”
Read report →“Which Linux commands are particularly useful in a DevOps environment?”
Read report →Formats, difficulty and experience
Across all 12 Okta interview reports.