Quality Engineering Lead · Test Architecture · Automation

I architect quality systems that make release confidence measurable.

I connect test strategy, automation, CI/CD and product risk so organisations can make evidence-based release decisions. Web · Mobile · API · Data · User experience.

View case studies ↓ View resume ↗
8+
Years experience
3
Web · Mobile · API
5
Product domains
3
Architecture ownership roles
Anita Pal, Quality Engineering Lead specialising in test architecture and automation
The Happy-Path SkepticEvery release claim needs evidence.
// about

I turn product risk into a quality operating model.

I'm a Quality Engineering Lead specialising in test architecture and automation. I shape QA operating models, suite strategy, framework boundaries, CI/CD execution and release governance across browser, native mobile, API and data layers.

I held architecture ownership across Ingersoll Rand, Vitaccess and freelance engagements. At Airmeet, I contributed QA, maintainability and testability inputs to architecture trade-off discussions and extended the existing Cypress framework; at Kalinga, I maintained and contributed to an established Selenium framework.

Across industrial IoT, healthcare, event technology, e-commerce and payments, I connect requirement risk, test design, automation, observability and production evidence while keeping user experience central to every release decision.

Open to work · Bangalore · Remote-ready
01

Test architecture and governance

Defined QA operating models, automation boundaries, reusable framework layers, suite taxonomy and CI/CD execution across three architecture-ownership roles.

02

Architecture through collaboration

Translate product risk, testability, maintainability and delivery constraints into practical trade-offs with QA peers and engineering, product and DevOps partners.

03

Quality leadership

Own the path from requirement analysis and risk planning through suite governance, defect investigation, mentoring and release sign-off.

// selected case studies

How I engineer confidence.

Three examples of turning product risk into repeatable evidence across web, mobile and production debugging.

CASE 01 · WEB + API

A release-ready Playwright platform

Designed an automation foundation for an industrial IoT customer portal with complex roles, devices and microservice dependencies.

Engineering decision

Separated business flows, page components, test data and API utilities so the suite could grow without duplicating setup or selectors.

Evidence

Combined browser assertions with REST and database validation, RBAC coverage, Docker execution and GitLab CI feedback.

Quality outcome

Created one maintainable path from story review to repeatable release evidence across UI and backend state.

PlaywrightTypeScriptRESTGitLab CIDocker
CASE 02 · NATIVE MOBILE

One strategy for iOS and Android

Built mobile coverage for patient, event and payment journeys where device behavior, network traffic and backend data all mattered.

Engineering decision

Used WebdriverIO with Appium while keeping platform-specific XCUITest and UiAutomator2 behavior explicit instead of hiding meaningful differences.

Evidence

Validated real devices and simulators, BrowserStack coverage, API traffic through Charles Proxy and resulting data consistency.

Quality outcome

Connected user-visible mobile behavior to the network and data layers needed to diagnose failures confidently.

AppiumXCUITestUiAutomator2BrowserStackCharles Proxy
CASE 03 · PRODUCTION DEBUGGING

Proving a “network error” was not network

Investigated an intermittent browser error without source access and narrowed the failure domain using independent evidence.

Investigation

Correlated an empty Network timeline with a caught client-side TypeError that occurred before any backend request was constructed.

Reasoning

Separated what the evidence proved from plausible implementation hypotheses, avoiding a misleading root-cause claim.

Quality outcome

Produced actionable recommendations for error classification, state validation and telemetry that would reduce diagnosis time.

DevToolsNetworkRuntimeRoot CauseObservability
// experience

Where I've done the work.

Click any role to read what I actually built and the impact it had.

