Manual QA Engineer

Key Responsibilities

• Perform manual testing of WordPress and CMS-based websites to identify functional, UI, usability, content, integration, and compatibility issues.
• Validate WordPress functionality including templates, pages, posts, reusable components, plugins, forms, navigation, media, widgets, and other CMS-managed functionality.
• Perform functional, regression, smoke, exploratory, integration, UI, compatibility, and responsive testing.
• Test websites across multiple browsers including Chrome, Safari, Firefox, and Edge.
• Perform comprehensive testing across desktop, tablet, and mobile devices, including both Android and iOS environments.
• Validate responsive layouts across different screen resolutions, orientations, browsers, and physical devices.
• Use HTML, CSS, JavaScript knowledge and browser Developer Tools to investigate UI issues, inspect DOM elements, understand network requests, identify console errors, and provide useful technical information in defects.
• Should have good knowledge of database testing.
• Review user stories, requirements, and Acceptance Criteria (AC) before testing and identify missing, unclear, negative, boundary, and edge-case scenarios.
• Create, enhance, execute, and maintain test cases and test scenarios based on business and technical requirements.
• Work closely with Product Owners, Developers, Designers, and other QA team members to clarify requirements and ensure complete test coverage.
• Identify, reproduce, document, prioritize, and track defects through resolution.
• Create high-quality bug reports containing clear reproduction steps, expected and actual results, screenshots/videos, environment details, device/browser information, logs, and other supporting evidence.
• Perform regression testing for releases and validate fixes across applicable browsers and devices.
• Participate actively in daily stand-ups, sprint planning, backlog refinement/grooming, retrospectives, and other Agile ceremonies.
• Provide testing estimates, progress updates, quality risks, and meaningful QA inputs during sprint activities.