Senior Project/Program Manager

Location: Remote (EST Hours)

Duration: 3 months+ Extension 

Purpose

Provide detailed delivery management below program level. The program manager holds the overall plan and reports combined status.   This role goes a layer deeper on assigned substreams — decomposing features into tasks, tracking them daily, and chasing the dependencies and decisions that block them. The substreams assigned are likely to be those with the heaviest external dependency load, since that is where detailed tracking pays off most. 

Key responsibilities 

• Take assigned substreams from the backlog — for example tool integrations, attribution and chargeback, or reporting — and manage them at task level beneath the feature and story structure. 
• Decompose stories into tasks with owners and dates, and maintain them accurately enough that the program manager's combined status rests on real progress rather than optimism. 
• Track and chase dependencies within assigned substreams, particularly data population, access grants and schema changes owned by other teams. These do not fail loudly; they arrive late and partial, and surfacing that early is the core of the role. 
• Maintain the decision log for assigned substreams and drive open items to a named decision-maker. 
• Run day-to-day delivery ceremonies for assigned substreams and keep the backlog current as scope evolves. 
• Escalate cleanly and early to the program manager, with the analysis already done rather than the problem simply passed upward. 
• Coordinate across the contract and permanent team members working the same substreams in parallel. 
• Conduct data collection exercises, gathering input and validation of from application owners who’s applications are consuming AI Tokens and generating AI costs.  
• Essential skills and experience 
• Senior delivery management on technical data or analytics programs — data platform, business intelligence, or enterprise reporting. 
• Comfortable operating below a program manager, owning a defined slice rather than the whole, and feeding a combined status they do not author. 
• Demonstrable experience chasing cross-team dependencies where the delivery team does not control the dependency and late partial delivery is the common failure mode. 
• Practical backlog management in Jira or an equivalent, at task level beneath a feature and story structure. 
• Sufficient technical literacy to chair a design discussion about attribution precedence or medallion layer ownership without needing everything translated. The candidate need not be an engineer, but should be able to tell when an answer is evasive. 
• Able to be useful within days on a program already in flight. 

Desirable

• Financial or FinOps context — chargeback, allocation, budget cycles. 
• Atlassian tooling depth, including reporting and automation.