CyberArk India SDET Interview: Rounds, Questions and Preparation

What the job involves

An SDET (Software Development Engineer in Test) at a global tech product company builds and maintains automated test frameworks, writes code to validate APIs, UI, and backend services, and partners with developers to catch defects early in the CI/CD pipeline. Day to day work includes writing test automation in Java or Python, debugging failures in distributed systems, and improving test coverage for security, performance, and reliability. Freshers in this role are expected to code confidently, think about edge cases, and understand how testing fits into modern product delivery.

Role and technical knowledge

1. 1

   What is the difference between a QA engineer and an SDET?

   Explain that an SDET writes production-quality automation code, builds test frameworks, and contributes to CI/CD, while a QA engineer may focus more on manual test execution and process. Mention that SDETs are expected to code daily.

2. 2

   How would you test a login API that returns a session token?

   Cover positive and negative cases: valid credentials, wrong password, missing fields, SQL injection attempts, rate limiting, token expiry, and response codes. Mention validating the token format and that it cannot be reused after logout.

3. 3

   Explain the Page Object Model and why it is used in Selenium automation.

   Describe how each page is represented as a class with locators and actions, which reduces duplication and makes tests easier to maintain. Mention that changes to the UI require updates in one place only.

4. 4

   What is the difference between smoke, sanity, and regression testing?

   Define smoke as a quick build verification, sanity as focused testing of a specific fix or feature, and regression as full testing to ensure new changes did not break existing functionality. Give a small example for each.

Practical scenarios and coding

1. 5

   Write a function to find the first non-repeating character in a string. What test cases would you write for it?

   Code a solution using a hash map or array, then list edge cases: empty string, all repeating characters, single character, spaces, and special characters. Show that you think about both implementation and test coverage.

2. 6

   You join a team with no automated tests. How would you start building a test automation framework?

   Start by identifying critical user flows, choosing a language and tools the team already uses, setting up version control and CI, and writing a few high-value tests first. Mention maintainability, reporting, and gradually expanding coverage.

3. 7

   A test passes on your machine but fails in the CI pipeline. How do you debug it?

   Check environment differences such as browser versions, screen resolution, time zones, and test data. Review CI logs and screenshots, reproduce in a similar environment, and add waits or stable locators if timing or UI issues are the cause.

4. 8

   How would you test a file upload feature that accepts PDFs up to 10 MB?

   Cover valid PDF upload, file exactly 10 MB, file over 10 MB, wrong file type, empty file, special characters in filename, and concurrent uploads. Mention checking server-side validation and error messages.

Behavioural and situational questions

1. 9

   Tell me about a time you found a bug that others missed. How did you handle it?

   Use the STAR method: describe the situation, the bug you found, how you reproduced and reported it with clear steps, and how the fix improved the product. Highlight attention to detail and communication.

2. 10

   Describe a project where you had to learn a new tool or technology quickly.

   Pick a real college or internship project, explain what you needed to learn, how you learned it, and the result. Show curiosity, self-learning, and ability to apply new knowledge under deadlines.

3. 11

   How do you handle disagreement with a developer who says a bug is not reproducible?

   Stay professional, provide detailed reproduction steps, logs, screenshots, and environment details, and offer to pair with the developer to reproduce it together. Focus on solving the issue rather than proving who is right.

4. 12

   Why do you want to work as an SDET at a product company like CyberArk India?

   Connect your interest in coding and quality with the company's domain, such as security or identity management. Mention wanting to build automation that protects users and to grow technically in a product-focused environment.

HR and company fit

1. 13

   What do you know about our company and the products we build?

   Research the company's core products, such as privileged access management or identity security, and mention recent news or values. Show that you understand the domain and why quality matters in security software.

2. 14

   Where do you see yourself in three years as an SDET?

   Talk about deepening automation and coding skills, learning more about security testing or performance testing, and eventually mentoring juniors or owning a test framework. Keep it realistic and aligned with the company's growth.

3. 15

   Are you comfortable working in a hybrid or office-based setup in India?

   Answer honestly and positively, showing flexibility. Mention that you value in-person collaboration for learning in the early career stage if that is true for you.

4. 16

   What are your salary expectations for this fresher role?

   Say that you are open to the company's standard fresher compensation and more focused on learning and growth. If pressed, give a reasonable range based on market research for SDET freshers in India.