SDET / AI QA salary progression (India, 2026):

Fresher (0-2 yrs)      ₹4–10 LPA
Mid-level (2-5 yrs)    ₹12–22 LPA
Senior (5-8 yrs)       ₹25–40 LPA
Principal / Manager    ₹60+ LPA

AI Test Engineer specifically:
Entry (2-4 yrs)        ₹30–55 LPA (highest demand role)

The gap between manual-only testers (₹3–6 LPA)
and specialised QA engineers (₹25–55 LPA) has
never been wider. Specialisation is the single
biggest salary lever in QA right now.

Market growth signals (India, 2026):

- Global automation testing market:
  $40B (2026) → $79B (2031), ~14% CAGR

- QA engineering positions grew 17% in 2 years,
  outpacing developer roles at 9%

- 77% of teams now use AI for routine QA tasks
  (flaky script fixes, test generation)

- 80%+ of Indian organisations exploring
  autonomous AI agents in workflows

- India needs 2M+ AI-savvy QAs by 2027
  (current talent pool is nearly empty)

The market isn't shrinking. It's splitting.
Routine work is being automated. Specialised
work is being paid more than ever.

// Live coding task — a common interview format in 2026
// "Automate login + checkout with assertions."

// A strong answer shows:
// 1. Locator strategy (role-based preferred)
// 2. Proper waits (auto-waits in Playwright)
// 3. Meaningful assertions
// 4. Clean structure

import { test, expect } from '@playwright/test';

test('login and add item to cart', async ({ page }) => {
  await page.goto('https://saucedemo.com');

  await page.getByPlaceholder('Username').fill('standard_user');
  await page.getByPlaceholder('Password').fill('secret_sauce');
  await page.getByRole('button', { name: 'Login' }).click();

  await expect(page).toHaveURL(/inventory/);

  await page.getByRole('button', { name: 'Add to cart' })
    .first()
    .click();

  await expect(page.locator('.shopping_cart_badge'))
    .toHaveText('1');
});

// What separates a strong answer from a weak one:
// Weak: hard-coded sleeps, CSS selectors, no assertions
// Strong: auto-waits, role-based locators, clear assertions

// The framework architecture question — how to answer it

// Interviewer: "Walk me through a framework you built."

// Strong answer structure:
//
// 1. STRUCTURE
//    - Page objects for each page (POM)
//    - Fixtures for setup/teardown
//    - Test data separated from test code
//    - Config (environments, credentials) in one place
//
// 2. SCALE
//    - Parallel execution with sharding
//    - Retry strategy for genuinely flaky tests only
//    - Test tagging (@smoke, @regression)
//
// 3. RELIABILITY
//    - Auto-waits instead of sleeps
//    - Locator strategy (role > CSS)
//    - CI pipeline with fail-fast
//
// 4. OBSERVABILITY
//    - Traces on failure (Playwright trace viewer)
//    - HTML reports + Allure
//    - Slack alerts on main-branch failures
//
// 5. TRADE-OFFS
//    - What you chose NOT to build
//    - Where you compromised and why
//
// The best candidates talk about decisions, not just tools.

Weekly study plan (12-15 hrs):
Mon 1.5h — Programming (Java/TypeScript)
Tue 1.5h — Playwright / API testing
Wed 1.5h — Framework architecture
Thu 1.5h — CI/CD + parallel execution
Fri 1h   — Review + notes
Sat 4h   — Project work
Sun 2h   — AI testing exploration / rest

Consistency beats intensity.
In 12 months, you can move from
a declining role to a growing one.

Portfolio checklist for 2026 QA roles:
- GitHub repo with a clean Playwright framework
- Two projects:
  1. UI + API test suite for a demo app
  2. A small AI-testing experiment
     (hallucination check, bias detection)
- Each project with a clear README
- One project running in CI (GitHub Actions)
- A blog post or writeup on:
  - "How I test AI outputs"
  - "Why I use Playwright over Selenium"
- LinkedIn profile with the right keywords
  (SDET, Playwright, AI Testing, CI/CD)

Show the projects in interviews —
talk through decisions, not just tools.