QA leadership and delivery: owned the Customer Portal QA lifecycle, sprint priorities, resource distribution, risk reporting and final QA sign-off for global production releases.
QA process from scratch: established the STLC, master test plans, release-risk documentation, bug workflows and smoke, sanity, functional and regression suites.
Agile participation: contributed estimates, scope and acceptance-criteria inputs during sprint planning, and facilitated Daily Standups when scheduled through the shared rotation.
Framework architecture and GitLab CI/CD: architected and built the Playwright hybrid framework and headless execution pipelines as an IC, including commit-triggered and scheduled nightly runs.
Peer enablement: supported QA peers with Playwright hybrid-framework concepts, scripting practices, manual test strategy and debugging.
Emergency release: led a one-week risk-based E2E regression for a critical e-commerce patch, covering carts, dealer-specific pricing and checkout receipts.
Customer Portal: validated multi-tenant registration, dealer onboarding, service reminders and role-based customer/dealer journeys.
Industrial IoT: verified Helix telemetry, uptime dashboards, sensor charts, machinery alarms, specifications, manuals, service history and serial-number-based configurations.
RBAC and data: used predefined query templates in the database-management UI to verify segregation for Admin, Executive and Dealer roles.
Middleware and cloud: validated MuleSoft payload transformation and synchronization across Salesforce Experience Cloud, GCP, OCI and Service Point integrations.
Salesforce LWC automation: built Playwright regression coverage using auto-waiting and resilient locators for asynchronously loaded Lightning Web Components.
API automation: authored Playwright APIRequestContext checks for connectivity data and service-microservice schema compliance.
Shift-left and PR verification: reviewed Figma designs during grooming and validated isolated Preview Apps before main-branch merges.
Delivery tools: managed defects and sprint testing in Jira and maintained test knowledge and case libraries in Confluence.
PlaywrightPlaywright API GitLab CI/CDSalesforce LWC MuleSoftGCP / OCI FigmaJira / Confluence RBACQA Leadership
QA process engineering: established the platform QA lifecycle under QA leadership, including clinical-data risk plans and Azure DevOps defect workflows.
Pod quality leadership: prioritized sprint cards, distributed QA assignments and provided day-to-day release-readiness sign-off.
Azure and GitHub CI/CD: maintained Azure Pipeline triggers for automated web and mobile execution on GitHub pull requests.
Automation architecture: architected and coordinated Cypress web and WebdriverIO/Appium mobile layers, using UiAutomator2 and XCUITest locators for the React Native application.
Requirements and test design: reviewed clinical surveys and acceptance criteria in Notion and managed smoke and regression suites in Azure Test Plans.
Healthcare data validation: verified DynamoDB and PostgreSQL read/write integrity for patient updates, caregiver variables and disease-burden records.
Communication workflows: tested scheduled patient/caregiver emails with Litmus, including responsive templates, links, localization and time-zone triggers.
Authentication: tested mobile OTP handshakes, expiry boundaries, network timeouts and registration retry restrictions.
Accessibility and security: automated WCAG 2.1 checks with Cypress-axe and performed baseline traffic and input validation using Burp Suite.
Web automation: maintained Cypress JavaScript regression for the real-world-evidence analytics dashboard.
API and logs: investigated JSON payloads and authorization headers through DevTools/Postman and isolated backend failures using Azure diagnostic streams.
Release coverage: validated localization, Preview Apps and BrowserStack matrices across web, Android and iOS, and coordinated KT in Notion.
Cypress / Cypress-axeWebdriverIO AppiumAzure Pipelines DynamoDB / PostgreSQLBrowserStack Burp SuiteLitmus NotionAzure Test Plans
Ownership growth: transitioned from the earlier client engagement into a direct Airmeet role with independent ownership of core modules, strategy and releases.
Interim QA leadership: led the QA function for one month during the QA Lead's absence, managing release schedules, resource allocation and stakeholder communication.
Streaming and accessibility: led closed-caption testing and coordinated cross-platform streaming validation across OBS Studio, YouTube Live and Facebook Live.
API and network analysis: inspected REST, WebSocket and GraphQL traffic through DevTools and Swagger, including schemas, parameters, authorization headers and payloads.
Recording pipeline: verified Firebase processing nodes and Mux recordings for playback stability, audio/video synchronization and output quality.
Localization: validated translations, regional date/time and currency settings without layout distortion or text truncation.
Release and incident ownership: coordinated cross-pod regression and rotational on-call releases; investigated failures through New Relic and ELK/Kibana in AWS.
Infrastructure: led multi-region AWS Data Center clustering, scaling and failover validation and tracked delivery in Shortcut.
Architecture collaboration: participated in framework architecture trade-off discussions, contributing QA, maintainability and testability inputs; then added JavaScript modules to the existing Cypress hybrid framework.
Data: seeded Postman event payloads and verified Amazon RDS, DynamoDB and Firebase records for booths, sponsors, metadata and user roles.
Product coverage: tested Social Lounge, speed networking, breakout rooms, templates, sponsor booths, subscription migrations and feature flags.
Analytics and email: validated GTM/GA events and Litmus transactional-email rendering, dynamic tokens and client compatibility.
Compatibility and shift-left: used BrowserStack across web/mobile and reviewed Figma designs during grooming to identify UI risks early.
Agile and enablement: managed sprint planning, test cases, regression sheets and KT sessions for cross-functional colleagues.
Cypress / JavaScriptBrowserStack Postman / SwaggerFirebase / Mux AWS / RDS / DynamoDBNew Relic / Kibana OBS StudioLitmus GTM / GAQA Leadership
Client engagement: joined the Airmeet platform through Alpha & Beta Innovation before transitioning to the direct Airmeet role.
Functional coverage: executed functional, regression and integration testing across attendee registration, breakout rooms, chat moderation and related event workflows.
Compatibility: performed BrowserStack cross-browser and cross-device validation for supported attendee and host journeys.
API and data: validated REST responses, status codes and targeted SQL/NoSQL data consistency for attendee, session and registration records.
Defect lifecycle: logged, triaged and tracked production-impacting issues with reproducible evidence and root-cause observations.
Agile delivery: participated in sprint planning, story discussions, reviews and retrospectives, contributing estimates, test scope and delivery risks.
Functional TestingRegression BrowserStackREST API SQL / NoSQLDefect Triage
Test automation architecture: architected fit-for-purpose solutions through Appium and framework POCs, selected scalable approaches and built reusable utilities for client codebases.
QA practice from scratch: partnered with a client to establish the QA function, global testing standards, release workflow and technical mentorship.
WordPress development and testing: developed, maintained, debugged and validated client websites as an IC, including functionality, layout and performance fixes.
Testing execution: combined structured test-case runs and exploratory testing across web and mobile products through crowdsourced-testing platforms.
EdTech: independently tested a live online video-tutoring product, including synchronization, interactive views and multi-user chat.
Commerce and subscriptions: tested checkout, payment-app transactions and subscription upgrades, downgrades and renewals across success and failure paths.
Mobile diagnostics: used real devices and Charles Proxy for network inspection, API checks and root-cause debugging.
Delivery infrastructure: introduced repeatable documentation, defect standards and lightweight GitHub CI hooks for clients without existing QA metrics.
Appium POCsCharles Proxy Exploratory TestingEdTech Payment AppsMusic & Gaming WordPressGitHub QA Practice Setup
Test design: analysed specifications and customer requirements to build structured functional suites across the product lifecycle.
Automation: maintained Selenium WebDriver, Java and TestNG regression tests within an existing data-driven POM framework.
CI/CD: monitored Jenkins execution and build-stability reports and escalated automation failures to senior engineers.
Embedded IoT: validated device data capture, firmware connectivity and reporting accuracy against specifications.
Database: wrote targeted SQL queries for CRUD, search, contact and transactional data-consistency checks.
Web and API: executed cross-browser UI testing and verified REST status codes, response bodies and device/backend schema consistency.
Agile: participated in sprint planning, basic story estimation and Daily Standups.
Defects: documented reproducible bugs with environment details, logs and lifecycle status.
SeleniumJava TestNGSQL
// skills

