Aligns the teams building Ecoscope, the conservation analytics platform co-developed by EarthRanger and Wildlife Dynamics, turning roadmap priorities into delivery plans that keep analysis tools in practitioners' hands.
Ecoscope is a software platform for wildlife and nature conservation, co-developed by EarthRanger and Wildlife Dynamics. It helps practitioners, data scientists, and developers analyze conservation datasets, run analysis workflows, and produce dashboards, graphs, exports, and reports.
The product suite is supported by two interconnected teams:
The Technical Project Manager (TPM) will make overlaps between these teams visible, manageable, and predictable while supporting delivery coordination, planning, and cross-team alignment. We are looking for someone strongly aligned with Ecoscope’s conservation mission.
We are seeking a senior TPM to coordinate delivery, dependencies, risks, planning, and communication across the Platform and Workflow teams. You will work closely with the Product Owner and Workflow Team Engineering Lead.
This role requires strong Agile delivery experience, technical fluency, excellent communication skills, and a low-ego, collaborative style. You do not need to be a software engineer or architect, but you must understand engineering explanations, appreciate tradeoffs, and translate them into plans, risks, scope options, and stakeholder updates.
The Platform team already has mature Agile practices, including two-week sprints, retrospectives, estimation, release planning, and GitHub Project workflows. Your role is to own and improve these practices where useful, while extending enough shared planning structure to coordinate with the Workflow team.
You will report to the Product Owner, who owns product design decisions, roadmap, and prioritization.
We are looking for someone pragmatic, clear, extremely organized, and collaborative. You should improve team practices without creating process for its own sake, push for clarity and accountability while remaining flexible, and earn trust by listening carefully, asking good questions, and respecting engineering expertise.
You should also be comfortable working across time zones. The Platform team generally works Eastern Time-friendly hours, while Workflow team members are primarily based around Kenya time.
This role owns delivery coordination, dependency management, readiness tracking, risk visibility, and facilitation. It does not own final product, roadmap, prioritization, engineering judgment, product design, engineer management, external client relationships, grants/funder communications, or unilateral decisions on behalf of the Product Owner.
In your first 90 days, you will have enough product, technical, and team context to independently own Platform delivery coordination, including sprint planning, retrospectives, release planning, GitHub Project hygiene, stakeholder updates, documentation/process improvements, and quarterly KR tracking.
You will have built strong working relationships with the Product Owner, Workflow Team Engineering Lead, engineers, QA, design, support, and Workflow counterparts. Platform ↔ Workflow dependencies, risks, blockers, and scope tradeoffs should be clearer, better tracked, and less likely to become surprise release blockers.