30-Day QA Automation Interview Preparation Plan India 2026

Have a QA automation interview in 30 days? Following a structured 30-day plan that covers Selenium core concepts (Week 1), framework design (Week 2), API testing and advanced topics (Week 3), and mock interviews with your portfolio (Week 4) results in 70% interview success rate for candidates who complete it consistently. This is the exact plan used by engineers who cracked TCS, Infosys, Mphasis, and Freshworks QA automation roles.

Week 1: Core Selenium and Manual Testing Fundamentals

Day 1-2: Selenium locators — master all 8 locator strategies with practice

• ID, Name, Class, TagName, LinkText, PartialLinkText, XPath, CSS Selector
• Write relative XPath for 10 different web elements on any website
• Practice: dynamic XPath using contains(), starts-with(), text()

Day 3-4: WebDriver actions and synchronization

• Implicit wait vs Explicit wait vs Fluent wait — write code for all 3
• Actions class: hover, right-click, drag-and-drop, double-click
• Handle alerts, iframes, multiple windows/tabs

Day 5-6: TestNG framework

• All TestNG annotations: @Test, @BeforeMethod, @AfterMethod, @BeforeClass, @DataProvider
• testng.xml: define suites, tests, groups, parallel execution
• Priority, groups, dependsOnMethods usage

Day 7: Manual testing concepts review

• SDLC vs STLC, test design techniques, bug lifecycle
• Write 5 test cases for login page on paper (common live interview task)

Week 2: Framework Design and Advanced Concepts

Day 8-9: Page Object Model

• Implement complete POM for a 3-page application: login, home, checkout
• PageFactory and @FindBy annotation usage
• Separation of test data from page objects

Day 10-11: Data-driven testing and reporting

• Read test data from Excel using Apache POI
• @DataProvider with multiple rows
• ExtentReports: add screenshots on failure, custom logs

Day 12-13: Framework architecture questions

• Explain your framework design in 3 minutes (practice out loud)
• Hybrid framework: combining data-driven + keyword-driven
• What makes a good automation framework? (maintainability, reusability, reporting)

Day 14: Git and version control basics

• git add, commit, push, pull, branch, merge
• Resolve a merge conflict (practice with two branches)
• GitHub Actions: what CI/CD means for QA automation

Week 3: API Testing and Advanced Topics

Day 15-16: REST API fundamentals

• HTTP methods: GET, POST, PUT, PATCH, DELETE and when to use each
• Status codes: 200, 201, 400, 401, 403, 404, 500
• JSON structure: objects, arrays, nested JSON

Day 17-18: RestAssured or Postman

• RestAssured: given/when/then pattern, header assertions, body extraction
• Postman: collection runner, environment variables, assertions in test scripts
• Write 5 API tests for a public API (JSONPlaceholder or Petstore)

Day 19-20: Cross-browser and parallel testing

• Run same test on Chrome, Firefox, Edge using TestNG parallel config
• WebDriverFactory pattern for cross-browser support
• Selenium Grid concepts (even if you have not used it — know the theory)

Day 21: Behavioral and HR questions

• Why QA automation? (Your personal story — 2 minutes max)
• Biggest challenge in automation you solved
• How do you handle a flaky test? What is your process?

Week 4: Mock Interviews and Portfolio Polish

Day 22-23: Live coding practice

• Write Selenium scripts from scratch on paper or blank IDE (no autocomplete)
• Practice common live coding tasks: login script, table data extraction, dropdown selection

Day 24-25: Portfolio walkthrough

• Prepare 3-minute walkthrough for each GitHub project
• Know every line of code in your POM project — interviewers ask why you made specific choices
• Have GitHub open and portfolio running during interview

Day 26-27: Company-specific preparation

• Research the company tech stack — Java or Python? Selenium or Playwright?
• Check LinkedIn for people with the same role at this company
• Prepare 3 questions to ask the interviewer (show genuine interest)

Day 28-30: Final mock interviews

• Conduct 2-3 mock interviews with a friend or record yourself
• Answer all Week 1-3 questions without notes
• Review your weakest topics one more time

Top 15 QA Automation Interview Questions You Must Know

1. What is the difference between Selenium WebDriver and Selenium RC?
2. Write XPath for a button with text “Submit” that is the third button on the page.
3. What is the difference between implicit wait and explicit wait?
4. Explain Page Object Model with an example.
5. How do you handle dynamic dropdowns in Selenium?
6. What is TestNG and why is it preferred over JUnit for Selenium?
7. How do you run tests in parallel using TestNG?
8. How do you take a screenshot on test failure?
9. What is the difference between findElement() and findElements()?
10. How do you handle file uploads and downloads in Selenium?
11. Explain your automation framework architecture.
12. What is RestAssured and how do you validate a JSON response?
13. What is the difference between smoke testing and sanity testing?
14. How do you decide which test cases to automate?
15. How do you handle a StaleElementReferenceException?

Frequently Asked Questions

How many hours per day should I study for a QA automation interview?

3-4 hours minimum for 30 days. Split: 1 hour theory review, 1 hour coding practice, 30 minutes portfolio work, 30 minutes mock interview. Consistent daily practice beats marathon weekend sessions — your brain consolidates learning during sleep.

What if I have not built a portfolio before the interview?

Build a minimal portfolio in Week 4 alongside mock interviews. A single Selenium POM project for SauceDemo with 20 tests, CI, and ExtentReports is better than no portfolio. Interviewers understand freshers — they are testing attitude and learning ability more than the size of your project.

How do I prepare for live coding in QA automation interviews?

Practice writing Selenium scripts without IDE autocomplete. Open a blank text editor and write: a login script, a data-driven test, an API test with RestAssured assertions. Do this for 30 minutes daily from Day 1. Muscle memory with code is different from theoretical knowledge.

Which companies have the hardest QA automation interviews in India?

Google and Microsoft have the hardest — including data structures, algorithms, and system design. Razorpay and Freshworks focus on practical Playwright/Selenium coding. TCS and Infosys have the most structured interviews with standard questions. Prioritize your preparation based on which companies you are targeting.