UK

United Kingdom · Technology and data · Senior (5-8 years)

Senior Technical Program Manager

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Start my Senior Technical Program Manager plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

  • Experience bandSenior (5-8 years)
  • Direct reportsNo direct reports
  • Reports toLead Technical Program Manager or Director, Technical Program Management
  • UK framework levelUsually a manager, or the deepest specialist in a team

Also advertised as Senior Programme Lead · Technical Delivery Manager · Senior Project Manager (Technical)

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

Pearson BTEC Level 4 Diploma in Professional Competence for IT and Telecoms Professionals Pearson Education Ltd · Level 4 · covers 1 of 5 standards
Pearson BTEC Level 3 Diploma in Professional Competence for IT and Telecoms Professionals Pearson Education Ltd · Level 3 · covers 1 of 5 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

IT & Telecoms System Management Pearson BTEC Level 4 Diploma in Professional Competence for IT and Telecoms Professionals

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Start my Senior Technical Program Manager plan, free

2AI and this work

Will AI change your work as a Senior Technical Program Manager?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skill this role is being asked for

  • Prompt Engineering & LLM Integration
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Senior Technical Program Manager plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Senior Technical Program Manager plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

Senior Technical Program Manager: leads complex technical programmes from concept to launch, coordinating engineering teams and other functions to deliver major initiatives. The work involves handling technical dependencies, unblocking teams, and keeping everyone aligned. It is hands-on, focused on driving outcomes rather than just reporting on them.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Jira & Confluence Advanced/Expert

You'll design complex workflows, automate processes with rules, build advanced JQL queries and dashboards for leadership, and own the information architecture in Confluence. It's your command centre.

Miro / Lucidchart Expert

You'll lead complex architecture design sessions, create detailed dependency maps, build interactive templates for team use, and visualise programme roadmaps. It's how you make the complex understandable.

Slack / MS Teams Advanced

You'll set up and manage complex channel structures, automate workflows (e.g., with Slack Workflow Builder), and enforce communication best practices across teams. It's your real-time comms hub.

Tableau / Looker Advanced

You'll create new dashboards from existing data sources to track programme-specific KPIs (e.g., delivery predictability, bug trends). You'll also collaborate with data teams to define new data requirements for your programmes.

GitHub / GitLab Intermediate

You'll interpret CI/CD pipeline statuses, understand branching strategies, and facilitate technical discussions around code merges and releases. You won't be writing code, but you'll understand the engineering workflow deeply.

Google Workspace / Microsoft Office 365 Advanced

Creating compelling presentations, detailed spreadsheets for tracking, and collaborative documents. You'll be a wizard with these tools to communicate and organise.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Technical Approach & Methodology Follows established methodologies; escalates any proposed changes to supervisor. Chooses appropriate methodology for routine projects; consults with senior TPMs on variations. Selects and adapts methodologies for complex, ambiguous programmes; makes technical decisions within programme scope (e.g., specific tool choices, process tweaks) with minimal oversight. Consults architects on core system design.
Programme Scope & Timeline Changes Escalates all scope or timeline change requests to supervisor for review and approval. Proposes scope/timeline adjustments for routine projects; requires manager approval for any significant deviation. Identifies potential scope/timeline impacts, proposes mitigation strategies, and makes recommendations to Director and Product leadership. Can approve minor internal timeline shifts (up to 1 week) that don't impact external commitments.
Budget Allocation (Programme-specific) No budget authority; flags any cost implications to supervisor. Tracks programme spending against approved budget; flags overruns to manager. Can approve small purchases (up to £1K) for project-related expenses. Manages programme-specific budget, tracking spend and forecasting. Can recommend budget adjustments up to £10K for tools or services. Requires Director approval for anything above this.
Risk Management & Mitigation Identifies and reports risks to supervisor; executes pre-defined mitigation steps. Identifies risks, proposes mitigation plans, and takes ownership of their execution for routine projects. Escalates high-severity risks. Proactively identifies, quantifies, and develops comprehensive mitigation plans for complex technical and programme risks. Drives execution of these plans with engineering and product. Makes recommendations to leadership on critical risk trade-offs.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Program Predictability
How closely the actual delivery date and scope align with your initial plan and subsequent updates.
Target · 85% of programmes delivered within +/- 10% of the original timeline (or latest committed date).

