Bugcrowd India SDET Interview: Rounds, Questions and Preparation

What the job involves

As an SDET at a global product company or fast-growing security platform, you write code to test software, build automation frameworks, and integrate tests into CI/CD pipelines. You work alongside developers to catch bugs early, improve test coverage, and ensure releases are reliable across web, API, and mobile surfaces. The role blends software engineering with quality advocacy, often including performance, security, and accessibility checks.

Role and technical knowledge

1. 1

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

   A strong answer explains that an SDET writes production-quality automation code, builds frameworks, and works on test infrastructure, while a QA engineer may focus more on manual test execution and process.

2. 2

   How do you decide what to automate and what to test manually?

   Cover factors like frequency of execution, stability of the feature, ROI, and risk. Mention that exploratory, usability, and one-off tests often stay manual.

3. 3

   Explain the test pyramid and how you would apply it in a microservices-based product.

   Describe unit tests at the base, integration and API tests in the middle, and a small number of UI tests at the top. For microservices, emphasise contract testing and API-level coverage.

4. 4

   What is the difference between a stub, a mock, and a fake in testing?

   Define each clearly: stubs return canned answers, mocks verify interactions, and fakes are working lightweight implementations. Give a short example for an API dependency.

Practical automation and coding scenarios

1. 5

   Write a Selenium script in Java or Python to log in to a web application and verify the dashboard title.

   Show use of locators, explicit waits, page object pattern, and assertions. Mention handling of dynamic elements and avoiding hard-coded sleeps.

2. 6

   How would you automate testing a REST API that returns a list of users with pagination?

   Describe using Rest Assured or requests, validating status codes, response schema, pagination parameters, and edge cases like empty pages and invalid tokens.

3. 7

   Your automated test suite takes 45 minutes and fails intermittently. How do you fix it?

   Talk about identifying flaky tests, isolating test data, parallel execution, smarter waits, and splitting smoke versus regression suites.

4. 8

   Given a CSV of test data, how would you run the same test across 100 rows without duplicating code?

   Mention data-driven testing with TestNG DataProvider or pytest parametrize, keeping test logic separate from data, and reporting per-row results.

Testing a real product and debugging

1. 9

   How would you test a password reset flow for a security-focused SaaS product?

   Cover token expiry, one-time use, email delivery, rate limiting, SQL injection in the reset form, and ensuring old passwords stop working.

2. 10

   A bug is reported only in production but not in staging. What is your approach?

   Compare configurations, data, environment variables, and third-party services. Suggest adding logging, reproducing with production-like data, and checking deployment differences.

3. 11

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

   List boundary tests, file type validation, virus scanning, concurrent uploads, error messages, and storage cleanup. Mention both UI and API-level checks.

4. 12

   What would you include in a test plan for a new notification service that sends email and SMS?

   Include functional cases, delivery guarantees, retries, opt-out handling, rate limits, template rendering, and monitoring alerts.

Behavioural and HR questions for freshers

1. 13

   Tell me about a time you found a bug in a college project or internship. How did you handle it?

   Use STAR format: describe the situation, the bug, how you investigated, and what you learned about testing or communication.

2. 14

   Why do you want to work as an SDET instead of a pure developer role?

   Show genuine interest in quality, automation, and preventing defects. Mention that you enjoy coding but also like breaking and improving systems.

3. 15

   How would you handle a developer who says your automated test is wrong and refuses to fix the code?

   Emphasise data, reproduction steps, and collaboration. Suggest pairing, reviewing logs together, and escalating only if needed with evidence.

4. 16

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

   Talk about deepening automation skills, learning performance or security testing, and possibly mentoring juniors or owning a test framework.