Technical Project Manager(Python/React) _ Remote(East Coast)

Requirement details:

Role: Technical Project Manager

Location: Remote(East Coast)

Duration: 12+ Months

Role Overview:

• We are seeking an experienced Technical Project Manager (TPM)
• Must have strong experience managing projects built on Python and React; ability to understand architecture, participate in technical discussions, and effectively coordinate with development teams is required.
• The TPM serves as the primary on-site interface between business stakeholders and the delivery team, owning both the how-and-when of delivery and the onsite product representation function.
• The TPM works in close partnership with an Offshore Product Owner who handles detailed backlog execution, i.e., Epic/Story authoring, documentation, grooming, and other high-volume PO work allowing the TPM to remain focused on strategic delivery leadership and stakeholder engagement.

Roles and Responsibilities:

1. Project Execution & Delivery Management

• Own the end-to-end delivery lifecycle of cloud SaaS projects from initiation through release and retrospective.
• Define, maintain, and control project plans, schedules, milestones, and critical paths using Jira, MS Project, or equivalent.
• Track sprint velocity, release burndown, and delivery metrics; take corrective action when deviations occur.
• Coordinate multi-team or multi-vendor delivery, ensuring dependencies are identified and resolved proactively.

2. Agile & Scrum Facilitation

• Lead and facilitate Scrum ceremonies: sprint planning, daily standups, sprint reviews, and retrospectives.
• Coach teams on Agile principles and remove impediments that block progress.
• Maintain team capacity planning across sprints, accounting for PTO, technical debt, and unplanned work.
• Coordinate program-level planning (SAFe PI Planning or equivalent) where applicable.

3. Risk & Issue Management

• Identify, log, and proactively manage project risks, issues, and dependencies throughout the delivery lifecycle.
• Develop mitigation strategies and escalate blockers to senior leadership as needed.
• Maintain a risk register and communicate status transparently to all stakeholders.

4. Stakeholder Communication & Reporting

• Serve as the primary point of contact for delivery status across internal and external stakeholders.
• Prepare and deliver regular project status reports, steering committee updates, and executive dashboards.
• Facilitate cross-functional alignment meetings between engineering, QA, DevOps, architecture, and security.
• Manage stakeholder expectations on scope, schedule, and budget- escalating trade-off decisions appropriately.

5. Technical Coordination

• Collaborate with engineering leads and architects to understand technical dependencies and cloud deployment strategies (AWS / Azure / Google Cloud Platform).
• Coordinate cloud environment provisioning, CI/CD pipeline readiness, and release gating criteria.
• Ensure cloud-related compliance, security reviews, and infrastructure milestones are sequenced into the project plan.
• Bridge the gap between technical implementation teams and non-technical business stakeholders.

6. Budget & Resource Management

• Track project budget, resource utilization, and forecast costs in alignment with finance and PMO guidelines.
• Manage staffing plans; coordinate onboarding and ramp-up of new team members or contractors.
• Provide inputs to resource planning and capacity forecasting across projects.

7. Quality & Process Governance

• Define and enforce Definition of Done (DoD) and release readiness criteria.
• Ensure quality gates, testing milestones, and UAT sign-offs are built into delivery plans.
• Drive adoption of project management best practices, tooling standards, and documentation protocols.

8. Release & Deployment Coordination

• Coordinate release planning, go-live readiness, and post-deployment monitoring with DevOps and SRE teams.
• Maintain and communicate release calendars; manage change windows and rollback procedures.
• Own the operational handover checklist from project delivery to ongoing support/operations.

9. Stakeholder Requirements Elicitation

• Act as the on-site voice of the business -- engage directly with client stakeholders to elicit, capture, and prioritize product requirements.
• Conduct requirements workshops, discovery sessions, and structured interviews with business users and subject-matter experts.
• Translate high-level business needs into feature briefs and Epic-level direction for the Offshore PO to elaborate.
• Validate that proposed solutions align with business objectives before they enter the sprint backlog.

10. Product Backlog Direction & Prioritization

• Define and communicate backlog priority direction to the Offshore PO based on stakeholder input and business value.
• Make final prioritization calls during sprint planning when business trade-offs need an on-site decision-maker.
• Review and approve Epic-level items before they are broken down into User Stories by the Offshore PO.
• Ensure the product backlog reflects the most current and accurate business priorities at all times.

11. Sprint Review & Business Acceptance

• Facilitate sprint review demonstrations with on-site business stakeholders and capture structured feedback.
• Act as the formal acceptance authority for completed stories on behalf of the business during sprint reviews.
• Communicate accepted, rejected, or deferred items back to the Offshore PO for backlog updates.
• Ensure feedback loops between business stakeholders and the delivery team are short, clear, and actionable.

12. Offshore PO Direction & Coordination

• Provide the Offshore PO with clear, context-rich direction on Epics, features, and business intent.
• Review and provide feedback on User Stories, acceptance criteria, and documentation produced by the Offshore PO.
• Hold regular sync sessions with the Offshore PO to align on backlog state, refinement progress, and upcoming sprint content.
• Escalate offshore PO blockers (ambiguous requirements, missing stakeholder input) and resolve them on-site.

13. Product Documentation Oversight

• Review and approve key product documents produced by the Offshore PO: feature specs, process flows, and acceptance criteria.
• Ensure all product artefacts meet the quality and completeness standards required for development and compliance.
• Maintain oversight of Jira hygiene -- Epic/Story status, labels, and linking -- ensuring it accurately reflects project reality.