QA + UX Tester — Children's Reading Web App (iPad / Chromebook / Desktop)

QA + UX Tester — Children's Reading Web App (iPad / Chromebook / Desktop) About the product We're an early-stage edtech startup building an AI-powered reading tutor for children (roughly ages 6–10). It's a web app (runs in the browser, no install) where a child reads short stories aloud and gets real-time, friendly feedback from an animated guide. Before pilots, we want fresh eyes — both "does everything work?" and "is this actually a good experience for a child?" There are three pieces of work below. You can apply for one, two, or all three — tell us which. Pieces can run in parallel or be staged one at a time. Note: the app involves a child reading aloud into the device microphone, in English. For the UX and child-session pieces, comfort reading and speaking English clearly matters (we pay a premium for strong/native English). For technical QA, an accent is totally fine — it's actually useful test data. How to document your findings We work fastest from clear written notes and annotated screenshots, so please make those your primary format. Use video only when a screenshot can't capture it — timing, animation, or audio issues — and when you do, pair it with a short written summary and timestamps. We'll give you a simple reporting template and a shared folder to file everything. Part 1 — Technical QA (functional bug hunt) Go through the whole app like a real user and find everything broken, confusing, or rough. We provide test accounts, access, and QA checklists (covering the flows and the specific things we want verified) after hire. What to test: Every screen and button in both the parent setup flow and the child reading flow. The child reading loop specifically — the heart of the product, where we most need careful eyes: Text or audio getting cut off (mid-word, mid-sentence) Buttons that don't respond, fire twice, or do the wrong thing The guide's spoken/written feedback not matching what's on screen — e.g. it says one word but seems to expect another, or asks the child to read a single word but reacts to the whole line The app mishearing correct reading, or accepting reading that's clearly wrong Audio that doesn't play, overlaps, or comes at the wrong moment Cross-device / responsive: Desktop Chrome, iPad (Safari), Chromebook, and Android tablet/phone. Flag anything that looks or behaves differently per device. Performance: load times, and especially microphone/audio responsiveness and lag during read-aloud. Accessibility basics on parent-facing screens: keyboard navigation, readable contrast, sensible labels. Deliverable: a clear bug report — each issue with steps to reproduce, expected vs. actual, device/browser, and an annotated screenshot. Use a short screen recording only for things a still can't show (timing, animation, audio), with a written note of what to look for. If something "works" but feels wrong for a child, flag it as a UX issue so it routes to Part 2. Part 2 — UX & visual design review (focus: the child's experience) Open to Part 2 taking place first or in parallel Step back from bug-hunting and evaluate the whole experience through two lenses: Experience / flow: Is it clear, friendly, and motivating for a young child (ages 6–10)? Where does it confuse, frustrate, bore, or lose them? We especially want a deep look at the child's end-to-end flow — the warmup, the reading session, and the reward at the end. Visual design / UI: layout, spacing, alignment, typography, color, contrast, visual hierarchy, consistency across screens, and overall polish. Call out what looks unfinished, cramped, cluttered, or off-brand, and where the visuals help or hurt comprehension for a young reader. What we want: A walkthrough from a child's point of view, calling out friction, confusion, and what works well. A prioritized list of concrete improvement opportunities — experiential and visual — each with the problem, why it matters, and a suggested fix. We review and approve which to act on. (You recommend changes; you don't implement them.) Comparison notes vs. other children's learning apps, where relevant. Deliverable: a written UX & visual review (doc or slides) plus a prioritized opportunities list; annotated screenshots are very welcome, and a narrated screen-recording walkthrough is a strong plus. Background in UX, UI/visual design, or early-childhood education is a real advantage. Part 3 (optional / premium) - can assist with part 2 — Observed sessions with a ages 6–10 Helpful but not required, treated as a separate premium piece, and it pairs naturally with Part 2. If you can have a child in the 6–10 range go through the app — with their parent's consent — and document the journey, that's the clearest UX signal we can get. What this looks like: A child uses the app while you observe and guide as needed; you document where they thrive, hesitate, or get stuck. We capture the screen and the child's voice/audio (the reading audio also helps us improve the tutor). No camera / face recording of the child is needed. Verifiable parental consent before every session — we provide the consent and audio-release forms; no session goes ahead without it. You're comfortable guiding a young child through a reading activity in English. Deliverable: the session recording (screen + audio) plus your notes on the child's experience, feeding directly into the Part 2 opportunities list. If this part isn't a fit for your situation, no problem — Parts 1 and 2 stand on their own. Who we're looking for Meticulous, and genuinely enjoys finding the subtly-broken thing. Writes clear, organized bug/UX reports with screenshots or recordings. Has a working microphone and a quiet space (you'll test a read-aloud loop). Bonus: web-app QA experience; children's/education product experience; Devices: ideally access to more than one of Desktop Chrome, iPad, Chromebook, Android tablet. Tell us what you have. How we work / pay Start date: July 1, 2026. Apply for one, two, or all three parts — tell us which. Parts can run in parallel or one at a time. NDA: you'll sign a simple mutual NDA before getting access — the product is unreleased and it's a children's app. Communication: async-friendly. We ask for a short written summary at the end of each testing pass or session, plus one optional kickoff call (some overlap with US Central hours helps). [Compensation: TBD — hourly or fixed per part; premium rate for strong/native English on Parts 2–3.] We provide QA checklists, a reporting template, and a shared folder for your reports after hire. No real children's data is involved in technical QA. To apply Tell us: (1) which part(s), (2) which devices you can test on, (3) your English comfort and whether you can do read-aloud testing, (4) relevant QA/UX/children's-product experience, (5) Part 3 only — whether you can arrange a session with a child ages 6–10 with parental consent. A sample bug report or UX review is a plus.