Manual QA Tester

Title: Manual QA Tester for AI Meeting Platform — Written Reports, Ongoing Weekly Work Category: QA & Testing → Manual Testing Type: Hourly, ongoing (5–10 hrs/week to start; can scale) Experience level: Intermediate --- About us We're BuzzTrail.ai — a small team building an AI meeting platform for SaaS sales. AI avatars join live video meetings, talk with prospects, and capture the conversation. The platform is in production, and we ship multiple times a week. We need a reliable manual tester to catch what slips through. What you'll do Walk through scripted QA playbooks against our staging and production sites and tell us — in writing — when something is broken. No coding required. We've already written the playbooks. Every step says "go here, click this, you should see that." Your job is to run them honestly, notice what's off, and report it clearly. A typical week: - 1–2 full regression passes (~2–4 hours each) after major releases - Smaller targeted playbooks (~20–45 min each) after smaller changes when we ask - Issue reports filed in a shared channel - Re-tests when fixes ship Surfaces you'll cover - Guest experience (prospects joining a meeting in incognito — most critical) - Host platform (logged-in user: dashboard, configuration, billing, integrations) - Internal admin tools (simple smoke checks) Web only for now. Desktop Chrome + Safari + a mobile viewport (375px) per pass. Must-haves - Strong written English. You'll be giving us written reports, not screen recordings. Clear, structured, complete sentences. - A quiet space, working webcam + mic, fast home internet — the AI you're testing is a live voice/video conversation, so you have to be in the meeting. Reporting back to us is purely written. - Latest Chrome and/or Safari, plus the ability to test on a real iPhone or Android - A Chrome profile with saved autofill data (we test autofill behavior) - Methodical, honest, and willing to flag small things - Reliable async communication — Slack or email, within ~24 hours Nice-to-have (not required) - Prior experience testing video calling - Familiarity with SaaS sales / demo flows Format we want for issue reports Plain text only. No screenshots, no screen recordings, no annotated images. We want words. For each issue you find, give us: - Playbook name + scenario number + step number - What you expected to see - What you actually saw (described in words — what was on screen, where it was, exactly what the wording said) - Browser, OS, viewport (desktop / mobile width) - Whether you could reproduce it on a second try If something is visual ("this color looks off", "the text overlaps the icon", "the button moves on hover"), describe it in words. We'd rather have a clear written description than an image. How we work - We give you the playbook, a test account, and a short note on what changed - You run it, file findings, we fix, you re-test - One weekly sync if useful, otherwise async - We pay for your time, including writing time, not just the active testing window To apply, please send 1. A written sample bug report you've filed before. Paste it directly into your application; no attachments, no images. Redact anything sensitive. 2. Your hourly rate We'll respond within a few business days. We start with a short paid trial; one playbook, ~1 hour of work, written report back. If we like how you work, we move to ongoing weekly hours. Example of the work Attached is a real playbook we use internally — the "Meeting Ended Page" QA playbook. Skim it before applying. It's representative of what we'd hand you on your first day: a single web page, ~12 scenarios, ~30 minutes to run. If reading it makes you think "I could run this and write up what I find", you're our person.