QA + Bug Testing for SaaS/Web App Launch — AI Tools Required

1. Project Scope Flowjo is hiring an AI-assisted QA tester to help prepare the full Flowjo platform for launch. This is a short-term launch QA role focused on finding bugs, testing user flows, checking UI/UX against specifications and wireframes, documenting issues clearly in Trello, completing QA coverage tracking, and retesting fixes once implemented. Testing will cover the major launch systems across: Flowjo Marketing Website — public flowjo.coach website pages, navigation, CTAs, forms, responsive layouts, copy/content, newsletter/email capture, and launch-critical marketing flows. Flowjo Finder Funnel — Finder entry, quiz progression, email/account capture, logged-in/logged-out behaviour, routing into the app, and results handoff. Flowjo Web App — authentication, dashboard, onboarding, account settings, user roles/access, Stripe/subscription behaviour, loading/error/empty states, and core user journeys. Training Dojo LMS, inside the Flowjo App — custom learning-management experience covering course discovery, lessons/modules, locked/unlocked access, progress/navigation, resources, video/course presentation, and responsive course experience. Native CMS / Admin Areas — admin workflows for the React-based Flowjo App, plus WordPress/Elementor content-management checks for flowjo.coach and jamietoyne.com where relevant. jamietoyne.com Website — full site QA including public pages, Resource Hub, search, filters, resource templates, links, forms, responsive layouts, copy/content, newsletter/email flows, and platform integration points. Cross-Platform Launch Flows — user journeys between flowjo.coach, flowjo.coach/app, and jamietoyne.com, including Finder-to-app routing, login/signup routing, payment/access changes, resource usage, newsletter/contact flows, and internal/external links. You will use structured checklists and user journeys as the primary testing guide. The full specification and wireframes will be available as a reference source, and you are expected to use AI tools to quickly identify relevant expected behaviour, UX requirements, UI references, and copy expectations when testing each area. 2. Testing Requirements Testing should cover: functional bugs and broken flows logged-in and logged-out user journeys role/access behaviour forms, validation, and error states Stripe/payment and subscription flows CMS/admin workflows UI consistency against wireframes mobile, tablet, and desktop responsive behaviour copy, spelling, and content issues UX friction and unclear navigation loading, error, empty, and success states broken links console/browser errors where relevant cross-platform routing and launch flows retesting fixes after developer updates QA coverage must be tracked in the provided Google Sheet checklist. Trello is used for bug reports. The Google Sheet is used to show what has been tested, what passed, what failed, what is blocked, and what requires retesting. Bug reports must be created quickly, clearly, and efficiently in Trello. Each bug report must include: clear title severity label: Launch-blocking / Important / Minor page or feature affected related QA checklist ID steps to reproduce expected result actual result screenshots or screen recording where useful browser/device details any relevant notes for the developer UX feedback should identify friction, confusion, or mismatch against expected behaviour. Do not redesign flows or introduce new product concepts. Retesting fixed issues is part of the project scope and may be completed in a separate retest round. Before the live testing interview, shortlisted applicants will be given the detailed Flowjo QA Project Scope and Google Sheet quote estimator. You will be asked to duplicate the sheet, complete the Quote Estimator tab, and return an estimate before the live test. 3. Tools + Workflow All bugs must be documented in Trello. Preference will be given to testers who already use efficient bug-capture, screen-recording, browser/device testing, accessibility, performance, and AI-assisted QA tools that support clear Trello reporting. Examples of useful tools include Marker.io, BugHerd, Chrome DevTools, Loom, BrowserStack, LambdaTest, Postman, Playwright, Cypress, Applitools, AI test-case generation tools, or equivalent tools already in your workflow. These tools are optional examples, not mandatory requirements. You must provide your own QA tools, AI tools, browser/device testing tools, screen-recording tools, and workflow. 4. What We Provide We will provide: access to the required Flowjo systems relevant test accounts and user roles Trello bug board access Google Sheet QA checklist and quote estimator testing checklists and user journeys relevant specs, wireframes, and expected-behaviour references launch priorities and severity definitions 5. Required Skills + Experience AI-assisted QA workflow — expert at using AI to generate test cases, expand edge cases, summarise bugs, prepare retest checklists, and improve test coverage quickly. Clear bug reporting — able to create accurate, structured Trello tasks quickly with reproduction steps, expected vs actual results, severity, screenshots/video, browser/device details, and related QA checklist IDs. Manual QA testing — experienced testing websites, web apps, SaaS platforms, dashboards, forms, and user flows. Specification-based testing — able to test against wireframes, expected behaviour, checklists, and written requirements. UX and usability judgment — able to identify confusing flows, unclear navigation, and friction points without redesigning the product. Responsive testing — able to test desktop-first layouts plus tablet and mobile responsive views. Strong written English — able to communicate bugs clearly and understand product behaviour from written requirements. Retesting discipline — able to verify fixes and confirm whether bugs are resolved or still present. Launch QA mindset — able to identify what is launch-blocking, what is important, and what is minor. Useful but not required: React app testing experience WordPress / Elementor testing experience membership platform or LMS testing experience Stripe/subscription/access testing experience Chrome DevTools experience Marker.io, BugHerd, BrowserStack, LambdaTest, or similar QA tools basic accessibility testing automation tools such as Playwright, Cypress, BugBug, or testRigor Do not apply if you only do casual website reviews, cannot write clear bug reports, do not use AI tools in your QA workflow, cannot work systematically, or are not comfortable testing complex logged-in web app flows. 6. How to Apply Step 1 — Apply Provide the following information in your application: a. Your hourly rate b. A link to your portfolio or relevant QA work c. In 50 words or less: summarise your relevant QA testing experience d. One example bug report you have written — remove confidential details if needed e. List the QA tools you prefer to use f. Explain how you use AI to test faster and more thoroughly g. In 50 words or less: explain your workflow for this project h. What are the first 5 things you would test in a new SaaS/web app before launch, and why? i. Are you willing to complete a 30-minute live testing interview before being hired? Answer YES or NO Step 2 — QA Project Scope + Quote Estimate Shortlisted applicants will receive the detailed Flowjo QA Project Scope and Google Sheet quote estimator before the live testing interview. You will be asked to: review the QA Project Scope duplicate the Google Sheet complete the Quote Estimator tab in your copy estimate hours by major system and testing round return the completed estimate before the live testing interview This estimate helps us understand your approach, expected timing, assumptions, and how you would structure the QA work before hiring. Step 3 — 30-Minute Live Testing Interview Shortlisted applicants who complete the quote estimate may be invited to a 30-minute live testing interview. During the interview, you will test a small section of the Flowjo platform live for approximately 20 minutes. You will be asked to: explain your testing approach identify bugs, UX issues, and unclear behaviour use your normal QA/AI workflow where useful create one example Trello bug report classify issues as Launch-blocking / Important / Minor We will assess your testing method, attention to detail, bug-reporting quality, AI workflow, communication, Trello usage, and overall speed/thoroughness. The task is designed to assess workflow and judgment, not to obtain free QA work. 7. About Flowjo Flowjo helps ADHD founders, entrepreneurs, and creatives beat burnout and build systems that help them perform at their best. We are preparing to launch the Flowjo marketing website, Flowjo app, Training Dojo LMS, Native CMS/Admin areas, and jamietoyne.com website. We need a QA tester who can find problems before users do, document them clearly for our developer, use AI tools to work efficiently, and help us reach QA launch readiness by 31 July 2026.