Technical Program Manager

The Technical Program Manager (TPM) is HugoHub's internal-facing role. They own delivery of complex, cross-functional technical programmes — ensuring the right things are built correctly, on time, and at scale across Engineering, Product, Design, QA, Compliance, and Operations.

We are looking for a TPM who combines deep technical fluency with programme management rigour and the ability to drive alignment across complex, multi-team organisations. The following qualities define someone who will thrive in this role:

• Problem-Solving: Diagnoses root causes quickly, structures options clearly, and drives to a decision — even under ambiguity and time pressure.

• Attention to Detail: Maintains rigour across programme plans, status reports, and technical decisions — because details missed at planning become issues in delivery.

• Programme Ownership: Takes full accountability for programme outcomes. Drives forward proactively without waiting to be asked — and escalates early with context and options, not just problems.

• Time Management: Manages multiple concurrent programmes across teams with different priorities, holding each to its commitments while keeping the broader delivery picture in focus.

• Communication Skills: Translates fluently between engineering reality and business expectation — giving leadership what they need to decide, and giving engineering teams what they need to execute.

• Adaptability: Restructures approach when priorities shift or scope changes — without losing programme momentum or stakeholder confidence.

• Cross-Functional Leadership: Aligns Engineering, Product, Design, QA, Compliance, and Operations around shared programme goals — driving decisions and clearing blockers across team boundaries without direct authority.

• Technical Translation: Converts engineering constraints, architectural decisions, and technical risks into clear business implications — enabling leadership to make informed, timely decisions.

• Risk and Dependency Management:Identifies risks and dependencies before they become blockers. Builds mitigation plans proactively and communicates trade-offs clearly to the right stakeholders at the right time.

• Technical Acumen: Understands system architecture, APIs, data pipelines, and the SDLC well enough to spot technical risks, challenge estimates credibly, and earn the trust of engineering teams.

The Engine of Cross-Functional Delivery

The TPM is HugoHub's internal delivery engine. They translate strategic objectives into structured, executable programme plans — and then drive those plans to completion across Engineering, Product, Design, QA, Compliance, and Operations. A TPM at HugoHub is not a coordinator. They are a programme owner who holds teams accountable, surfaces risk early, and ensures nothing falls through the gaps between teams.

The core responsibilities of the TPM role at HugoHub:

• Program Planning and Execution: Own end-to-end programme planning and execution — from scoping and goal definition through delivery and stabilisation. Define programme goals, success metrics, milestones, and resource requirements in collaboration with Engineering, Product, and leadership. Track progress in Jira using Agile and Scrum methodologies, maintaining a live view of programme health at all times.

• Project Coordination: Serve as the central coordination point across all programme workstreams — ensuring Engineering, Product, Design, QA, Compliance, and Operations are aligned on scope, timelines, and priorities at every stage. Manage risks, dependencies, and blockers proactively; escalate to the right people with context and a clear recommendation.

• Cross-functional collaboration: Drive alignment across Engineering, Product, Design, QA, Operations, and Compliance — from requirements definition through delivery. Identify blockers, assign ownership, and clear them. Influence and drive decision-making with senior leadership without direct authority over any of the contributing teams.

• Stakeholder Communication: Own stakeholder communication across all levels — from Engineering sprint updates to leadership steering decks. Produce structured programme status reports (RAG health, milestones, risks, decisions needed). Act as the bridge between business objectives and engineering execution, translating in both directions with precision.

• Technical Oversight: Maintain sufficient technical depth to evaluate architecture decisions, challenge estimates, identify technical risks before they surface in delivery, and engage credibly with engineering teams on design trade-offs and SDLC constraints.

• Risk Management: Maintain a live risk and dependency register across all programmes. Identify risks early, assess business impact, develop mitigation plans, and communicate trade-offs to leadership with enough lead time to act — not after the fact.

• Resource Management: Ensure the right engineering and cross-functional capacity is allocated to each programme. Identify resource constraints early and work with team leads and leadership to resolve them before they affect delivery timelines.

• Quality Assurance: Hold programme deliverables to defined acceptance criteria and quality standards. Coordinate with QA on test planning, exit criteria, and defect prioritisation — ensuring quality is built into the programme, not bolted on at the end.

• Continuous Improvement: Continuously identify and implement improvements to programme management practices, tooling, and ways of working across the TPM function and the broader delivery organisation. Share learnings across programmes.

• Documentation and Reporting: Maintain accurate programme documentation — plans, status reports, risk registers, decision logs, and meeting records. Prepare and present programme updates to senior leadership, translating programme complexity into clear business narrative.

• Mentorship: Coach and develop junior TPMs through structured feedback, shared programme experiences, and deliberate knowledge transfer. Raise the capability of the TPM function as a whole — not just your own programmes.

The experience and capabilities we look for:

• 3 to 5 years of hands-on technical programme management experience, owning complex cross-functional programmes end-to-end

• Background in software engineering or a deeply technical role is strongly preferred — this experience underpins the technical credibility the role requires

• Proven track record of driving cross-functional programmes to delivery — with measurable outcomes and demonstrable stakeholder management at senior level

• Proficient in English both written and spoken

• Experience in fintech, banking, or regulated technology environments is a strong plus

• Proficiency in Agile and Scrum methodologies; experience running or coordinating sprints across multiple engineering teams

• Proficiency in Jira for programme tracking, dependency management, and reporting

• PMP, SAFe, or PRINCE2 certification is a plus; what matters more is demonstrated delivery at scale

Quick Win — First 30 Days:

• Map HugoHub's internal team structure, understand each function's role and how they interact in programme delivery

• Learn HugoHub's programme management processes, tooling, and governance frameworks

• Understand HugoHub's product portfolio, active programmes, and client landscape — building context fast enough to contribute to live programmes

• Get hands-on with the systems and platforms used across teams — Jira, internal dashboards, communication and documentation tools

Finding Your Stride — 60 Days:

• Independently manage at least one active programme — running cadence, tracking status, managing risks, and producing stakeholder updates without supervision

• Build effective working relationships across Engineering, Product, Design, QA, and Compliance — with teams trusting you to coordinate their work fairly and accurately

Full Stride — 120 Days:

• Own and drive multiple complex programmes simultaneously — building programme plans, managing cross-functional dependencies, and delivering to committed timelines with minimal escalation

• Proactively identify risks and blockers across your programmes before they surface, assign ownership, and resolve them — with escalation as the exception, not the default

• Identify and implement at least one meaningful improvement to HugoHub's programme management practices — contributing to the TPM function's ongoing development, not just your own programme execution