QA Tester for Web App SaaS

We're about to launch a web-based SaaS platform and need a QA tester to do a full pass before release. The product is a two-sided marketplace: businesses post short-term shifts, and independent professionals apply to fill them. Payments run through Stripe (including Stripe Connect payouts), and an admin role manually verifies new accounts before they can transact. **What you'll test: ** - Signup and verification: registration for both account types, admin approval/rejection, and confirming unverified users are correctly blocked from posting or applying - Shift lifecycle: posting, editing, cancelling, expiring, and the application/accept/decline flow between both sides - Payments: Stripe checkout in test mode, Stripe Connect onboarding for professionals, payout status, plus the alternate "pay offline" path and how it changes shift and payment status - Admin dashboard: user lists, filtering, account detail views, approve and reject actions - Permissions and access control: each role only sees and does what it should, with no cross-account data leaks or unauthorized route access - Notifications and emails: the right message fires at the right trigger, to the right person - Forms and validation: required fields, bad input, duplicate submissions, error messaging - Compatibility: Chrome, Safari, Firefox on desktop, plus mobile browsers (iOS and Android) ... **Deliverables:** - A written test plan or checklist covering the flows above (we'll review it before you start executing) - A bug log in [Google Sheets / Notion] with clear repro steps, expected vs. actual, severity, browser and device, and a screenshot or screen recording - Retesting once fixes ship, and confirming closure **Requirements:** - [1+] years manual QA on web applications - Experience testing payment flows (Stripe experience a strong plus) - Experience testing multi-role or permission-based apps - Clear written English. Vague bug reports cost us more time than they save. **To apply, answer this:** You've been given login credentials for two user roles and a staging site with no documentation. What are the first five things you test, and why those five?