QA Engineer

Act as the tactical executor of quality assurance within sprints and the QA owner inside a squad.

Bridge requirements with automation‑ready and sustainable test coverage, collaborating closely with developers under a QA Shift‑Left approach.

• TASKS & RESPONSIBILITIES Overview
• Own sprint-level QA: test planning, story testability, data, manual & exploratory runs, and story-level automation following Organization set standards.
• Collaborate Shift‑Left with developers: write automation early, review acceptance criteria, propose testability improvements.
• Keep a squad regression checklist; nominate cases to the shared/domain regression as per organization process standards Track squad quality signals (coverage, pass/fail, leakage, flakiness); contribute to dashboards; lead squad defect triage and RCA with devs.
• Sprint‑Level Quality Ownership
• - Create and maintain sprint‑level test plans aligned with acceptance criteria and integration needs.
• - Actively participate in refinement to clarify acceptance criteria and ensure testability (Shift‑Left).
• - Maintain a squad‑level regression checklist; propose candidates for broader regression to the QA Product Lead.
• Test Case Design & Execution
• - Design high‑quality, reusable, modular test cases for functional, negative, edge, and API scenarios.
• - Ensure test cases are automation‑ready and follow organizational standards defined by QA Lead (Org).
• - Execute manual and exploratory testing within each sprint.
• - Prepare and maintain test data sets to support consistent execution across environments.
• - Evaluate relevance of test cases and propose refactoring/removal of obsolete tests.
• Automation Contribution
• - Implement and maintain story‑level automated tests using approved frameworks (Selenium, Postman, Gherkin/Java).
• - Follow framework architecture and coding standards defined by QA Lead (Org).
• - Collaborate with developers to ensure automation is created early in the sprint (Shift‑Left).
• - Investigate automation failures, apply fixes under code review, and identify root causes.
• - Flag flaky tests, propose stabilization improvements, and implement approved fixes.
• Quality Governance (Squad Level)
• - Track and report quality signals: coverage, execution rate, defect leakage, automation stability.
• - Provide quality insights to QA Product Lead and Domain Engineering Manager for dashboards and governance.
• - Recommend process or tooling improvements while ensuring alignment with organizational standards.
• - Promote Shift‑Left practices by improving user story readiness and acceptance criteria quality.
• - Participate in squad retrospectives to improve test planning, coverage, and testability.
• Defect Management
• - Coordinate with QA Product Lead on Squad Assigned Defects assignment and resolution based on SLA/MTR.
• - Lead squad‑level defect triage, ensuring accuracy of severity, priority, and reproduction paths.
• - Ensure defects include logs, payloads, data, and screenshots to accelerate investigation.
• - Collaborate with developers on root‑cause analysis and validate corrective actions.
• - Expand regression coverage by adding checks for fixed defects and recommending broader regression candidates.
• Collaboration
• - Fully embedded in one or more squads, collaborating daily with developers, PO, and UX/UI.
• - Participate in all Agile ceremonies, driving quality‑focused conversations.
• - Coach junior testers on test design, exploratory testing, and story readiness.
• - Coordinate with other squads QA engineers when stories span multiple domains or integration points.
• Limited Beta / Pre‑Release Support
• - Support targeted beta actions for squad‑owned features (exploratory, smoke, usability checks).
• - Escalate broader beta campaign needs to QA Prod Lead to avoid scope overlap with platform‑level QA.
• Continuous Improvement
• - Identify bottlenecks in QA processes and propose actionable improvements.
• - Raise suggestions for enhancing test frameworks, automation practices, and story readiness.
• - Share quality learnings within the squad and the QA Guild to improve domain‑wide maturity.
• Professional Background, Skills & Abilities
• - Bachelor's degree in Computer Science or related field.
• - 3-6 years QA experience in Saa S or similar environments.
• - Experience in test planning, execution, functional and integration testing.
• - Hands‑on with Selenium, Postman, Gherkin, Java, Azure Dev Ops.
• - Certifications in ISTQB foundation CTFL/ CTFL‑AT/ CTFL‑TTA or certifications in Agile Testing, Dev Ops Quality, or Test Automation are beneficial!
• - Knowledge of SDLC, Agile, and Shift‑Left testing practices.
• - Strong analytical and communication skills.
• - Comfortable collaborating with developers on test design early in the process.
• - Ability to handle multiple stories and integrations within the squad.
• #J-18808-Ljbffr