If a programme was initially slated for a 12-week delivery, you'd aim to launch it between 10.8 and 13.2 weeks. If you hit 12.5 weeks, that's a win for predictability.

Reduction in Blocked Time
The amount of time engineering teams spend waiting on other teams or external factors, which you've actively worked to minimise.
Target · 15% year-over-year reduction in time engineers spend blocked by cross-team dependencies within your programmes.

If your programme's engineering teams collectively spent 100 hours blocked last quarter, you'd aim for no more than 85 hours this quarter by proactively identifying and clearing those roadblocks.

Process Improvement Adoption
Your ability to identify inefficiencies, propose better ways of working, and actually get teams to adopt them.
Target · Successfully rolls out 1-2 major process improvements (e.g., a new technical intake process, a refined release cadence) adopted by 95% of relevant teams per year.

You introduce a new 'technical discovery' phase for all new features, complete with a template and clear hand-off points. Success means 95% of new features go through this process within six months.

Technical Risk Mitigation Rate
The percentage of identified technical risks that have a clear mitigation plan in place and are actively managed, preventing them from becoming issues.
Target · 90% of all high and medium severity technical risks have a documented mitigation plan and are tracked weekly.

You identified a potential scaling issue with a new database. You worked with the architecture team to define a sharding strategy, got it into the backlog, and tracked its implementation, preventing a future outage.

Stakeholder Trust & Influence
How much your key stakeholders (Engineering Leads, Product Managers, Directors) rely on your judgment and proactively involve you in critical decisions.
  • You're consistently invited to early-stage planning meetings, your opinions are sought on technical trade-offs, and you're seen as the 'go-to' person for a clear, unbiased view of programme status and risks. People come to you with problems before they escalate.
Proactive Problem Solving
Your ability to spot potential issues (technical, process, or people-related) before they become major blockers and take action.
  • You're flagging risks in the RAID log weeks before others see them. You're suggesting process tweaks to prevent recurring issues. You're initiating conversations about dependencies that haven't even been formally acknowledged yet. You're not waiting to be told there's a problem
  • you're finding it.
Quality of Mentorship
The impact you have on the growth and development of junior or mid-level TPMs you mentor.
  • Your mentees show demonstrable improvement in their programme management skills, confidence, and ability to handle complex situations. They actively seek your advice, and their managers recognise their growth, often citing your guidance. You're empowering them, not just telling them what to do.
Clarity of Communication
Your skill in translating complex technical details into understandable language for various audiences, and vice versa.
  • Executive summaries are concise and hit the key points without jargon. Engineering teams clearly understand the 'why' behind product requirements. There are fewer 'misunderstandings' or 'lost in translation' moments across your programmes. You can explain microservices to the CEO and business impact to a junior engineer.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Solving Complex Puzzles

You love untangling messy dependencies, figuring out how disparate technical systems can work together, and orchestrating a solution to a seemingly impossible problem. The bigger the puzzle, the more you're energised.

You're faced with three teams, each building a critical component for a new platform, all with conflicting priorities and timelines. Your day involves mapping every dependency, identifying the critical path, and then working with each team lead to align on a realistic, integrated plan.

Driving Visible Impact

You get a real buzz from seeing your programmes actually launch and make a difference to the business or our customers. You're not content with just 'managing' a project; you want to see it succeed.

After months of hard work, a major new technical capability goes live, enabling a new product line. You're tracking the metrics, celebrating with the team, and already thinking about the next big thing.

Empowering & Mentoring Others

You enjoy sharing your knowledge and experience, helping junior TPMs navigate tricky situations, and seeing them grow into more confident, capable leaders. You're a natural coach.

A junior TPM comes to you with a complex stakeholder conflict. Instead of just telling them what to do, you guide them through how to analyse the situation, prepare their talking points, and mediate a resolution, then debrief with them afterwards.

