SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Narvar is hiring a Technical Project Manager to lead complex, multi-team engineering initiatives where success depends on orchestrating work across groups that don't naturally coordinate. This is a high-impact coordination role, not a status-reporting position.
You'll build and maintain the real dependency graph behind major projects: identifying which team's output blocks another team's start, tracking the critical path, and ensuring work happens in the right sequence. You'll follow technical discussions closely enough to spot dependencies before they become blockers, and proactively pull in the right stakeholders—engineering, product, design, data, leadership—before gaps turn into delays.
Core responsibilities include:
**Dependency Mapping & Critical Path Management**: Map cross-team dependencies for projects spanning multiple engineering teams with no single owner. Maintain a live view of the critical path (not just individual task lists) and flag when slips in one team affect achievable timelines for others. Surface hidden dependencies that sit at team seams before they become blockers. Distill the dependency graph into concise, honest updates for non-technical stakeholders and leadership.
**Cross-Functional Coordination**: Proactively identify when product, design, data, legal, or other functions need to be looped in—without waiting for engineers to flag it. Recognize when dependencies cross team boundaries and ensure both sides are actually talking to each other. Chase down answers, escalate when needed, and keep work moving. Serve as connective tissue across engineering and adjacent functions, especially where no single team sees the whole picture.
**Technical Context & Decision Support**: Follow technical discussions closely enough to grasp tradeoffs—architecture decisions, infrastructure choices, API design, build vs. buy. Reason about how technical choices affect parallelization vs. serialization of work. Surface implications for timeline, scope, and other teams. Facilitate broader input when decisions warrant it, without creating unnecessary overhead.
**Documentation & Operational Hygiene**: Keep dependency graphs, specs, decisions, and timelines documented and accessible. Ensure decisions made in Slack or ad-hoc meetings don't get lost, especially ones affecting teams beyond the room. Make it easy for anyone joining mid-stream to get up to speed quickly, including understanding why sequencing is what it is.
You'll need 4+ years managing complex, multi-team software projects with multiple workstreams and stakeholders in fast-moving environments. You should be comfortable with systems and dependency thinking, technical fluency (following engineering conversations without hand-holding), strong written communication, proactive initiative-taking, and calm decision-making under ambiguity. Cross-functional credibility with engineers, product managers, designers, and executives is essential.