The full stack of quality.

Automation frameworks
Playwright Appium Cypress Selenium WebdriverIO TestNG JUnit Playwright API Mocha Chai
Languages
JavaScript TypeScript Java HTML CSS
Mobile & iOS automation
Appium XCUITest UiAutomator2 WebdriverIO Real devices BrowserStack Charles Proxy
AI & test generation
Playwright MCP Claude AI GitHub Copilot Applitools Resilient locators LLM-assisted QA Comet
API & data
Cypress API Postman Swagger SQL PostgreSQL MongoDB DynamoDB ELK Stack
Testing types
E2E API Visual Performance Security Accessibility (WCAG) Mobile Cross-browser RBAC Database
CI/CD & tooling
Jenkins Azure DevOps GitHub Actions Docker Git Jira TestRail BrowserStack Burp Suite Lighthouse
// ai & testing

AI, with engineering judgment.

I use AI to accelerate discovery and analysis while keeping assertions, risk decisions and final validation grounded in evidence.

Playwright MCP

AI that actually uses the browser

At Ingersoll Rand, I used Playwright MCP to inspect the live application and accelerate scenario and script drafting from the real DOM — with every generated step reviewed before entering the suite.

LLM Prompting

Test cases from user stories

Using Claude AI and GitHub Copilot with structured prompts to generate BDD scenarios, edge cases, and negative test paths directly from acceptance criteria — reviewed and refined, not blindly accepted.

Resilient Locators

Selectors aligned with user intent

Playwright's role, label and text locators replace fragile DOM chains with accessible contracts. AI can suggest candidates; maintainers still decide which locator best expresses test intent.

Visual AI

Applitools for pixel-perfect releases

Integrated Applitools Eyes into Cypress suites at Vitaccess — visual checkpoints caught layout regressions that functional tests miss, across a healthcare platform where UI accuracy directly affects patient trust.

Playwright● Cypress● Selenium● Playwright API● Playwright MCP● Claude AI● GitHub Copilot● Applitools● Jenkins● Azure DevOps● Docker● BrowserStack● Appium● Burp Suite● PostgreSQL● Playwright● Cypress● Selenium● Playwright API● Playwright MCP● Claude AI● GitHub Copilot● Applitools● Jenkins● Azure DevOps● Docker● BrowserStack● Appium● Burp Suite● PostgreSQL●
// qa field notes

Small frictions. Useful lessons.

A growing collection of observations from testing, product flows and the job-search journey. Each note starts with a real moment worth investigating.
// the story of testing 3 chapters open

Every product is a door. Let’s test what happens when we open it.

Follow Riya and Sam as one ordinary classroom door becomes a complete software system. No heavy definitions at the beginning—just curiosity, evidence and one useful question at a time.

RiyaThe door opened. It works!
SamBut what was it supposed to do?
Begin the story See the chapters
Click the door to begin investigating
Story progress 3 / 26
// contact

Let's build quality together.

Open to Quality Engineering Lead, Test Architect, QA Lead and Test Automation Architect opportunities. Bangalore-based, remote-ready, immediately available.

Available now · Immediate joiner
Email er.anitapal@gmail.com
↗
Resume View quality engineering resume
↗
Writing QA Field Notes · on this site
↗
GitHub github.com/anietaa
↗
LinkedIn linkedin.com/in/anita-pal2k26
↗