What frustrates people
  • Herding Cats: Being 100% accountable for a programme's success while having 0% direct authority over the engineers doing the actual work. It's all about influence.
  • The Translation Tax: Spending a significant portion of your day acting as a human middleware layer, translating deep technical jargon for business stakeholders and business ambiguity into clear requirements for technical teams.
  • Accountability without Control: Being the single person blamed for a missed deadline that was caused by a team you don't manage deprioritising your critical dependency. It happens.
  • The Glorified Scribe: Fighting the perception that your job is just to take notes in meetings and update Jira tickets, rather than actively driving the programme forward and solving problems.
  • Roadmap Tetris: The constant, exhausting effort of trying to fit immovable stakeholder deadlines and often under-estimated engineering work into a finite timeline, only for priorities to shift again next week.
  • Chasing Status Updates: Having to constantly ping people for updates because they don't proactively communicate progress or blockers, despite your best efforts to build a culture of transparency.
  • The 'Urgent' Executive Request: When a senior leader's 'quick question' or 'small idea' completely derails a carefully planned sprint or programme roadmap, requiring you to re-plan everything on the fly.
What this role does not give you
  • Direct people management responsibilities (though you'll certainly lead and mentor).
  • Deep, hands-on coding or architectural design (you'll understand it, but you won't be writing it).
  • A completely predictable work schedule; urgent issues and shifting priorities are just part of the job.
  • The ability to make unilateral decisions on technical implementation or product features – it's all about collaboration and consensus.

8Who you work with

Your work directly influences our ability to deliver on strategic technical initiatives. Get it right, and we're building the future. Get it wrong, and we're stuck in the past, potentially losing market share or missing critical deadlines. You're driving outcomes for significant business processes, making sure our technical investments actually pay off.

Inside the business
  • Engineering Leads & Managers (your primary partners)
  • Product Managers (who own the 'what')
  • Architects (for technical design decisions)
  • QA & Release Engineering (making sure it actually works and gets out the door)
  • Security & Compliance Teams (ensuring we don't cut corners)
  • Other Senior TPMs (for cross-program dependencies)
Outside the business
  • Key Vendors (if your programme involves external tech or services)
  • Strategic Partners (when integrating with third-party platforms)

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • At least 5 years of experience in technical project or programme management, with a clear track record of leading complex, cross-functional technical initiatives to successful completion.
  • Demonstrable experience in managing technical dependencies across multiple engineering teams and external partners.
  • Proven ability to influence senior technical and business stakeholders without direct authority.
  • Solid understanding of software development life cycles, agile methodologies, and modern cloud architectures.
  • Experience with advanced Jira usage, including workflow design, JQL, and dashboard creation.
  • A knack for identifying and mitigating technical risks before they become major problems.

10What to practise next

Where the job is going, and what to do about it starting this week.

AI-Driven Analytics for Programme Health

Important within 12 months. Tools are emerging that can predict programme delays or identify at-risk dependencies by analysing historical data and current activity. This shifts your role from reactive problem-solving to truly predictive management.

Predictive Modelling for Delivery · Anomaly Detection in Workflows · Sentiment Analysis for Team Health · Automated Dependency Mapping

  • This quarter: Explore existing AI-powered project management tools (e.g., Linear, Jira Product Discovery's AI features) and understand their capabilities.
  • Next quarter: Work with our data science team (if applicable) to see how historical programme data could be used for predictive insights.
  • Month 6: Propose a pilot for an AI-driven programme health dashboard for one of your programmes.
  • Month 9: Learn the basics of data visualisation libraries (e.g., Python's Matplotlib/Seaborn) to interpret and present AI-generated insights effectively.

Quick win: Start experimenting with basic data analysis in Excel or Google Sheets to identify trends in your current programme's data (e.g., average time to close a bug, sprint commitment vs. delivery).

Advanced Cloud Native Architectures & FinOps

Important within 18 months. As our technical footprint grows, understanding how to manage costs and optimise performance in complex cloud-native environments becomes crucial. You'll need to speak the language of cloud architects and finance.

Container Orchestration (Kubernetes) · Serverless Architectures · Cost Optimisation in Cloud (FinOps) · Observability & Monitoring

  • This quarter: Take an online course on cloud fundamentals (e.g., AWS Cloud Practitioner or Azure Fundamentals).
  • Next quarter: Shadow an architect or senior engineer during a design review for a new cloud-native service.
  • Month 6: Read up on FinOps principles and how they apply to programme budgeting and resource allocation.
  • Month 9: Participate in a cost-optimisation initiative for one of our existing cloud services.

Quick win: Familiarise yourself with our current cloud provider's cost explorer dashboards. Just knowing where the money goes is a great start.

11Staying current once you are in

What people here do to keep up
  • Regularly attend industry meet-ups and conferences focused on technical programme management, agile at scale, or specific cloud technologies. Networking and learning from peers is invaluable.
  • Actively participate in internal knowledge-sharing sessions, leading discussions on best practices or lessons learned from your programmes.
  • Dedicate time each quarter to learning a new technical concept or tool that could enhance your programme management capabilities (e.g., a new data visualisation tool, an advanced Jira plugin).
  • Seek out mentorship from more senior TPMs or Directors, both internally and externally, to refine your strategic thinking and leadership skills.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering & LLM Integration

Critical within 6 months—this is already happening, not future. Competitors are using large language models (LLMs) to draft reports in 10 minutes that used to take 2 hours. TPMs who figure this out will outproduce their peers significantly.

  • Context Windows & Token Limits
  • Temperature Settings
  • RAG Architectures
  • Output Validation & Hallucination Detection
  • Prompt Chaining

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Agile & Lean Methodologies
  • System Design & Architecture Concepts
  • Cross-Functional Dependency Management
  • Technical Risk Management
  • Roadmap & Release Planning
  • Data-Driven Programme Management

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Mid-Level Technical Program Manager (L2)

    2-3 years at L2

    Skills to master

    • Mastering end-to-end project delivery, taking ownership of routine processes, identifying and proposing solutions to project-level issues, and beginning to informally guide new joiners.

    You're ready to move on when

    • Consistently delivering complex projects on time and within scope.
    • Proactively identifying and resolving project-level dependencies without constant oversight.
    • Demonstrating strong communication skills with cross-functional peers.
    • Taking initiative to improve project processes or documentation.
  2. 2

    Senior Software Engineer or Architect

    3-5 years in engineering, plus 1-2 years in a technical lead role

    Skills to master

    • Developing strong programme management methodologies, honing stakeholder communication (especially with non-technical teams), understanding broader business context, and learning to lead without direct authority.

    You're ready to move on when

    • Demonstrating a desire to focus on delivery orchestration rather than hands-on coding.
    • Proven ability to lead technical initiatives and influence architectural decisions.
    • Strong organisational skills and an ability to see the 'big picture' beyond individual components.
    • Excellent communication skills, particularly in translating technical concepts to diverse audiences.
  3. 3

    Senior Project Manager (Non-Technical moving to Technical)

    3-4 years in non-technical project management, plus 1-2 years gaining technical depth

    Skills to master

    • Deepening technical understanding (SDLC, cloud, architecture concepts), building credibility with engineering teams, learning agile at scale, and adapting project management skills to highly ambiguous technical environments.

    You're ready to move on when

    • Proven experience managing complex projects with multiple stakeholders.
    • Demonstrable effort in acquiring technical knowledge (e.g., certifications, personal projects).
    • Strong problem-solving skills and an ability to quickly grasp new technical domains.
    • Excellent communication and stakeholder management skills, adaptable to technical audiences.

15Where this role leads

The long view: This role can lead into leading larger teams, becoming a deep technical expert, or moving into new areas such as product management or operations.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Senior Technical Program Manager is actually changing.

Where it leads

Roles this leads to

Also named as a next step, with no page in the catalogue yet:

  • Technical Program Manager Manager (L5)

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from IT & Telecoms System Management, worked against Senior Technical Program Manager.

IT & Telecoms System Management Level 4

Applied to your work in Senior Technical Program Manager

This unit aims to provide learners with the knowledge and skills to effectively manage IT and telecoms systems within an organisation. Learners will analyse existing systems, identify areas for improvement, and implement management strategies that align with best practices and industry standards, ensuring efficient and secure operations.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Senior Technical Program Manager plan, free
See Your Progress Grow Illustration
Senior Technical Program Manager
  • Agile & Lean Methodologies
  • System Design & Architecture Concepts
  • Cross-Functional Dependency Management
  • Technical Risk Management
  • Roadmap & Release Planning
  • Data-Driven Programme Management
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

16The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Senior Technical Program Manager is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Staff Technical Program Manager (L4)

    3-5 years as a Senior TPM

    This is a significant step up, moving from managing complex programmes to architecting and improving org-wide processes and managing a portfolio of related programmes. You'll be solving the toughest dependency challenges across the business.

    • Advanced Systems Thinking Applying a truly holistic view to solve problems that span the entire technical ecosystem.
    • Cross-Organisational Dependency Resolution Solving the most complex, politically charged dependency issues across the entire company.
    • Tooling & Automation Strategy Defining the strategy for our programme management tools and automation, ensuring they meet organisational needs.
    • Business Case Development Building robust business cases for new technical initiatives, including ROI analysis and resource planning.

  2. Technical Program Manager Manager (L5)

    4-6 years as a Senior TPM (or Staff TPM)

    This path involves stepping into people management, leading a team of TPMs. You'll be responsible for their growth, performance, and the overall delivery of a major technical domain or department's portfolio.

    • Portfolio Strategy Defining the programme management strategy for a major technical domain or department.
    • Stakeholder Alignment at Executive Level Ensuring programme delivery aligns with executive-level strategic objectives.
    • Process Governance Establishing and enforcing best practices and standards across your team and potentially the wider organisation.
    • Talent Development Identifying skill gaps within your team and developing plans to address them.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, a lot of programme management can feel like repetitive admin or chasing information. But what if you could offload a chunk of that to AI? We're not talking about replacing you; we're talking about giving you superpowers. Imagine spending less time on status reports and more time actually solving the hard problems.

At Zavmo, we're serious about giving our Senior TPMs the best tools. Our AI Productivity Hub is packed with ways to automate the tedious bits of your job, letting you focus on the strategic thinking, complex problem-solving, and crucial stakeholder influence that only a human can do. Here's a glimpse of how AI can transform your day-to-day:

Automated Scribe & Summariser

Use AI meeting assistants (like Fathom or Otter.ai) to automatically transcribe your programme meetings, identify action items, and generate concise summaries. These can then be distributed straight to Slack and Confluence, saving you hours of note-taking and follow-up. You'll spend less time writing and more time listening and leading.

Risk & Dependency Forecaster

Imagine AI tools scanning your Jira backlogs, Confluence pages, and even Slack channels to flag potential dependencies or risks that haven't been explicitly linked. For example, 'AI detected similar keywords in Team A's API spec and Team B's feature brief. Is there an un-tracked dependency?' This helps you proactively identify issues before they become major blockers, giving you a huge head start.

First-Draft Factory

Leverage large language models (LLMs) like ChatGPT or Claude to generate the first draft of project briefs, communication plans, stakeholder updates, and even risk registers. Just feed it a few bullet points and key data, and you'll get a solid starting point, cutting down on the blank-page syndrome and speeding up your documentation process significantly. You'll spend your time refining, not starting from scratch.

Stakeholder Comms Customiser

Feed a detailed technical status update into an AI model and ask it to generate tailored summaries for different audiences. Need a high-level business impact summary for the CEO? A financial update for the CFO? A resource-focused summary for engineering leads? AI can draft these variations for you, ensuring your message lands perfectly with each group, saving you precious time on bespoke reporting.

Common questions

Common questions

How do you become a Senior Technical Program Manager?

Common routes in include Mid-Level Technical Program Manager (2-3 years at L2), Senior Software Engineer or Architect (3-5 years in engineering, plus 1-2 years in a technical lead role) and Senior Project Manager (Non-Technical moving to Technical) (3-4 years in non-technical project management, plus 1-2 years gaining technical depth). Times vary with prior experience.

Where can a Senior Technical Program Manager progress to?

This role can lead on to Staff Technical Program Manager (3-5 years as a Senior TPM) and Technical Program Manager Manager (4-6 years as a Senior TPM (or Staff TPM)), depending on the skills you build.

What new skills matter most for a Senior Technical Program Manager?

Increasingly, Prompt Engineering & LLM Integration. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

17Where to go from here

Other roles at Level 5

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

 More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills built in this role transfer well. They can lead into broader leadership roles in product management, operations, or consulting. The ability to coordinate complex technical delivery and influence without formal authority is useful across tech-driven organisations, including FinTech, HealthTech, SaaS and eCommerce.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my Senior Technical Program Manager plan, free What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.