Need help? Reach out to us
Back to library

Indian unicorns and high-growth startups

CDSL India QA Engineer Interview: Rounds, Questions and Preparation

For QA Engineer roles at companies like CDSL India

Share with friends

Preparing together? Send them this role's questions.

https://www.cynchrony.in/library/cdsl-india-qa-engineer

What the job involves

QA Engineers at Indian unicorns and high-growth startups test software products for functionality, performance, and security before release. They write and execute test cases, log bugs, and work closely with developers to ensure high-quality user experiences. In fast-paced environments, they also automate repetitive tests and participate in agile ceremonies.

Role and Technical Knowledge

  1. 1

    What is the difference between verification and validation in software testing?

    Verification checks if the product is built correctly (reviews, inspections), while validation checks if the right product is built (actual testing). Give examples like specification review vs. executing test cases.

  2. 2

    Explain the bug life cycle with a real example from a startup context.

    Cover stages: New, Assigned, Open, Fixed, Retest, Verified, Closed, Reopened. Use an example like a payment failure bug in a fintech app and how it moves through stages.

  3. 3

    What are the key differences between smoke testing and sanity testing?

    Smoke testing checks critical functionalities after a new build to decide if further testing is possible. Sanity testing checks specific fixes or minor changes. Mention they are both narrow but smoke is broader and done on initial builds.

  4. 4

    How would you test a login page of a high-traffic Indian e-commerce app?

    List test cases: valid/invalid credentials, SQL injection, password masking, remember me, forgot password, CAPTCHA, session timeout, and load testing for peak sale days. Show structured thinking.

Practical Scenarios

  1. 5

    You find a critical bug just before a release. What steps do you take?

    Immediately log the bug with clear steps, screenshots, and severity. Inform the lead and developer, assess impact, and suggest a go/no-go decision. Emphasize communication and risk analysis.

  2. 6

    How do you decide which test cases to automate in a startup with limited time?

    Prioritize repetitive, high-risk, and regression tests. Avoid automating unstable features. Mention ROI, maintenance cost, and using tools like Selenium or Cypress.

  3. 7

    A developer says your bug is not reproducible. How do you handle it?

    Provide detailed environment details, steps, screenshots, and logs. Try to reproduce on different devices or data. Collaborate calmly and consider if it is environment-specific.

  4. 8

    How would you test an API that returns user transaction history for a fintech app?

    Check status codes, response schema, data accuracy, authentication, pagination, error handling, and performance. Use Postman and mention SQL to verify backend data.

Behavioural and HR

  1. 9

    Why do you want to work as a QA Engineer in a high-growth startup like CDSL India?

    Show passion for quality, fast-paced learning, and ownership. Connect to the company's domain (e.g., financial market infrastructure) and mention adaptability.

  2. 10

    Describe a time you found a mistake in your own work and how you fixed it.

    Use STAR method. Highlight honesty, attention to detail, and process improvement. Example: missed a test case, then created a checklist to avoid recurrence.

  3. 11

    How do you handle pressure when multiple releases are planned in a short time?

    Talk about prioritization, risk-based testing, clear communication, and using automation for regression. Show calmness and teamwork.

  4. 12

    Where do you see yourself in 3 years in a QA role?

    Mention growing into automation, performance testing, or QA lead. Align with company needs and show commitment to learning.

Tools and Process

  1. 13

    What is the difference between a test plan and a test strategy?

    Test plan is document with scope, approach, resources, schedule for a specific project. Test strategy is high-level, organization-wide approach. Mention they are often confused.

  2. 14

    How do you write a good bug report? What fields do you include?

    Include title, description, steps to reproduce, expected vs actual, severity, priority, environment, attachments. Emphasize clarity and conciseness.

  3. 15

    What is the role of SQL in testing? Give an example query you might use.

    SQL helps verify data integrity, backend updates, and reports. Example: SELECT * FROM users WHERE user_id = 101; to check if a new user was inserted correctly.

  4. 16

    Explain how you would use JIRA in your daily QA work.

    Mention creating and tracking bugs, linking to test cases, updating status, and using dashboards for reports. Show familiarity with agile boards.

Coding round

QA Engineer interviews usually include a coding round. Practise planning the solution out loud, then review code the AI writes from your plan, in Python, Java, C++, C or JavaScript.

Ready to try it for real?

Take a timed test or talk through a mock interview for this role, then see your scores.

This is practice material for QA Engineer roles, written with AI. It is not a list of questions CDSL India or any other company has asked.