About
Quality is an engineering discipline.
I'm a QA Automation Engineer with around six years of experience, from manual testing and exploratory work to building automation that teams rely on before every release.
I started in manual QA, writing test cases, validating backend data, and learning how defects reach production. That foundation still shapes how I work: automation should protect repetitive, business-critical flows, reduce regression risk, and give teams confidence beyond happy-path coverage.
Today, I work with Playwright, Cypress, and TypeScript, alongside API testing, CI/CD pipelines, k6 performance validation, and AI/ML system testing. Release readiness is where my work matters most. I use risk-based testing to focus on what could hurt users, data, or the business, and I build test coverage that teams can trust.
Outside of client work, I've built AI-powered QA tools including QA Copilot and QA Intelligence to automate requirement analysis, generate test strategies, analyze CI failures, and help teams investigate regressions more efficiently.
I enjoy thinking beyond individual test cases and focusing on quality systems: stable automation frameworks, trustworthy CI feedback, clear release signals, and automation architecture that other engineers can build on and maintain.
Now
Current focus
I'm growing toward SDET-level engineering by strengthening my Playwright and TypeScript automation architecture, while also expanding into Python and pytest to build a broader testing foundation across different stacks.
CI/CD reliability and failure analysis are a major focus for me. I want pipeline feedback to be actionable, not noisy, and I'm building toward that with projects like QA Intelligence and QA Copilot, tools focused on flaky test analysis, failure investigation, and clearer release feedback.
I'm also learning more about LLMs, AI-assisted workflows, and how they can support QA work in a practical way: requirement analysis, test design, failure analysis, and risk discovery, while keeping human judgment in control.
How I work
Principles I work by
Quality starts before implementation
Testing begins with unclear requirements, missing edge cases, risky assumptions, and product behavior that needs clarification. I push back early when scope is fuzzy or acceptance criteria leave room for interpretation. Catching ambiguity before code ships is cheaper than catching it in production.
Automation should create trust
A test suite is only valuable if the team trusts its results. I focus on stable, readable, maintainable automation that gives clear release feedback, not noise that people learn to ignore. When a test fails, the team should know what broke and why it matters.
Release readiness matters more than bug count
Not every defect should block a release. I look at severity, likelihood, user impact, business impact, and regression risk before making a QA recommendation. The question is not how many bugs exist. It is whether the product is safe to ship.
CI failures should be actionable
A failed pipeline should help the team understand what broke, why it matters, and whether it is a new regression, a flaky test, or an existing issue. I treat noisy CI as a quality problem, not just an infrastructure annoyance. Clear failure signals keep releases moving without sacrificing confidence.
AI assists the process, judgment stays human
AI can speed up test design, debugging, and failure analysis, but QA judgment is still needed to decide what matters. I use AI as a practical assistant, not a replacement for risk thinking. The final call on release readiness always stays with the engineer.
Good QA helps the whole team move faster
The goal is not to slow releases down. The goal is to make releases safer, feedback faster, and quality decisions clearer. When QA is structured well, developers spend less time on preventable regressions and more time shipping value.
Career
Career
Automation, regression validation, API checks, performance testing, and CI reliability across enterprise web applications.
Responsibilities
- Took ownership of automation, regression testing, and release validation across enterprise web applications, working closely with developers and product teams to identify risks early and support stable software releases
- Built and expanded Playwright and Cypress automation suites to support new feature development, regression coverage, and day-to-day quality validation
- Used Postman and backend validation techniques to verify integrations, data flows, API behavior, and data integrity across multiple services
Impact
- Performed load and performance testing with k6 to evaluate application stability, response times, and behavior under different traffic conditions
- Improved CI/CD reliability by investigating unstable tests, reducing flaky executions, and using AI-assisted analysis to identify recurring failure patterns and root causes
Expertise
Where I go deep
Playwright & TypeScript
Designing maintainable E2E automation with page objects, reusable fixtures, test tagging, reporting, and CI-friendly execution that teams can trust and keep running.
API & Backend Validation
Validating payloads, integrations, data flows, response contracts, authentication behavior, and backend consistency beyond what the UI shows.
CI/CD Reliability
Reducing noisy pipeline failures, investigating flaky tests, improving failure visibility, and making automated feedback easier for teams to act on.
AI/ML Validation
Testing inference behavior, prediction consistency, invalid inputs, confidence handling, logging, and persistence around AI-powered systems.
Performance Testing
Using k6 to validate stability, response times, throughput, and system behavior under different traffic conditions before release.
Quality Strategy
Supporting better QA practices through risk-based testing, release readiness reviews, test planning, mentoring, and clear defect communication.