Detailed execution plan
8-week company-switch preparation plan
Use this as your weekly operating rhythm. Each week should produce something visible: notes, code, reports, a CI run, or an interview story. That gives you proof, not just preparation.
Week 1
Testing fundamentals refresh
- Revise SDLC, STLC, test levels, test types, severity vs priority.
- Practice designing test cases for login, cart, payment, upload, and search.
- Prepare 2 examples where you found important bugs through risk thinking.
Week 2
Automation framework depth
- Build or polish one Playwright/Selenium mini framework with POM.
- Add fixtures, test data, screenshots, traces, and reusable assertions.
- Write a short architecture explanation you can speak in 90 seconds.
Week 3
Coding and debugging practice
- Practice Java/Python/JS basics used in automation: arrays, maps, strings, OOP.
- Write utilities for random data, date formatting, retries, and API helpers.
- Debug one intentionally flaky test and document the root cause.
Week 4
API testing
- Create API tests for CRUD, auth, negative cases, schema validation, and chaining.
- Compare Postman collection tests with code-based API automation.
- Prepare an answer for UI vs API automation trade-offs.
Week 5
CI, Docker, reports
- Add GitHub Actions/Jenkins pipeline to run tests on PR and schedule.
- Publish HTML/JUnit/Allure reports and upload screenshots/traces as artifacts.
- Know how to explain parallel runs, retries, and failure triage.
Week 6
Performance and security awareness
- Write a basic k6/JMeter script and read p95, p99, throughput, and error rate.
- Revise OWASP basics: auth issues, injection, IDOR, XSS, CSRF, rate limiting.
- Prepare where performance/security testing fits in your QA process.
Week 7
Resume and stories
- Convert responsibilities into outcome bullets with numbers and business impact.
- Prepare STAR stories for flakiness, conflict, production bug, deadline, ownership.
- Record yourself explaining your current framework and improve weak spots.
Week 8
Mock interviews and applications
- Run two mock interviews: one technical, one behavioral.
- Apply with tailored resume keywords from each JD.
- Keep a rejection/feedback log and turn repeated misses into study tasks.
Phase 1
Testing foundation
Core concepts every interviewer will probe regardless of tech stack
Testing pyramid & types
Must
unitintegratione2e
Explain the pyramid, why you don't invert it, and where your 2yr experience falls in each layer.
Test case design techniques
Must
BVAequivalencepairwise
Boundary value analysis, equivalence partitioning, decision tables. Interviewers love asking you to design tests on the spot.
SDLC & STLC
Must
agilescrumshift-left
Where testing fits in agile sprints, definition of done, shift-left testing philosophy.
Bug lifecycle & defect management
Must
Jiraseveritypriority
Severity vs priority, writing a good bug report, states from open to closed. Have a real example ready.
Test coverage metrics
High
line coveragebranchmutation
What coverage means, what it doesn't guarantee, and how your team tracks it today.
Risk-based testing
High
impactprobabilityscope
How to prioritise which areas to automate and test first based on business risk, not just code coverage.
Regression, smoke & sanity strategy
Must
smokesanityregression
Know what runs after every build, before release, and after hotfixes. Be ready to explain how you choose a lean smoke suite.
SQL & database validation
High
joinsCRUDtransactions
Practice SELECT, JOIN, GROUP BY, basic inserts/updates, and validating backend state after UI/API actions.
Basic coding for automation interviews
Must
stringsarraysOOP
Revise loops, collections, exception handling, classes, inheritance, and small utility functions used inside test frameworks.
Phase 2
Framework depth
Hands-on coding and tool-specific questions interviewers will whiteboard
Selenium / Playwright internals
Must
WebDriverCDPpage objects
How Playwright differs from Selenium under the hood. CDP, auto-waiting, contexts. Page Object Model pattern implementation.
Locator strategies
Must
XPathCSSaria
CSS vs XPath trade-offs, using aria roles, data-testid attributes, and why you should avoid brittle locators.
Test framework patterns
Must
POMscreenplayfixture
POM vs Screenplay pattern. Fixtures and setup/teardown lifecycle in Pytest, JUnit, or Jest. Be ready to code one.
Handling async & waits
Must
explicit waitauto-waitflakiness
Hard sleeps vs explicit waits vs Playwright's auto-wait. How to debug and eliminate flaky tests — companies hate them.
Parameterization & data-driven tests
High
@pytest.mark.parametrizeDDT
Data-driven testing with external fixtures (JSON, CSV), parametrize decorators, and how to scale test data without duplication.
Mocking & stubbing
High
mockstubspy
When to mock vs stub vs spy. How to mock network requests in Playwright/Cypress. Dependency injection for testability.
Visual regression testing
Nice
PercyApplitoolsscreenshot diff
Pixel diffing tools, when visual tests are worth it, and how to handle dynamic content like dates or ads.
Mobile test automation
Nice
AppiumXCUITestEspresso
Appium architecture, how it wraps native drivers. Cross-platform vs native. Good to mention even if not hands-on.
Authentication & session handling
Must
cookiestokensstorage state
Avoid logging in through the UI for every test. Learn token setup, saved browser state, role-based users, and session cleanup.
Test data management
Must
fixturesfakercleanup
Create unique data, seed known states, clean up safely, and prevent parallel tests from fighting over the same account/order.
File upload, download & email flows
High
uploaddownloadmailtrap
Know how to automate document uploads, verify downloaded files, and test OTP/reset-email flows using test inboxes.
Flaky test triage playbook
Must
tracesscreenshotsroot cause
Classify failures as product bug, test bug, data issue, environment issue, or timing issue. Have one strong debugging story.
Phase 3
CI/CD & tooling
Modern companies expect you to own your pipeline end to end
Running tests in CI pipelines
Must
GitHub ActionsJenkinsGitLab CI
YAML pipeline config, triggering on PR/push, parallelising test runs, fail-fast strategies, artifact publishing.
Docker for test environments
Must
Dockerfilecomposeselenium-grid
Running headless browsers in containers, Selenium Grid with Docker Compose, keeping test infra reproducible.
Test reporting & observability
Must
AllureHTML reportJUnit XML
Integrating Allure or HTML reporters, publishing test results to dashboards, Slack/Teams notifications on failure.
Version control & code review practices
Must
GitPR workflowbranch strategy
Feature branches, naming conventions for test code, reviewing others' automation code — you're part of the dev workflow now.
Test parallelisation
High
shardingworkersPlaywright
Playwright sharding, pytest-xdist, matrix strategies in CI. Reducing suite time from 20min to 5min is a great story.
Cloud test platforms
Nice
BrowserStackSauce LabsLambdaTest
Cross-browser cloud execution, when to use vs self-hosted grid, and cost trade-offs. Common at product companies.
Environment configuration & secrets
Must
env varssecretsprofiles
Run the same suite against dev, QA, staging, and prod-like environments without hardcoded URLs or credentials.
Quality gates in CI
High
PR gatethresholdblocking
Define when builds should fail: smoke failure, critical e2e failure, API contract break, coverage drop, or high flakiness.
Browser/device matrix planning
High
ChromeFirefoxmobile web
Explain how you decide which browsers/devices run in every PR, nightly, and release pipeline based on user data.
Phase 4
API & performance testing
Differentiate yourself — many 2-year QAEs are weak here
REST API testing fundamentals
Must
HTTP methodsstatus codesheaders
CRUD semantics, auth methods (Bearer, API key, OAuth2), response validation, JSON schema checks.
API testing with code
Must
requestssupertestRestAssured
Writing API tests in code (not just Postman), chaining calls, reusing auth tokens, asserting nested JSON structures.
Contract testing
High
Pactconsumer-drivenschema
Consumer-driven contract testing with Pact. Huge in microservices shops — shows you think beyond UI-level tests.
Performance & load testing basics
High
k6JMeterLocust
Difference between load, stress, and soak tests. Running a simple k6 script, reading p95/p99 response times, VU ramp-up.
GraphQL API testing
Nice
queriesmutationsschema
Testing GraphQL endpoints, introspection, handling variables — increasingly common at product companies.
Security testing awareness
Nice
OWASPZAPauth flaws
Basic OWASP top-10 awareness, SQL injection test cases, using OWASP ZAP in a pipeline. Great differentiator.
Postman to automation migration
High
PostmanNewmancode suite
Know when Postman/Newman is enough and when to move API checks into a maintainable coded test framework.
Negative API scenarios
Must
4xxvalidationauthz
Test missing fields, invalid types, expired tokens, unauthorized access, duplicate requests, and malformed payloads.
Accessibility testing basics
Nice
WCAGaxekeyboard
Run axe checks, verify keyboard navigation, labels, contrast, focus order, and explain what automation can and cannot catch.
Phase 5
Behavioral & process
Switching companies means selling your thinking, not just your tools
Automation ROI story
Must
metricstime savedimpact
Quantify what your automation did: X tests that previously took Y hours now run in Z minutes. Every company wants this story.
Framework you built / inherited
Must
architecturetrade-offsdecisions
Describe your framework top-down: folder structure, runner, reporting, CI integration. What would you do differently now?
Handling disagreement with developers
Must
STARconflictcollaboration
Scenario when dev pushed back on a bug you raised. Keep it factual: data, impact, resolution. Don't villainise anyone.
Why you're switching companies
Must
motivationgrowthnarrative
Pull vs push framing: talk about what you're running toward (scale, domain, stack) not what you're escaping. Rehearse this.
Estimating test scope
High
test plancoverage analysis
"How long would it take to automate login + checkout?" Walk through discovery, edge cases, flakiness budget, CI time target.
Questions to ask the interviewer
High
flakiness ratetest ownershipcoverage goal
Ask about flakiness rate, who owns test failures, current CI time, and whether devs write their own unit tests. Shows maturity.
Resume bullet proof points
Must
ATSimpactnumbers
Every major resume claim should have a number, tool, scale, or result you can defend in an interview.
STAR story bank
Must
ownershipfailuredeadline
Prepare stories for production bug, missed deadline, flaky suite, difficult stakeholder, learning new tool, and improving process.
Notice period, salary & offer narrative
High
HRCTCnegotiation
Practice calm answers for current CTC, expected CTC, notice period, competing offers, and why now is the right time to move.
Practice lab
Hands-on drills to prove interview readiness
Do these as timed exercises. Keep your code in one public or private repo so you can revise it before interviews and speak from real work.
UI automation drill
- Automate login, logout, invalid login, and role-based access checks.
- Use Page Object Model with clear locators and no hard sleeps.
- Add screenshots/traces on failure and one reusable assertion helper.
- Run the suite headless and headed with environment-driven base URL.
Interview answer to prepare: why your locator strategy will survive UI changes.
API automation drill
- Create tests for create, read, update, delete, unauthorized, and validation errors.
- Chain API calls without relying on hardcoded IDs from previous runs.
- Validate status code, headers, response body, schema, and database state if possible.
- Separate request builders, test data, and assertions.
Interview answer to prepare: which checks belong at API level instead of UI level.
CI/CD drill
- Create a pipeline that installs dependencies, runs lint/tests, and publishes reports.
- Upload screenshots, videos, traces, and JUnit XML as build artifacts.
- Add matrix or sharding for browser/project-level parallel execution.
- Document how you would handle flaky tests without hiding real defects.
Interview answer to prepare: what should block a PR and what should run nightly.
Framework explanation drill
- Draw your framework architecture: tests, pages, fixtures, data, utils, reports, CI.
- Explain how a new test is added from requirement to pipeline execution.
- Name three trade-offs you made and what you would improve next.
- Prepare a short walkthrough of one meaningful test from your repo.
Interview answer to prepare: how your framework reduces maintenance cost.
Answer bank
Questions you should rehearse out loud
For each question, prepare a 60-90 second answer with one real example. Keep it specific: system, tool, problem, action, result.
Technical questions
- How do you decide what to automate and what not to automate?
- How do you debug a flaky test that passes locally but fails in CI?
- Explain your automation framework architecture from scratch.
- What is the difference between implicit wait, explicit wait, and auto-waiting?
- How would you test a payment flow without charging real money?
Scenario questions
- A release is tomorrow and 20 regression tests fail. What do you do?
- A developer says your bug is not valid. How do you handle it?
- Your suite takes 45 minutes. How would you reduce it to 10 minutes?
- Requirements are unclear but testing must begin. How do you proceed?
- Production has a bug missed by automation. What changes after RCA?
HR and switch questions
- Why are you leaving your current company?
- What kind of QA role are you looking for next?
- Tell me about a time you took ownership beyond assigned work.
- What is your biggest weakness as a QA automation engineer?
- Why should we hire you over another 2-year QA candidate?
Bonus tips
Company-switch specific advice
Research their stack before round 1
Check the job posting, LinkedIn engineers, and GitHub if they have public repos. Mention their actual tools by name — it signals you did your homework.
Bring a coding sample
A GitHub repo with a small Playwright or Pytest suite using POM, fixtures, and CI config goes further than any verbal explanation. Link it in your resume.
Lead with outcomes, not tools
Don't say "I used Selenium." Say "I reduced regression cycle time from 3 days to 40 minutes by building a Selenium suite that ran in CI." Tools are the how.
Practice live coding tests
Write a page object for a login form, add a parametrised test, and handle a network intercept — all under 20 minutes. Time yourself at home.
Position yourself as a dev collaborator
Companies switching to test ownership by devs still need someone who bridges the gap. Show you can review dev-written tests and mentor, not just write your own.
Have a flakiness war story
Every QA team has flaky tests. Describe one you diagnosed and fixed — timing issue, environment instability, test data collision — and what you put in place to prevent it.