Technical Project Manager

Narvar is growing! We are hiring a Technical Project Manager to drive our most complex, multi-team engineering initiatives — the ones with no single owning team, where progress depends on getting the sequencing right across groups that don't naturally coordinate with each other. This is not a status-reporting role. You won't be writing production code, but you will build and maintain the real dependency graph behind a project: which team's output blocks which other team's start, where the critical path actually runs, and what has to happen in what order for the whole thing to land. You'll follow technical discussions closely enough to spot those dependencies before they become blockers, and you'll proactively pull in the right people — across engineering, product, design, data, or leadership — before gaps turn into delays. Core responsibilities Dependency mapping and critical path management Map cross-team dependencies for projects that span multiple engineering teams with no single owning team — identify what blocks what, and in what order work needs to happen Maintain a live view of the critical path, not just individual teams' task lists, and flag when a slip in one team changes the achievable timeline for others Surface hidden or emerging dependencies before they become blockers, particularly ones that no single team has visibility into because they sit at the seams between teams Distill the graph into concise, honest updates for non-technical stakeholders and leadership — what's driving the timeline, what's at risk, and why Cross-functional coordination Identify when product management, design, data, legal, or other stakeholders need to be looped in — and act on it proactively, without waiting for engineers to flag it Recognize when a dependency crosses team boundaries and make sure the teams on both sides of it are actually talking to each other, not just individually on track Chase down answers, escalate when needed, and keep work moving forward Serve as the connective tissue across engineering and adjacent functions throughout the delivery lifecycle — especially where no single team is positioned to see the whole picture Technical context and decision support Follow technical discussions closely enough to grasp the tradeoffs being made — architecture decisions, infrastructure choices, API design, build vs. buy — and understand how those choices ripple into other teams' work Reason about sequencing implications of technical decisions: does this choice change what can be built in parallel versus what must be serial? Surface implications of technical decisions for timeline, scope, or other teams Know when a decision warrants broader input and facilitate getting it, without creating unnecessary process overhead Documentation and operational hygiene Keep the dependency graph, specs, decisions, and timelines documented and accessible Ensure decisions made in Slack or ad-hoc meetings don't get lost, especially ones that affect teams beyond the room they were made in Make it easy for anyone joining a project mid-stream to get up to speed quickly — including understanding why the sequencing is what it is What we're looking for Systems and dependency thinking: You can look at multiple teams' plans and identify where they interlock — where a change in one ripples into another — even when no one team has full visibility into the whole Technical fluency: You don't need to write code, but you need to follow engineering conversations comfortably — architecture diagrams, system tradeoffs, sprint planning — without hand-holding Project management experience: 4+ years managing complex, multi-team software projects with several workstreams and stakeholders in a fast-moving environment — ideally including projects with no single owning team Strong written communication: Able to distill a complex dependency picture into crisp, accurate updates for non-technical audiences Proactive by default: You identify when to loop someone in without b…