Test Automation Engineer
Test Automation Engineers design, write, and maintain the automated test suites that gate every production deployment. Day-to-day they author UI tests in Selenium, Playwright, or Cypress; build mobile test packs in Appium for Android and iOS; write API and contract tests in REST Assured or Postman/Newman; run load profiles in k6 or JMeter; and wire all of it into Jenkins, GitLab CI, or GitHub Actions pipelines. In India this is the most common growth path out of manual QA — the role pays 1.5-2x what a manual tester earns and is hired heavily across TCS, Infosys, Cognizant, Wipro on the services side and at product companies like Razorpay, Flipkart, Swiggy, PhonePe where SDET (Software Development Engineer in Test) titles command product-engineering salaries. The role demands real coding skill (Java, Python, JavaScript), system thinking about flaky tests, and constant negotiation with developers who would rather ship than wait for green builds.
Overview
Test Automation Engineers design, write, and maintain the automated test suites that gate every production deployment. Day-to-day they author UI tests in Selenium, Playwright, or Cypress; build mobile test packs in Appium for Android and iOS; write API and contract tests in REST Assured or Postman/Newman; run load profiles in k6 or JMeter; and wire all of it into Jenkins, GitLab CI, or GitHub Actions pipelines. In India this is the most common growth path out of manual QA — the role pays 1.5-2x what a manual tester earns and is hired heavily across TCS, Infosys, Cognizant, Wipro on the services side and at product companies like Razorpay, Flipkart, Swiggy, PhonePe where SDET (Software Development Engineer in Test) titles command product-engineering salaries. The role demands real coding skill (Java, Python, JavaScript), system thinking about flaky tests, and constant negotiation with developers who would rather ship than wait for green builds.
A Day in the Life
Reach the office (services: TCS / Infosys / Cognizant in Bengaluru / Hyderabad / Pune / Chennai; product: Razorpay / Flipkart / Swiggy / PhonePe Bengaluru), or log in if remote; check overnight CI run results in Jenkins / GitHub Actions.
Daily 15-min standup with the engineering pod (devs + SDETs) — share automation progress for the current sprint, flag any flake-driven blockers.
Investigate 3-6 flaky test failures from the overnight run: re-run, check timing assumptions, inspect screenshots and Allure / Playwright traces, file fixes or quarantine the test with a comment and tracking ticket.
Write or update 4-8 automated test cases for the current sprint's feature work — Selenium Java / Playwright TypeScript / Cypress, typically 2-4 hours of focused scripting.
Lunch with the engineering pod; informal sync on an upcoming feature's testability or a recurring CI infra issue.
Review 2-3 pull requests from devs with eye toward testability — missing test IDs, race conditions, untestable async flows; leave PR comments before merge.
Pair with a developer for 30-60 min on a tricky integration test, an API contract test in REST Assured / Postman, or to debug a CI pipeline failure blocking the team's deploy.
Maintain or extend the framework — refactor a Page Object, upgrade Playwright / Selenium / Appium versions, add a new utility for a common pattern (auth, file upload, payment flow, mobile geolocation).
Run the scheduled regression suite (web + mobile + API), triage red builds, escalate true product bugs to engineering, ignore known flakes with comments.
Update Jira / Azure DevOps with sprint test status, flake counts, and coverage metrics; quick chat with the engineering lead on release readiness.
Performance test work (k6 / JMeter) — once a week, run a load profile against the staging environment and report p95 / p99 trends.
Wind down — kick off overnight CI nightly run, push any WIP framework PRs, leave for the day. Release weeks add 1-2 evening hours and occasional weekend on-call for CI outages.
Common Mistakes
7- ⚠️Staying in services automation past year 4Why: Services SDET ceilings sit around ₹15-22L for senior ICs; meanwhile product-company peers hit ₹35-50L by the same tenure. The longer you stay, the harder the product-company switch becomes.Instead: Use years 1-3 at services for fundamentals + certifications; year 3-4 jump to a product company or US captive; expect a 60-100% salary jump on the switch.
- ⚠️Treating record-and-playback tools as 'real' automationWhy: Selenium IDE, Katalon Recorder, Testim record-mode produce brittle tests that break on every UI change; engineers who lean on these never learn framework design and stall at junior-IC roles.Instead: Hand-code your tests in Java / Python / TypeScript from day one; use record-mode only to discover locators, never to ship test code.
- ⚠️Ignoring CI/CD and infrastructureWhy: SDETs who can't read or fix a Jenkins / GitHub Actions pipeline get bottlenecked by DevOps; meanwhile SDETs who own their own CI pipelines become indispensable.Instead: Learn enough YAML, Docker, and at least one CI tool deeply (Jenkins or GitHub Actions); own the test-CI pipeline for at least one project before year 3.
- ⚠️Skipping API and contract testing in favor of UI testsWhy: UI tests are the slowest, flakiest, lowest-value tier of the pyramid; teams that lean on UI tests have brittle suites and slow releases. SDETs who only know UI testing are over-supplied.Instead: Build the test pyramid honestly: 60-70% unit + API + contract, 20-30% integration, 10-15% UI. Learn REST Assured / Postman / pact / Karate; these compound the most.
- ⚠️Refusing to learn coding deeply enoughWhy: SDETs who can't read Java / Python / TypeScript at a senior-dev level get treated as second-class engineers and lose negotiating leverage with feature devs.Instead: Spend 4-6 hours a week on real programming (LeetCode-easy / mediums, system design, design patterns, language idioms); aim to be technically stronger than the median feature dev on your team by year 3.
- ⚠️Quarantining flaky tests without ever fixing themWhy: Flake quarantine is necessary in the short term but corrosive long-term; suites with >5% quarantined tests lose engineering trust and stop catching real bugs.Instead: Run a weekly 'flake budget' meeting — every quarantined test gets a deadline; suites are never allowed above 2-3% quarantined at any time.
- ⚠️Treating SDET as a stepping stone you don't fully commit toWhy: SDETs who half-do the role while preparing to switch to SDE never build framework depth and end up middling at both careers.Instead: Either fully commit to SDET (own framework strategy, build a public portfolio, aim for Senior / Principal SDET), or do a focused 6-12 month DSA grind and switch to SDE cleanly. Don't dabble.
Salary by Indian City (Mid-level total cash comp)
6| City | Range |
|---|---|
| Bengaluru | ₹14-25 LPA |
| Hyderabad | ₹13-23 LPA |
| Pune | ₹10-20 LPA |
| Delhi NCR (Gurugram/Noida) | ₹11-22 LPA |
| Chennai / Mumbai | ₹8-18 LPA |
| Remote / International contract | ₹20-45 LPA |
Notable Indians in this career
5Communities + forums
7- Ministry of TestingWeb + SlackLargest global testing community; very active India chapter; conference (TestBash) talks, in-depth courses, and a Slack with senior SDETs / QA leaders worldwide.
- Indian Testing Conference / SeleniumConf IndiaIn-person + webAnnual in-person testing conferences in India; the most credible networking venue for senior SDET / QA-architect roles and India-specific tooling discussion.
- Free Applitools-sponsored automation courses by leading practitioners (Angie Jones, Joe Colantonio, Andy Knight); strong India learner base, certifications add weight to a resume.
- TestProject (legacy) / TestGuild podcastWeb / podcastJoe Colantonio's TestGuild podcast and blog; weekly long-form interviews with senior SDETs and tool vendors; useful for staying current on tooling trends.
- Global subreddits with strong India presence; honest discussion of services vs product, manual-to-automation switch, and tooling religion (Cypress vs Playwright, Selenium vs WebdriverIO).
- Naveen AutomationLabs Discord / Rahul Shetty communityDiscord / SlackIndian SDET training communities; active mentorship from trainers and senior SDETs, especially useful for career switchers from manual QA.
- Official Playwright (Microsoft) and Cypress Discord communities; maintainers answer questions; the fastest way to stay current with modern web-test tooling.
What to read / watch / follow
10- Foundations of Software Testing — ISTQB Certificationbookby Dorothy Graham, Erik van Veenendaal, Isabel Evans, Rex BlackThe official ISTQB Foundation textbook; required reading for Indian services-company SDET roles and the foundation for most senior-level test reasoning.
- Selenium WebDriver 3 Practical Guide / Selenium with Javabookby Boni Garcia / Mukesh OtwaniPractical, India-focused references for Selenium-Java work; Mukesh's book mirrors his YouTube content and is one of the most-used resources in Indian SDET upskilling.
- Continuous Deliverybookby Jez Humble & David FarleyThe definitive book on CI/CD and deployment pipelines; senior SDETs who haven't internalized this book underperform on framework-architecture and shift-left decisions.
- Agile Testing / More Agile Testingbookby Lisa Crispin & Janet GregoryStandard references for agile QA practice — test pyramid, in-sprint testing, BDD; senior SDETs at product companies are expected to know this material.
- The Art of Software Testingbookby Glenford Myers, Tom Badgett, Corey SandlerClassic test-design text; the boundary-value, equivalence-partitioning, and risk-based testing chapters are still load-bearing in every modern test plan.
- Test Automation Patternsbookby Seretta Gamba & Dorothy GrahamA pattern-language for framework design — page object, screen object, screenplay, robot pattern; senior SDETs reference this when designing or refactoring frameworks.
- Naveen AutomationLabs (YouTube)video channelby Naveen KhuntetaThe single most-watched Indian automation channel; covers Selenium, Playwright, REST Assured, Appium, Java, design patterns; great for a structured 6-12 month upskill path.
- TestGuild podcast / Joe Colantonio newsletterpodcast / newsletterby Joe ColantonioWeekly senior-SDET interviews and tooling roundups; the easiest way to keep aware of new tools (Mabl, Testim, KaneAI, Diffblue) and industry shifts.
- Playwright docs + Microsoft Playwright YouTubedocs / videoby Microsoft Playwright teamFirst-party documentation is unusually good; the official YouTube has senior-developer-grade tutorials on trace, codegen, fixtures — load-bearing for any modern web SDET.
- Angie Jones blog + talksblog / videosby Angie JonesOne of the most respected senior SDET voices globally; speaks at every major test conference; her talks on test-design and career growth shape how modern SDET orgs run.
Daily Responsibilities
7- Write or update 4-8 automated test cases for the current sprint's feature work — typically 2-4 hours of focused scripting in Selenium / Playwright / Cypress.
- Investigate 3-6 flaky test failures from the overnight CI run: re-run, check timing assumptions, inspect screenshots and traces, file fixes or quarantine the test.
- Review pull requests from devs with eye toward testability: missing test IDs, race conditions, untestable async flows — leave PR comments before merge.
- Pair with a developer for 30-60 min on a tricky integration test or to debug a CI pipeline failure that's blocking the team's deploy.
- Run scheduled regression suite (web + mobile + API), triage red builds, escalate true product bugs to engineering, and ignore known flakes with comments.
- Attend sprint standup, refinement, and one ad-hoc sync with product or devs about test coverage for an upcoming feature; push back on un-testable specs.
Advantages
- Cleanest stepping-stone out of manual QA in India — most automation engineers earn 1.6-2x what they did as testers within 18 months of switching, with a clear 5-year path to ₹20L+.
- Genuine remote and hybrid options at product companies — Razorpay, Postman, Zerodha, GitLab India, and most US captives hire SDETs as fully remote pan-India.
- Strong job security: every product company that ships software needs CI gates, and automation skill compounds across stacks (a Selenium expert is a Playwright expert in 3 weeks).
- Lower interview-prep tax than pure SDE roles — system design rounds are framework-design rounds, and DSA expectations are typically lighter (sliding window / two pointers level, not graph DP).
- Predictable hours compared to feature-team SDEs — most automation work is sprint-aligned, with on-call only for CI-pipeline outages, not user-facing 2 AM pages.
Challenges
- Salary ceiling is real at IT services companies — TCS / Infosys / Cognizant SDET ladders cap around ₹15-22L for senior individual contributors; product companies are where the ₹40L+ band lives.
- Automation work is constantly devalued by management who underestimate maintenance cost — flaky-test debt and framework rot can consume 30-50% of an engineer's week if not actively managed.
- Tooling churn: Selenium → Cypress → Playwright in five years; Appium native vs Appium 2 vs WebdriverIO; the half-life of a test framework is 3-4 years, and re-platforming work is rarely glamorous.
- Dev-vs-QA culture friction is common — many engineering teams treat SDETs as second-class citizens who slow down releases, even when the SDET is technically stronger than the developer.
- Career transitions out are narrower than for SDEs — moving from SDET to feature engineering requires either re-interviewing through DSA loops or a strong internal advocate.
Education
6- Required (most common): B.Tech / B.E. / BCA / B.Sc IT — the standard route into Indian IT services QA pools at TCS, Infosys, Cognizant, Wipro, Capgemini, where automation upskilling happens 6-18 months into the job.
- Strong alternatives: MCA or M.Sc (Computer Science) — directly accepted for SDET roles at product companies; the second degree is often what gets a manual tester promoted into automation.
- Self-taught path: a strong GitHub with 3-5 framework projects (Page Object Model in Selenium/Java, Playwright + TypeScript suite, Appium mobile pack, k6 performance scripts) is increasingly accepted at product startups and remote-first companies.
- Certifications that hire: ISTQB Foundation Level (table-stakes for services jobs), ISTQB Advanced Test Automation Engineer, Selenium WebDriver certifications, AWS Certified Cloud Practitioner for cloud-test-infra roles.
- Indian bootcamp routes: Edureka, Simplilearn, NareshIT, Naveen AutomationLabs YouTube + paid course — work for career switchers from manual QA, but only when paired with a real portfolio.