Technical Project Manager (Software Delivery, QA, & Documentation)

About the Role We are a growing SaaS product company building and continuously improving our proprietary platform. This is a 100% internal software delivery role (not an agency, consulting, or client-facing position). We are looking for a hands-on Technical Project Manager with strong experience in Agile/Scrum methodologies to report directly to the Product Manager and support our engineering and QA teams. You will own the day-to-day organization and execution required to move features smoothly from requirements to verified releases. Key Responsibilities - Agile Ticket & Backlog Management: Convert product requirements into detailed epics, user stories, tasks, and subtasks in ClickUp, complete with testable acceptance criteria, edge cases, and designs. - Agile Ceremonies & Standups: Lead/co-lead daily standups, backlog refinement, sprint planning, and release reviews to maintain a predictable delivery rhythm. - Delivery & Dependency Tracking: Monitor active work daily, identify stalled tasks or delivery risks early, manage cross-ticket dependencies, and track work from development through QA. - Product Acceptance Testing: Perform hands-on testing on completed features to verify they meet requirements before approving closure (including post-release production verification). - Bug Tracking: Reproduce reported issues and create clear, detailed bug tickets (steps to reproduce, environment, user role, expected vs. actual results). - Documentation & Content: Maintain accurate internal platform guides, release notes, and record short product feature walkthrough videos/screen recordings. This role works closely with QA but does not replace the QA function. QA owns formal test planning, regression coverage, and test automation. The Technical Project Manager provides an additional product-acceptance layer by confirming that the delivered functionality matches the approved requirements and intended user experience. Expected Outcomes - Offload routine ticket creation, backlog hygiene, and ClickUp follow-ups from senior engineering leadership. - Maintain 95%+ accuracy in ClickUp ticket statuses, dependencies, sprint boards, and task owners. - Ensure 100% of major feature tickets pass product acceptance verification before being marked done. - Deliver concise weekly status reports covering completed work, active blockers, delivery risks, and release readiness. Qualifications Must-Haves: - Proven experience managing software development projects using Agile, Scrum, or Kanban frameworks. - Deep experience with ClickUp for managing Agile backlogs, sprint workflows, and board statuses. - Hands-on experience writing clear user stories, bug reports, and testable acceptance criteria. - Practical experience performing manual functional/user acceptance testing (UAT). - Exceptional written and verbal English communication skills with strong attention to detail. - Strict availability during 9:00 AM – 5:00 PM CT, Monday–Friday. Good-to-Haves: - Experience working with AI-powered SaaS products or complex API integrations. - Experience creating quick product walkthrough videos or writing user help guides. What Success Looks Like After 90 Days - Routine ticket creation no longer depends on senior engineers. - The Product Manager does not need to repeatedly request ClickUp updates. - Daily standups are structured, useful, and followed by documented action. - The active backlog accurately represents what the engineering team is working on. - Engineers begin work with clearer requirements and acceptance criteria. - QA receives better-defined functionality to test. - Blockers and potential delays are identified early. - Major features are verified before tickets are closed. - Released functionality is checked in production. - Product documentation and walkthrough materials are more complete and current. - The Product Manager can spend more time on strategy, roadmap, priorities, and major product decisions instead of routine delivery administration.