QA Engineer (Mid-to-Senior)

Description

Summary: Papaya is seeking a QA Engineer to own quality assurance for high-impact EdTech products, ensuring robust and scalable solutions for K-12 school districts. Highlights: 1. Opportunity to be the QA owner for an actual district pilot with real stakes. 2. Authority over your craft: decide automation, coverage, and CI execution. 3. Work with modern tooling like Playwright, k6, and GitHub Actions. **QA Engineer (Mid\-to\-Senior)** **Papaya — B2B EdTech for U.S. K\-12 School Districts** **Location** Remote, LATAM (must overlap U.S. Central Time, 9 AM–4 PM CT minimum) **Type** 3\-month contractor with strong intent to extend (confirmed during offer) **Experience** 2–4 years professional QA **Compensation** **S/ 3,000 (peruvian soles) per month**, depending on experience **Reports to** Engineering Senior Lead **About Papaya** Papaya is a B2B EdTech company building the operating system for high\-impact tutoring in U.S. K\-12 public schools. We currently serve 50\+ school districts across Texas and partner with 2,400\+ tutors supporting 8,000\+ students through a tightly integrated platform that handles scheduling, attendance, accountability, and learning data end\-to\-end. **Our stack** * **Test automation:** Playwright (preferred) or Cypress * **API testing:** Postman \+ code\-driven REST tests * **Performance:** k6, Locust, or JMeter * **Database:** PostgreSQL — you'll write data\-driven tests directly against it * **CI/CD:** GitHub Actions * **Browser targets:** modern Chrome \+ locked\-down Chromebook environments (Texas districts deploy these widely) **Must\-have** * **2\+ years strong end\-to\-end test automation** with Playwright or Cypress * **API testing fluency** — Postman or code\-driven REST tests in Python/TypeScript * **Performance/load testing chops** — k6, Locust, or JMeter, with a track record of validating throughput on real systems * **SQL fluency** — you write data\-driven tests directly against PostgreSQL, no ORM crutch * **Ability to extend and execute a test plan independently** — strategic plan is shaped with engineering, day\-to\-day expansion and CI integration are yours * **CI/CD familiarity** (GitHub Actions or equivalent) * **Excellent written English;** comfortable communicating directly with non\-technical district stakeholders **Nice\-to\-have** * Has authored full test strategies for prior production launches (huge plus, not required at this level) * Browser compatibility testing on locked\-down Chromebook environments * Experience coordinating UAT with non\-technical stakeholders * Visual regression testing (Percy, Chromatic, etc.) * Bilingual Spanish/English **Why join** * **Real launch, real stakes.** You'll be the QA owner for an actual district pilot, not a generic backlog. * **Authority over your craft.** You decide what gets automated, where coverage gaps are, and how CI runs. Engineering hands you a strategic plan and gets out of your way on execution. * **Modern tooling.** Playwright, k6, GitHub Actions. No flaky Selenium grids, no Jenkins from 2014\. * **Path to extend.** This starts as a 3\-month contract specifically because we want to prove the fit both ways. Strong performers stay on through the full org rollout. * **Remote, async\-friendly, LATAM\-aligned.** US Central Time overlap, but we run on documentation, not standups. **How to apply** Send a short note \+ resume/LinkedIn to **tech@papayatutor.com** with the subject line: QA Engineer — \[Your Name] In your note, tell us: * One production launch you helped ship and what you specifically owned in the test strategy * The trickiest flaky\-test or load\-testing problem you've solved in the last 12 months * Your salary expectations and earliest start date We read every application personally. We do not use automated resume screeners. *Papaya is an equal\-opportunity employer. We hire based on what you can build and how you work with a team — nothing else.* Sueldo: S/.2,500\.00 \- S/.3,000\.00 al mes Lugar de trabajo: Empleo remoto