We are building a new generation corporate data platform: we are integrating data loading, storage, processing, and usage into a single standardized path. We are gradually replacing disparate solutions and migrating existing processes to a new stack.
Two main teams work on the platform, collectively responsible for the entire data journey — from loading and storage to preparing data marts and analytics tools. The teams are closely connected and interact extensively with other departments of the company.
As the platform evolves, the number of parallel initiatives, dependencies, migrations, and external interactions grows. We are looking for a Technical Project Manager / Delivery Manager who will take charge of the operational aspects of the platform: help teams plan their work, synchronize with each other and with adjacent teams, manage risks and dependencies, and bring initiatives to completion.
This is not a role of a second platform lead or a technical lead. The strategy and priorities remain with the data platform lead, and technical solutions and engineering quality remain with the team leads. Your task is to make the teams' work transparent and predictable and to raise issues that require management decisions in a timely manner.
What you will do
- Manage the overall platform initiatives plan: stages, deadlines, dependencies, responsible parties, and expected results.
- Synchronize the work of the two platform teams and coordinate dependencies with other company departments.
- Together with team leads, transform large initiatives into a realistic plan and monitor the progress of key stages.
- Proactively identify risks and blockers, help find solutions, and escalate issues that teams cannot resolve independently in a timely manner.
- Maintain the platform development plan and team plans up-to-date.
- Coordinate migrations, pilots, and the implementation of new platform features.
- Manage operational communication with adjacent teams and internal customers: record agreements, deadline changes, dependencies, and next steps.
- Organize and develop team processes: planning, retrospectives, regular meetings, and inter-team synchronizations. Change the process if it stops helping the team's work.
- Monitor the execution of agreements after meetings: a significant decision should have a next step, a responsible person, and a deadline.
- Together with team leads, establish the on-call process: maintain a clear schedule, handover procedures, and escalation paths. Technical rules and requirements remain the responsibility of the team leads.
- Organize incident reviews: gather participants, record conclusions and tasks based on the outcomes, and monitor their execution. Technical analysis of causes and solution selection remain with the team and team lead.
- Monitor the state of work processes: identify recurring blockers, stalled tasks, accumulation of unfinished work, and problems in team interactions.
- Develop processes together with the teams and use a set of metrics that help identify problems and make decisions.
- Keep Jira and Confluence in a state where the progress of major initiatives can be understood without manual status collection.
How we divide responsibilities
The Data Platform Lead is responsible for strategy, priorities, organizational decisions, and key agreements.
Team Leads are responsible for teams, technical planning, architectural decisions, estimates, engineering standards, quality, and system stability.
Technical Project Manager / Delivery Manager is responsible for the operational organization of work: overall plan, deadlines, dependencies, risks, participant interaction, team processes, and transparency of the current state.
In shared areas, we divide content and process. For example, a team lead determines how on-call duties should be technically organized or what needs to be changed after an incident. The project manager helps ensure that the process itself works, agreements are met, and problems are not lost.
Technical Context
The work is related to data platform development teams. Deep technical expertise in this area is not required, but it is important to understand how the software development process works, where technical dependencies and risks arise, and how they affect deadlines and plans.
You need to be able to understand the technical context at a level sufficient for collaboration with engineers and team leads: ask questions, record limitations, and consider them during planning.
We'll be glad if you
- Have experience in IT project management or organizing result delivery in development teams.
- Have worked with engineering, platform, or infrastructure teams and understand the software development lifecycle.
- Can simultaneously manage several related initiatives and see dependencies between them.
- Can turn a large and not yet fully defined task into a clear work plan and refine it together with the team.
- Work with risks and blockers proactively, not just track their status.
- Can organize meetings so that they end with decisions and clear next steps.
- See systemic problems in processes and know how to change the way of working with the team, not just add new rules.
- Can negotiate and achieve results without formal authority over participants.
- Can work with engineers and team leads without being a developer.
- Structure information well and can concisely document context, decisions, responsible parties, and next steps.
- Understand when a process helps the team's work and when it creates unnecessary overhead.
It will be a plus if you have
- Experience with platform, infrastructure, or data teams.
- Experience with large technical migrations.
- Experience coordinating multiple engineering teams.
- Experience organizing on-call duties and incident review processes.
- Experience working with internal platforms and tools for company employees.
