Ongoing Product Tester for Fast-Moving SaaS & Web Apps

I’m a founder and product builder who ships quickly across several SaaS and web apps. I need a dependable, long-term product tester who enjoys living inside new software, trying real user flows, and finding problems before customers do. This is ongoing hands-on testing—not a one-time QA pass, and not primarily an automation role. I want someone who will repeatedly interact with current builds and new releases, explore beyond the happy path, notice confusing experiences, and verify fixes after they ship. What you’ll do: • Run exploratory, functional, and regression testing across web apps (with occasional mobile testing) • Exercise complete user journeys such as sign-up, onboarding, authentication, permissions, forms, payments, settings, and create/edit/delete flows • Invent realistic edge cases instead of only following a checklist • Report bugs in our tracker with severity, environment, exact reproduction steps, expected vs. actual behavior, and screenshots or short videos • Flag usability and product friction—not only technical failures • Retest fixes and maintain lightweight regression checklists for important flows • Send a concise update after each testing session: what you tested, what you found, what is blocked, and what should be tested next What good looks like: • You can begin independently from a build link and brief product context • You prioritize high-risk and core customer flows • You reproduce issues before reporting them and distinguish bugs from preferences • You are consistent, proactive, detail-oriented, and comfortable with frequent releases and incomplete early-stage products • You communicate clearly in written English • Access to multiple browsers and real desktop/mobile devices is a plus The engagement will begin around 5–15 hours per week and is intended to be ongoing. Work may increase around releases. Manual testing judgment matters more than automation experience. To apply, please answer: 1. Describe a difficult bug you discovered and why it was easy to miss. 2. Share an anonymized sample bug report, or describe the exact format you use. 3. List the browsers and devices you can test on. 4. Explain how you would spend your first two hours testing an unfamiliar SaaS app. 5. Start your proposal with the words “FLOW TESTED” so I know you read the full post.