About Me
Professional summary, testing mindset, technical understanding, and collaboration approach presented in recruiter-friendly language.
Manual QA Engineer with practical experience in testing web applications, validating APIs, documenting findings, and supporting release decisions with structured evidence.
I focus on finding issues early, clarifying requirements before execution, and producing documentation that helps teams fix defects efficiently.
I approach testing as risk analysis plus clear communication. The goal is not only to find bugs, but to understand what matters most to users, business workflows, and release quality.
Functional validation of end-to-end flows, negative scenarios, regression suites, smoke checks, and UI consistency across core pages.
Check layout integrity, component behavior, navigation, forms, and interactive states across desktop, tablet, and mobile breakpoints.
Use browser DevTools, request and response inspection, and status code analysis to connect UI behavior with backend responses.
Inspect DOM structure, states, styles, and layout rules to explain issues precisely and verify fixes with confidence.
Use SQL basics to validate records, confirm state changes after API or UI actions, and investigate data-related inconsistencies.
Collaborate with developers, PMs, and designers by asking precise questions, surfacing risks, and keeping defect reports actionable.
I review requirements for ambiguity, completeness, consistency, and measurability. Missing acceptance criteria, unclear business rules, and undefined error handling are treated as quality risks.
I inspect mockups for visual consistency, missing states, responsive behavior, contradictory labels, and details that can create implementation gaps later.