Requirements

• 3–6 years experience in software testing or test automation, owning quality for complex features in a cross-functional team.
  
• Deep knowledge of test automation frameworks (e.g., Selenium, Appium, Cypress, or similar) for both mobile and web.
  
• Strong understanding of QA fundamentals: test strategy, planning, execution, reporting, and bug lifecycle management.
  
• Proficiency with at least one programming language (e.g., Python, Java, JavaScript).
  
• Experience working iteratively (Agile-style), shipping in increments, and improving based on feedback and data.
  
• Ability to translate messy real-world requirements into clear, testable cases—without over-engineering.
  
• Clear communicator: can explain trade-offs, align stakeholders, and collaborate tightly with engineers and product managers.
  

• Own the end-to-end testing lifecycle for new features and modules—from requirement review → test planning → automation → execution → reporting → iterative improvement.
  
• Collaborate cross-functionally with Product, Engineering, Design, Data, and Operations to define quality criteria and ship reliable solutions in iterative modules (Agile delivery, frequent releases).
  
• Design, build, and maintain automated test frameworks for multiple user personas (e.g., parents, tappers, school admins, kitchen teams, internal ops) and ensure coverage for role-based workflows.
  
• Develop and execute tests with operational constraints in mind: offline-first or low-connectivity patterns, device realities (older Androids), and high-stakes accuracy.
  
• Work closely with engineers to de-risk releases before deployment through rigorous automation and exploratory testing.
  
• Contribute to the evolution of our QA processes and tooling, advocating for best practices in CI/CD, regression prevention, and test data management.
  
• Continuously analyze test results, identify root causes of issues, and drive actionable improvements to critical flows.
  
• Communicate clearly, present findings and recommendations in reviews, and keep stakeholders aligned without drama.
  
• Maintain strong handoff discipline: clean test documentation, reusable scripts, and developer-friendly bug reports.