QA Lead
Embedded QA · Contractor → Full-time · Owner of quality.
A QA Lead embedded in the development lifecycle, not parked at the end of it. You catch bugs the day a feature merges, work shoulder-to-shoulder with engineers, and own the quality bar for a child-safe AI learning product.
The essentials, up front
We hire on demonstrated ability, not years of experience.
Role
QA Lead — initially Contractor, transitioning to Full-time post-MVP.
Location
Fully remote, async-friendly. We hire adults who manage their own time.
Engagement
Phase 1 (MVP): Contractor. Phase 2 (post-MVP): Full-time, based on performance during the contract.
Seniority
Open — we hire on demonstrated ability, not years of experience.
Reports to
Founder; collaborates daily with engineering.
Hiring process
30-min intro call → short practical exercise (test plan + bug report on a live build) → working session with the team → founder chat & offer.
A child-safe AI learning product
JurneeGo is building a child-safe AI learning product. We believe AI can be one of the most powerful learning tools ever made for kids — but only if it is built with care, with strong safety as a default, and by people who genuinely sweat the product details. We are early, well-supported, and moving fast.
Embedded QA, not end-of-line UAT
We are looking for a QA Lead who is embedded in the development lifecycle, not parked at the end of it doing UAT. You will catch bugs the day a feature merges, work shoulder-to-shoulder with engineers, and own the quality bar for the product as a whole. You start as a contractor during MVP and transition into a full-time leadership role post-launch, where you will own automation, QA process, and eventually a small team.
Why this role matters
Our users are children. A bug in a normal consumer app is annoying. A bug in ours can break trust with a parent or, worse, surface something a child should never see. We need someone who treats quality as a product feature, not a checklist — and who is genuinely energized by being the safety net for a small, fast team.
Keep the product shippable every day
During MVP, your job is to keep the product shippable every day. You are the closest thing to a user that the team has, and you should test like one.
Key responsibilities — Phase 1
Continuous QA (dev integration)
Validate features immediately after they merge to the dev environment. Test core flows continuously during development, not in a batch at the end. Work closely with engineers while the change is still fresh in their head.
Manual QA
Run functional and regression testing across web and mobile flows. Identify bugs and edge cases early — especially the ones a child or a non-technical parent would actually hit. Verify fixes quickly so engineers can keep moving.
Task & delivery support
Push back when a task is unclear or untestable before work starts. Track bug lifecycle end to end (open → fix → retest → close). Coordinate closely with engineers during sprints; participate in planning and standups.
Release & UAT validation
Support UAT as the final validation step before any release. Ensure stability and confirm that critical flows work end to end. Be the person who can credibly say “yes, this is safe to ship.”
Own how quality works at JurneeGo
Once we transition you full-time, the role grows beyond hands-on testing. You become the owner of how quality works at JurneeGo.
Automation-driven QA
Design and build the automated test suite (API, end-to-end, regression). Decide what to automate, what to keep manual, and what is not worth testing at all.
QA process ownership
Define how bugs are tracked, how releases are gated, how UAT works, and how the team measures quality over time.
QA leadership
As we grow, hire and mentor additional QA engineers. Set the bar and the culture for the function.
Cross-functional voice
Represent quality and the user experience in product and engineering conversations, not just defect counts.
Must-haves and good to have
We hire on demonstrated ability. Here is what we are screening for — and what we are not.
Must-haves
- Solid QA experience on web and/or mobile applications shipped to real users.
- Strong understanding of QA inside the development lifecycle — you know how to test alongside engineers, not after them.
- Comfort working closely with a small engineering team in a fast-paced, high-change environment.
- Sharp eye for edge cases, broken UX, and bugs that automation will miss.
- Strong written communication — clear bug reports, clear test plans, clear retrospectives.
- Comfortable working remotely with a high degree of self-direction.
Good to have
- API testing experience (Postman, Insomnia, REST Client, or similar).
- Familiarity with CI/CD workflows — running tests in pipelines, gating merges, basic environment management.
- Exposure to automation tools such as Playwright, Cypress, Detox, or Appium. We do not expect you to be an SDET on day one — we expect you to grow into automation as the role evolves.
- Experience writing or maintaining test plans for safety-sensitive or compliance-bound products.
- Background in education, kids' products, or any consumer product with a high care-bar.
What we are not screening for
- A specific number of years of experience.
- A pre-existing automation framework or a thousand-test portfolio. The MVP needs strong manual QA first; automation comes after.
- ISTQB or other certifications. Useful, but not required.
Build the QA function from scratch
This is not a tester seat. It is the future ownership of QA at a company where quality genuinely changes outcomes for kids.
A real path from contractor to lead
We are not hiring a tester — we are hiring the future owner of QA. Phase 1 is a paid trial run for both sides.
Embedded, not isolated
You sit inside the product team, with a real voice in what gets shipped and when.
Real impact on kids
Education products that work change lives. Education products that go wrong cause harm. Both directions are motivating.
Build the function from scratch
The tooling, the process, the bar — you set it. That is rare, and it is the job.
Fully remote, async-friendly
We hire adults who manage their own time.
How we get to yes
A clear, low-mystery process. We read every application. We reply to every application.
Intro call (30 min)
We get to know each other and you ask us anything.
Practical exercise
We give you access to a recent build and ask for a short test plan, a prioritized list of bugs you found, and clear write-ups for the top issues. Should take ~2–3 hours.
Working session (60–90 min)
We walk through your exercise together, talk through how you would set up QA inside our current sprint cadence, and discuss the path to automation.
Founder conversation
Talk about the company, the next 12 months, and whether the fit is mutual.
Offer
Contractor engagement to start, with the full-time transition criteria written out clearly up front.
Send us a short email
Send a short email to aiden@jurneego.com with: a one-paragraph intro telling us why this role, a quick description of a bug or quality issue you are proud of catching (and how you caught it), and any links or attachments that show how you work — sample test plans, bug reports, or projects you have shipped quality on. A CV is welcome but not required if your examples speak for themselves.
We read every application. We reply to every application.
Ready to own the quality bar?
Embedded QA, a clear path from contractor to lead, and real impact on a child-safe product.