Sr. QA Automation Engineer

→ The test strategy: a pyramid covering unit, contract, API, E2E, performance and security, with quality gates in Jenkins.

→ A Playwright framework (TypeScript, Java or Python) for UI and API tests: fixtures, storageState auth, parallel runs, trace viewer and Allure reporting.

→ Sync API testing: REST, gRPC and GraphQL, covering schemas, auth, negative paths and contract tests (Pact).

→ Async communication testing: RabbitMQ and SQS flows and webhooks. Validate eventual consistency, ordering, idempotency, retries and DLQs using correlation IDs, never fixed sleeps.

→ Load and resilience with JMeter: load, stress, soak and spike tests with distributed runs. Analyse p95/p99 latency, throughput and bottlenecks with developers using observability tools. k6 or Gatling where they fit better.

→ Security and VAPT: OWASP Top 10 and API Top 10 using Burp Suite, OWASP ZAP, Nmap, Nikto and SQLMap. Work with external pentesters, triage findings and verify fixes.

→ AI-based testing: AI-assisted test generation, Playwright MCP and Copilot for authoring, self-healing locators, visual AI (Applitools-style), and testing LLM-powered features.

→ Manual testing: exploratory and risk-based testing, BVA, equivalence partitioning, decision tables, state transitions, and UAT support.

→ Service virtualisation and test data: WireMock, LocalStack and Testcontainers.

→ Pipeline guardrails: contract checks that block a deploy when an API or event schema breaks (Pact can-i-deploy, OpenAPI diff), accessibility checks with axe-core in Playwright against WCAG 2.2 AA, and a flaky-test register with quarantine and a tracked flake rate.

→ Lead the practice: mentor the QA engineer, own the defect lifecycle and report quality metrics.