Functional Testing
Validate application features, user journeys, business rules and expected system behavior against documented requirements.
Software QA Engineer
Software QA Engineer with 1+ years of professional QA experience testing web applications, payment platforms, and business-critical systems. I specialize in API testing with Playwright automation, validate workflows systematically, and investigate test failures to understand how systems fail in production.
All four public projects use Playwright automation with Page Object Model architecture and GitHub Actions CI/CD integration. Code, tests and results are publicly verifiable and independently auditable.
Software QA Engineer specializing in manual testing, API validation, and Playwright automation. I have validated critical workflows across web applications, payment processing, business management systems, CRM platforms, donation management systems and logistics operations. My focus is delivering measurable quality impact through systematic testing, root-cause investigation, and reliable test automation using modern frameworks and CI/CD pipelines. Client names, confidential implementation details and proprietary information are intentionally omitted where required.
Read Full ProfileA practical testing skill set covering the application lifecycle from requirements and functional validation through API, data, regression and automation testing.
Validate application features, user journeys, business rules and expected system behavior against documented requirements.
Test payment workflows, recurring transactions, refunds, failures, redirects and transaction related business logic.
Validate endpoints, payloads, response codes, authentication behavior, data integrity and integration workflows.
Revalidate existing functionality after changes to help identify regressions before software reaches users.
Verify stored data, relationships, consistency, calculations and expected database behavior using SQL-based validation.
Document reproducible defects, assess severity and priority, support triage and track issues through resolution.
Build and maintain automated checks for repeatable workflows and regression coverage where automation provides practical value.
Validate responsive web interfaces across browsers, screen sizes and mobile devices for consistent user experiences.
Structured QA workflow from requirements to release verification.
Review requirements, user stories and business rules to understand expected behavior and integration points.
Create test cases covering happy path, edge cases, boundary conditions, failure scenarios and realistic user workflows.
Run manual test cycles, identify defects, and document findings with clear reproduction steps, expected vs actual results and supporting evidence.
Implement Playwright-based automation for repeatable workflows using Page Object Model architecture and GitHub Actions CI/CD integration.
Validate fixes, run regression suites, confirm CI pipeline stability and report release readiness with clear quality findings.
Independent QA automation projects where architecture, code, tests and results are publicly verifiable on GitHub. These projects demonstrate QA automation thinking, Page Object Model architecture, CI/CD integration and testing methodology in publicly inspectable form.
26 automated tests across authentication, product catalog, shopping cart, checkout and REST API endpoints. UI and API validation with Page Object Model architecture and GitHub Actions CI.
6 UI automation tests covering Material Request, Quotation, and Sales Order workflows. Page Object Model architecture with Playwright and GitHub Actions CI. Includes autocomplete synchronization investigation.
37 automated tests across a real Razorpay Test Mode payment flow — verification, security, webhook handling and refund logic. Two real defects found, investigated and fixed with regression coverage.
Portfolio disclosure: The examples below represent selected areas of professional QA experience. Project names, client identities, proprietary implementation details, credentials, test data and other restricted information are intentionally omitted unless authorized for public disclosure.
Tested donation and payment workflows, including recurring transactions, failure scenarios and business-rule validation.
Performed end-to-end QA across CRM, financial workflows, reporting, user permissions and business-critical application modules.
Tested shipment and logistics workflows, status updates, business rules, data consistency and regression scenarios.
Validated donor-facing workflows, role-based functionality, data handling and application behavior across multiple user journeys.
Tested donation workflows involving multi-currency scenarios, transaction behavior, validation rules and regression coverage.
Validated data-driven workflows, reporting behavior, data consistency, business rules and user-facing application functionality.
A generalized example of QA activities performed on a business management application. Client identity and proprietary implementation details have been intentionally omitted.
Validated financial and donation-related calculations, eligibility rules, transaction scenarios and reporting behavior against documented requirements.
Tested user profiles, data entry, record updates, interaction history, search, filtering and data consistency across application workflows.
Validated role-based access behavior and checked that users could access only the functionality and information appropriate to their assigned permissions.
Tested successful and unsuccessful payment scenarios, recurring transactions, refunds, redirects and related application behavior.
Verified application reports, calculated values, filtering, data consistency and expected results across representative scenarios.
Tested user-facing workflows across different browsers, viewport sizes and mobile devices to identify layout and usability issues.
Stabilizing ERPNext Autocomplete Automation
During ERPNext QA automation development, automated tests failed intermittently when interacting with autocomplete dropdown fields. This case study demonstrates the debugging methodology applied to identify and resolve the underlying synchronization issue.
Tests targeting autocomplete fields failed sporadically. Same test passed in one run but failed in the next. Error occurred during input field interaction and option selection.
Ran failing test multiple times to isolate conditions. Confirmed intermittent nature: failures occurred randomly, not deterministically. Pattern suggested timing or synchronization issue.
Used browser DevTools and Playwright logging to inspect DOM state during execution. Observed that dropdown options appeared after click event, suggesting asynchronous rendering behavior.
Analyzed Playwright selector and timing. Found that test attempted to select dropdown option before DOM fully rendered. Root cause: missing wait for dropdown options to be visible before interaction.
Autocomplete dropdown options rendered asynchronously. Test code selected option immediately after click without waiting for dropdown to populate. Race condition between DOM update and test execution.
Added explicit wait for dropdown options using
page.waitForSelector() with appropriate
timeout. Modified Page Object method to wait for
visible options before selection.
Repeated the test execution after the fix to confirm stable behavior. Verified the correction didn't introduce delays or break other workflows. Test now executes reliably in the CI pipeline.
Automation reliability depends on proper synchronization with application behavior. Explicit waits for UI state changes prevent race conditions. This investigation strengthened overall test architecture.
Measurable outcomes from independent QA work.
Quality is not an afterthought.
I approach software testing as a critical thinking exercise: understanding how products fail,
validating that systems behave correctly under real conditions, and providing clear evidence to
inform release decisions.
Every test is intentional.
I write automation that catches real bugs, validates business logic, and scales with your system.
No cargo-cult testing. No false confidence from high test counts.
Your code can be inspected.
My approach is transparent: architecture, test design, automation patterns and results are open
on GitHub. Not promises—proof.
Tools are selected according to project requirements and testing objectives.
UI automation, regression workflows and API automation
Manual API exploration and validation
Database validation and test data management
Automated test execution in CI/CD pipeline
Automation implementation and test development
Maintainable and scalable test automation architecture
Defect tracking and issue management
Exploratory testing and complex workflow validation
Supporting documentation and artifacts demonstrating QA planning, execution, automation and findings.
Test plans defining scope, approach, resource allocation, schedule and success criteria for application testing cycles.
Manual test cases covering functional requirements, boundary conditions, error scenarios and user workflows. Coverage matrices documenting test scope.
Test execution reports documenting test runs, results, pass/fail counts, defects identified and regression coverage across application builds.
Public GitHub repositories with test source code, Page Object Model architecture, CI/CD pipeline configuration and test execution logs.
Root cause analysis of automation failures, engineering findings documenting investigation methodology and resolution approach.
Contributing to QA activities across multiple client projects, including functional testing, regression testing, API validation, payment workflow testing, defect management and automation.
Completed training covering manual testing, automation fundamentals and SQL database management.
Developed a foundation in accounting, business processes and financial concepts that supports testing of business-oriented software applications.
I'm open to full-time QA Engineer roles. I'm based in Mumbai and open to remote, hybrid, or on-site opportunities. Feel free to reach out directly to discuss.
Yes. I'm comfortable joining an existing QA workflow, adapting to team tools and processes, and contributing to both manual and automated testing efforts from day one.
All professional project examples are intentionally generalized. Client names, proprietary implementation details and internal documentation are omitted unless explicitly authorized for disclosure.
Available to discuss — please reach out via the contact page or email me directly and I'll respond promptly.