Exploratory QA Tester — Find Bugs, UX Issues & Edge Cases in a B2B SaaS (No Requirements Doc)

Category: QA & Testing → Manual Testing Tags: Exploratory Testing, Manual Testing, Usability Testing, Bug Reports, QA We're a small team shipping a B2B SaaS web dashboard with a REST API and developer SDKs. The product is live and being used, but it has never been tested by an outside QA. We don't want to hand you a requirements doc — we want fresh eyes that find what we've stopped seeing. What we want you to do Spend [X] hours doing charter-based exploratory testing of our web dashboard and developer-facing surfaces — no scripts, no test plan from us. Approach it as a real user would: sign up, set things up, try to break it, try to use it the "wrong" way, get confused on purpose. Hunt for: functional bugs, broken/empty/loading states, copy errors, accessibility issues, confusing flows, dead ends, performance feel, mobile/responsive issues, browser inconsistencies (Chrome, Safari, Firefox), dark-mode glitches. Prioritize and report findings with severity, clear repro steps, screenshots or short Loom recordings, expected vs actual. Deliverable A prioritized bug/issue tracker (Google Sheet or an easy to use tool) with Severity (S1–S4), Repro Steps, Expected, Actual, Screenshot/Video, Suggested Area. A short written summary at the end: top 5 systemic issues, top 5 UX paper-cuts, anything you think is dangerous. You're a strong fit if you have 3+ years of professional QA / exploratory testing on web SaaS apps. Experience finding bugs without a written spec — comfortable with charter-based / session-based testing (Bach/Bolton style is a plus). A portfolio of bug reports you can share (sanitized is fine). Sharp written English — your repro steps are the deliverable. Bonus: developer-tools / API testing experience (Postman, browser devtools, network tab). Logistics Mutual NDA before access (we'll provide). We'll create a fresh test account on a staging environment. Time-boxed engagement first — [X] hours over [Y] days. If it's a great fit, we'll continue. Budget: please share your quote Start your proposal with the word PINEAPPLE so I know you read this. Then tell me: One bug you found on a SaaS product that the team had completely missed — and how you found it. The tools you'd use for this engagement. Your timezone and earliest start. Templated proposals will be rejected.