Manual QA Tester: 4-Week Script-Driven Test Cycle (Jira + Screen Recordings)

Overview We are hiring a detail-oriented QA tester for a structured 4-week test cycle on a web application. This is script-driven manual QA. We provide the test cases, you execute them exactly as written, log results in Jira, and attach screen recordings as evidence. This role rewards precision over creativity. We are not looking for someone to redesign test plans. We need someone who follows a written script to the letter and treats any deviation from expected behavior as a finding. Scope & method Test cases and step-by-step scripts are provided weekly, organized in Jira by epic (one epic per workflow area). Each ticket includes numbered test steps and an expected-result description. You execute each ticket exactly as written, with no interpreting, extending, or skipping steps. A deviation from the script is itself a finding, not a judgment call. Weekly schedule The engagement runs four weeks, in order, not in parallel. We start with the end-user-facing surfaces and validate them first, then move to the internal admin surfaces. Findings are filed continuously and triaged in parallel, so you do not need to fully close one week before the next begins. Week 1: End-User Messaging & Operator Views Messaging interface and layout, AI-assisted reply suggestions and compose, automations and templates, operations and communications views, dashboard and analytics, and several supporting content views. Week 2: Core End-User Journey End-user onboarding and preference flow, personalized content generation (preference-based and inferred), end-user viewing and selection, requests, and content modes. Week 3: Admin Billing, Messaging & Config Plan and subscription status changes (tier upgrades and downgrades), subscription, invoice, and payment views, integration configuration settings and copy, content and personalization toggles, and admin settings categories (visible and clickable). Week 4: Admin Profiles & Access Account and profile creation, profile editing (email changes, saving), invitation and notification emails (including spam-folder behavior), unique-email handling, and login and access for created accounts. Ticket workflow Every test case is a Jira ticket under its epic, with steps and an expected result attached. Execute the ticket as written. If the result matches, close the ticket. If you find a defect but cannot reproduce it on retest, close the ticket with a screen recording reproducing the original steps and result as evidence. If you find a defect and confirm it, leave the ticket open, attach a screen recording reproducing the issue, and assign it to the team for triage. If you hit a defect outside the scope of the ticket you are testing, log it as a separate ticket. Do not fold it into the current one. Once a developer fixes a defect, the ticket comes back to you for retest. Validate against the original steps and close it, or reopen it if the issue persists. Ticket requirements Title: workflow area plus the specific case tested. Description: what is being tested and the expected result. Steps: numbered and reproducible, with no paraphrasing of the provided script. Evidence: screen recording attached for any ticket closed as not reproducible, and for any confirmed defect. What we are looking for Proven manual QA or software testing experience. Comfort working in Jira (epics, tickets, status workflow). A screen-recording setup (Loom or similar) and clean, reproducible bug-reporting habits. Strong attention to detail and the discipline to follow a script precisely. Reliable availability across the full 4-week cycle. Engagement Fixed 4-week cycle, sequential by week. The selected candidate signs an NDA before receiving any access or product details. To apply, please include A short summary of your manual QA experience. Your experience with Jira. The screen-recording tool you use. Your answer to this: if you find a defect you cannot reproduce on retest, what do you do?