Role Overview
The Project Manager is responsible for ensuring what we decided to build gets delivered predictably—driving execution across people, timelines, dependencies, and risks. This is a delivery-control role: success is measured by on-time delivery, clear ownership, visible risks, smooth coordination, and reduced execution chaos. The Project Manager partners closely with Engineering and Product to keep work unblocked and moving.
Key Responsibilities
Execution Planning & Milestones
- Convert product scope into delivery plans: milestones, sequencing, dependencies, and ownership.
- Maintain execution visibility: what is in progress, what is blocked, and what is at risk.
- Drive operational cadence: planning sessions, check-ins, release readiness coordination.
Dependency, Risk & Change Management
- Identify dependencies early (cross-team, external, infrastructure) and drive resolution.
- Track risks, escalations, and tradeoffs; propose mitigation paths.
- Manage scope change: ensure changes are explicit, documented, and reflected in timelines.
Team Coordination & Delivery Flow
- Coordinate work across engineering roles (Engineers, Architects, DevOps, QA, Support) to keep throughput high.
- Ensure tasks have clear acceptance criteria and owners before entering execution.
- Improve delivery flow by identifying bottlenecks and tightening process standards.
Stakeholder Communication
- Provide clear, consistent project updates: progress, risks, decisions needed, and expected timelines.
- Align internal stakeholders and, when applicable, coordinate client-facing delivery updates with Support.
Required Technical Skills
- Proven experience running software projects end-to-end (planning to delivery).
- Strong ability to break work into milestones and manage dependencies.
- Strong risk management and escalation judgment.
- Comfort working with engineering teams and technical constraints.
- Strong written status reporting and meeting facilitation skills.
- Proficiency with a project tracking tool (Linear/Jira/Asana equivalents).
Nice to Have
- Experience in remote-first teams across time zones.
- Experience working with release processes, QA cycles, and incident-driven reprioritization.
- Familiarity with Agile/Lean practices (pragmatic, not ceremony-heavy).
- Experience improving delivery processes and operational systems.
Behavioral Expectations
- Predictability mindset: reduces surprises through visibility and early risk surfacing.
- Bias for action: unblocks work, drives decisions, and keeps momentum.
- Process pragmatism: uses the minimum process that improves delivery outcomes.
- Accountability: ensures owners, deadlines, and definitions are explicit.
- Calm leadership: steady under pressure; keeps teams aligned when priorities shift.