UK

United Kingdom · Technology and data · Principal/Manager (12-16 years)

Director of Engineering

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 Director of Engineering 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 bandPrincipal/Manager (12-16 years)
  • Direct reports10-25 reports
  • Reports toVP of Engineering
  • UK framework levelUsually someone running a function, or a director

Also advertised as Engineering Manager (Team of Teams) · Principal Engineering Manager · Head of Engineering (Domain Lead)

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

EAL Level 2 Certificate In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 Diploma In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 Certificate in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 First Certificate in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 Diploma in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 First Diploma in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards

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

The units you would start with

Leading a team in Engineering EAL Level 2 Certificate In Engineering Technologies

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
AI Governance Fluency using AI responsibly
Automation Fluency building AI into how work runs
Systems Fluency seeing the whole picture
Start my Director of Engineering plan, free

2AI and this work

Will AI change your work as a Director of Engineering?

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

The new skills this role is being asked for

  • AI-Driven Engineering Management
  • Advanced Cloud Cost Optimisation (FinOps Leadership)
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 Director of Engineering 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 Director of Engineering plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A Director of Engineering leads engineering managers and shapes technical direction for a major part of a product. The work involves building teams and making sure engineering work supports business goals.

4What you'd actually use

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

Cloud Platforms (AWS/GCP) Strategic

Governing multi-account/multi-cloud strategy, managing enterprise-level cost optimisation using tools like AWS Cost Explorer or CloudHealth. Making strategic build vs. buy decisions on cloud services and ensuring architectural alignment across your domain.

CI/CD & DevOps Toolchain (GitLab CI/GitHub Actions/Jenkins) Architect

Setting the organisation's DevOps strategy for your domain, selecting and standardising the toolchain. You're accountable for DORA metrics, release velocity, and overall system stability across your teams.

Observability Platforms (Datadog/Prometheus/Grafana/Splunk) Strategic

Owning the observability budget and vendor relationships for your domain. Defining the organisation's monitoring and incident response strategy, and using SLO/SLI data to justify headcount and tech debt investment to senior leadership.

Project & Collaboration Tools (Jira/Linear/Confluence/Notion) Strategic

Configuring Jira for executive reporting (e.g., advanced roadmaps, eazyBI for portfolio visibility). Championing a strong documentation culture across your domain and using data from these tools to forecast project delivery and identify team bottlenecks.

Containerisation (Docker/Kubernetes) Architect

Making strategic decisions on container orchestration platforms (e.g., EKS vs. GKE, service mesh like Istio) for your domain. Planning for cluster capacity, security, and cost at an enterprise level.

Financial Planning Software (Anaplan/Pigment/Workday Adaptive Planning) Advanced

Owning and managing a multi-million pound budget for your domain. Conducting headcount planning, cloud spend forecasting, and variance analysis. You'll regularly defend your budget and financial decisions to the CFO.

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
Budget Allocation (Domain) Provides input on specific tool costs or training needs to their manager. Proposes team-level budget requests for specific projects, reviewed by a Senior Engineer. Manages project-level budgets up to £50K, with oversight from a Director. Can approve small purchases (<£5K).
Organisational Design & Headcount No authority. Reports on personal workload. Provides feedback on team structure and capacity to their manager. Suggests minor team adjustments or identifies headcount needs within their project. Involved in interviewing junior roles.
Major Technical Architecture Implements architecture as designed by senior engineers. Contributes to design discussions for specific features, identifying potential issues. Leads architectural design for projects, making technical decisions within project scope. Consults with Staff/Principal Engineers.
Vendor Selection & Contracts Uses existing tools. Suggests new tools for specific tasks, with manager approval. Evaluates technical aspects of potential new tools or services. Recommends vendors for project-specific needs.

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.

DORA Metrics (Domain-wide)
Deployment Frequency, Lead Time for Changes, Mean Time to Recovery (MTTR), and Change Failure Rate for your entire domain.
Target · Achieve 'Elite' status across your domain: Daily deployments, Lead Time < 1 day, Change Fail Rate < 15%, MTTR < 1 hour.

Your domain's average lead time for changes drops from 2 days to 18 hours, and your change failure rate consistently stays below 10% for two consecutive quarters.

Engineering Budget Adherence
How well you manage the allocated budget for your domain, covering cloud spend, tooling, licenses, and headcount.
Target · Maintain budget variance within +/- 5% of the annual plan (for a typical £500K-£2M budget).

Despite unexpected cloud usage spikes, you proactively identified cost-saving opportunities and ended the year with a 3% underspend, reallocating funds to critical tooling.

Regretted Attrition Rate
The percentage of engineers and managers who leave your domain that we genuinely wished we had kept.
Target · Keep regretted attrition below 8% annually across your domain.

Out of 15 departures in your domain this year, only one was a high-performer we wanted to retain, indicating strong retention of key talent.

Business Impact of Engineering Initiatives
The direct contribution of your domain's engineering work to key company objectives, such as revenue growth, cost reduction, or customer satisfaction.
Target · Engineering initiatives in your domain contribute to >10% increase in revenue or >5% reduction in COGS (Cost of Goods Sold) annually.

Your team's work on optimising our payment gateway reduced transaction fees by 7%, directly contributing to a £700K saving this year, and a new feature increased conversion rates by 12%.

Team Health & Morale
The overall well-being, engagement, and psychological safety within your engineering teams.
  • High participation in engagement surveys, positive feedback in 1:1s, low rates of burnout, proactive identification and resolution of team conflicts, strong internal mobility, and a visible culture of trust and collaboration.
Technical Strategy Adoption & Health
How effectively your domain's technical strategy is defined, communicated, and adopted, leading to improved system health and reduced technical debt.
  • Clear, documented architectural decision records (ADRs), measurable reduction in critical bugs, successful completion of major refactoring projects, positive feedback from engineers on system maintainability, and a clear roadmap for addressing technical debt.
Cross-functional Influence & Collaboration
Your ability to effectively influence and collaborate with product, design, operations, and other business functions.
  • Engineering's perspective is consistently sought and valued in strategic planning, strong working relationships with peer leaders, proactive resolution of cross-functional blockers, and joint ownership of outcomes with product teams.
Talent Development & Mentorship
Your commitment to developing the skills and careers of your engineering managers and their teams.
  • Visible career progression for your direct reports (e.g., managers taking on larger scope), effective performance management processes, clear development plans in place, and a culture where knowledge sharing and continuous learning are prioritised.

7Would you like it

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

What people enjoy
Building High-Performing Teams

You'll spend a good chunk of your week coaching your managers, helping them navigate tricky personnel situations, and designing team structures that actually work. Seeing your teams deliver amazing things because you've set them up for success is a huge win for you.

Successfully mentoring an Engineering Manager who then leads their team to deliver a complex project ahead of schedule, with high quality and morale.

Shaping Technical Strategy

You love taking a vague business problem and figuring out the long-term technical vision to solve it. This means whiteboarding sessions, reviewing architectural proposals, and making tough calls on technology choices that will impact us for years. You're thinking 12-24 months out, not just the next sprint.

Defining the architectural roadmap for a new product line that scales to millions of users, balancing innovation with maintainability and cost.

Driving Business Impact Through Engineering

You're not just building software; you're building solutions that directly impact our bottom line or customer experience. You get a kick out of seeing your domain's work directly contribute to revenue growth, significant cost savings, or a measurable improvement in our product's reliability. The numbers matter to you.

Leading an initiative that reduces our cloud infrastructure costs by 15% whilst improving system uptime, directly impacting our profitability.

What frustrates people
  • The Tech Debt vs. Feature Velocity War: The constant, draining negotiation between the Product team's demand for new features and the engineering team's critical need to refactor, upgrade, and pay down technical debt.
  • Inheriting the 'Black Box': Taking over a critical legacy system where the original developers are long gone, documentation is non-existent, and every change feels like defusing a bomb.
  • The Cloud Bill Surprise: Explaining to a non-technical executive team why the AWS bill is not a fixed cost and how a 30% increase can actually be a sign of business success (i.e., scaling to meet demand) – and then having to justify your budget.
  • Managing 'Brilliant Jerks': Dealing with a 10x engineer (or even a manager) who delivers incredible results but demoralises the rest of the team with their abrasive personality. People problems become your problems.
  • The Re-org Treadmill: Having your teams and priorities reshuffled every 9-12 months due to a new executive strategy, killing momentum and causing whiplash. You'll be the one to communicate and implement these changes.
  • Saying 'No' is Your Job: Being the person who has to consistently tell other ambitious leaders that their pet project is technically infeasible, too expensive, or will divert resources from more critical company goals. It's not always fun, but it's essential.
What this role does not give you
  • A lot of hands-on coding. While you'll stay technically sharp, your primary output is through others.
  • Predictable, routine work. Expect constant shifts in priorities and unexpected challenges.
  • Immediate gratification from individual contributions. Your wins are often long-term, strategic, and achieved through your teams.

8Who you work with

This role directly shapes the technical direction and delivery capabilities for a significant portion of our product or platform. Your decisions on architecture, team structure, and talent development will have a multi-year impact on our ability to innovate, scale, and meet customer needs. You'll be directly accountable for a P&L of roughly £500K-£2M, meaning your financial acumen is just as important as your technical chops.

Inside the business
  • VP of Product
  • Head of Operations
  • CFO and Finance Leadership
  • Other Directors of Engineering
  • People & Talent Team
Outside the business
  • Key Technology Vendors (e.g., AWS, Datadog)
  • Industry Peers (for benchmarking)
  • Potential Acquisition Targets (for due diligence)

9What you need before you start

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

  • Proven experience (at least 3-5 years) as a Staff or Principal Engineer (L4), demonstrating the ability to solve ambiguous, cross-team technical problems and set technical direction for a domain.
  • Demonstrable experience managing at least one small team or leading complex projects with significant cross-functional dependencies.
  • A track record of successfully mentoring and developing junior engineers, with clear examples of their growth.
  • Experience defining and delivering technical roadmaps that align with business objectives, not just technical tasks.
  • A solid understanding of cloud infrastructure, CI/CD, and observability best practices at scale.
  • The ability to communicate complex technical concepts effectively to both technical and non-technical audiences.

10What to practise next

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

Platform Engineering & Developer Experience

As organisations scale, providing a seamless, self-service developer experience becomes critical. Your role will increasingly involve defining the strategy for internal platforms, tools, and processes that empower your engineers to deliver faster and more reliably.

Internal Developer Platforms (IDP) · Golden Paths & Templates · Self-Service Infrastructure · Toolchain Consolidation

  • This quarter: Read up on leading platform engineering case studies and frameworks (e.g., Team Topologies).
  • Next quarter: Conduct a 'developer experience' survey within your domain to identify pain points and opportunities.
  • Month 6: Work with a Staff Engineer to draft a proposal for a new internal platform initiative, outlining its benefits and resource needs.
  • Month 9: Present your domain's platform strategy to the VP of Engineering, demonstrating how it will improve velocity and reliability.

Quick win: Identify one major pain point for your developers (e.g., slow local dev environments) and sponsor a small initiative to fix it, demonstrating commitment to developer experience.

11Staying current once you are in

What people here do to keep up
  • Regularly attend industry conferences (e.g., QCon, GOTO, LeadDev) to stay current on engineering best practices and leadership trends.
  • Participate in leadership forums or peer groups with other Directors of Engineering to share insights and tackle common challenges.
  • Engage in continuous learning through online courses (e.g., Coursera, edX) on topics like FinOps, advanced system design, or AI in leadership.
  • Mentor emerging leaders within our organisation or externally, giving back to the community and honing your coaching skills.
  • Contribute to open-source projects or write technical articles, maintaining your technical credibility and thought leadership.

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.

AI-Driven Engineering Management

AI is rapidly becoming a tool for managers, not just engineers. It's about using AI to analyse team metrics, predict project risks, optimise resource allocation, and even draft performance feedback. Leaders who can effectively use these tools will gain significant efficiency and insight.

  • Predictive Analytics for Team Performance
  • Automated Resource Allocation
  • AI-Assisted Feedback & Coaching
  • Ethical AI in Management

Advanced Cloud Cost Optimisation (FinOps Leadership)

Cloud spend is a massive, often unpredictable, line item. As cloud architectures become more complex, the ability to strategically manage and optimise cloud costs becomes a critical leadership skill. It's not just about technical tweaks, but about cultural shifts and financial governance.

  • FinOps Framework & Principles
  • Cloud Cost Allocation & Showback/Chargeback
  • Automated Cost Anomaly Detection
  • Reserved Instances & Savings Plans Strategy

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • System Design & Distributed Architecture
  • Agile at Scale & Delivery Management
  • SRE & DevOps Principles
  • Technical Strategy & Roadmapping
  • Organisational Design & Talent Management (Engineering)
  • Vendor Management & Financial Acumen (Engineering)

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

    From Staff/Principal Engineer (Internal)

    Typically 2-4 years as a Staff/Principal Engineer at L4.

    Skills to master

    • Deepen your architectural expertise, demonstrate cross-team influence without formal authority, mentor multiple junior engineers effectively, and start to think about the commercial implications of technical decisions. You'll need to show you can lead a 'team of teams' from a technical perspective.

    You're ready to move on when

    • Successfully led the technical design and delivery of 2-3 major, cross-domain initiatives.
    • Consistently sought out for advice on complex technical problems by other senior engineers and managers.
    • Demonstrated ability to influence product roadmap decisions with technical insights.
    • Actively mentored at least 2-3 engineers who have shown significant growth or been promoted.
  2. 2

    From Engineering Manager (External)

    Typically 3-5 years as an Engineering Manager at another organisation, with a track record of managing managers.

    Skills to master

    • Showcase your ability to lead multiple teams, manage a significant budget, drive organisational change, and contribute to strategic technical roadmaps. We'll be looking for examples of how you've built and developed high-performing management teams.

    You're ready to move on when

    • Managed a team of at least 10-15 engineers, including 2-3 direct reports who were also managers.
    • Successfully delivered a major product or platform initiative that had measurable business impact.
    • Experience with budget planning and management for an engineering function.
    • Clear examples of how you've developed and retained talent within your teams.
  3. 3

    From Technical Architect / Head of Architecture

    Typically 5-7 years in a dedicated architectural role, with some leadership experience.

    Skills to master

    • While your technical depth is likely strong, you'll need to demonstrate more direct people leadership, budget management, and a focus on organisational design. The shift is from 'what we build' to 'how we build it through people and process'.

    You're ready to move on when

    • Designed and overseen the implementation of enterprise-level architectural solutions.
    • Demonstrated ability to influence and align diverse technical teams on architectural standards.
    • Experience mentoring architects or senior engineers.
    • Understanding of the financial implications of architectural decisions.

15Where this role leads

The long view: This role can lead to Chief Technology Officer, Chief Product and Technology Officer, or Senior Vice President of Engineering.

16Pay and demand

Pay & demand

Typical pay £58,640 a year Source: ONS Annual Survey of Hours and Earnings, 2025 (provisional), under the Open Government Licence v3.0

The figure is the median for full-time employees in the ONS occupation this job title codes to (Production managers and directors in manufacturing), from the April 2025 survey, about six months old when published, as ASHE always is. It is that occupation's middle, not this role's. Half earn more.

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 Director of Engineering is actually changing.

Where it leads

Roles this leads to

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

  • Principal Architect / Distinguished Engineer (IC Path)

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 Leading a team in Engineering, worked against Director of Engineering.

Leading a team in Engineering Level 2

Applied to your work in Director of Engineering

The objective of this unit is to equip learners with an understanding of the roles, responsibilities, knowledge, and skills required to effectively lead a team in an engineering environment. Learners will explore how to manage team workloads, allocate tasks, and contribute to achieving team goals through effective leadership practices.

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 Director of Engineering plan, free
See Your Progress Grow Illustration
Director of Engineering
  • System Design & Distributed Architecture
  • Agile at Scale & Delivery Management
  • SRE & DevOps Principles
  • Technical Strategy & Roadmapping
  • Organisational Design & Talent Management (Engineering)
  • Vendor Management & Financial Acumen (Engineering)
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.

17The 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

Director of Engineering is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. VP of Engineering (L6)

    3-5 years in the Director of Engineering role.

    This is a significant step up, moving from owning a domain to shaping the strategy for an entire business unit or a substantial part of the engineering organisation. Your P&L responsibility will increase dramatically, and you'll be presenting to the board.

    • Enterprise-level technical vision setting.
    • Managing P&L upwards of £2M-£10M+.
    • Driving complex, cross-functional business unit transformations.
    • Strategic vendor and partner ecosystem management.

  2. Principal Architect / Distinguished Engineer (IC Path)

    3-5 years in the Director of Engineering role.

    This is a lateral move, but a deep specialisation, moving back into a pure Individual Contributor (IC) technical leadership role. Your scope of influence remains enterprise-wide, but your focus is on deep technical problem-solving and architectural guidance, not people management.

    • Designing and implementing cutting-edge, complex technical solutions for the entire enterprise.
    • Driving technical innovation and R&D initiatives.
    • Resolving the most challenging, ambiguous technical problems that no one else can solve.
    • Representing the company as a top technical expert externally.
Working with AI on the job

Working with AI

Where AI is starting to help

As a Director of Engineering, your time is gold. It should be spent on strategy, people, and high-level problem-solving, not sifting through reports or drafting repetitive communications. Here at Zavmo, we're embedding AI tools to free up your schedule, giving you back precious hours every week to focus on what truly matters.

Imagine a world where routine management tasks, data analysis, and even initial drafts of complex documents are handled by AI. This isn't science fiction; it's how we're working right now. We're not replacing human judgment, but augmenting it, allowing you to be more effective, more strategic, and less bogged down by operational overhead. Here's how AI will change your day-to-day as a Director:

Automated Status Reporting

Use an AI agent that connects to Jira, GitHub, and PagerDuty APIs. It'll automatically generate weekly progress reports, risk assessments, and incident summaries in natural language for your executive stakeholders. No more late nights compiling updates; the AI does the heavy lifting, leaving you to add the strategic narrative.

Bottleneck Analysis

Feed your CI/CD pipeline logs, observability data, and project management stats into an AI model. It'll identify hidden bottlenecks, highlight which test suites are disproportionately slow, or pinpoint stages with the highest failure rates over time. This gives you actionable insights to optimise your engineering processes without hours of manual data crunching.

Technical Strategy & Doc Drafting

Need to draft a complex technical strategy document? Provide a large language model (LLM) with your business goals, current architecture diagrams, and team skill sets. Ask it to outline potential initiatives, risks, and resource requirements. You'll get a solid first draft in minutes, saving you hours of staring at a blank page.

Performance Review & Feedback Generation

Use an AI assistant to synthesise performance feedback for your direct reports (your managers). Input bullet points from 1:1 notes, project outcomes, and peer reviews, and have the AI draft a structured, well-written performance review. This ensures consistency, saves time, and helps you focus on the human coaching aspect.

Common questions

Common questions

How do you become a Director of Engineering?

Common routes in include From Staff/Principal Engineer (Internal) (Typically 2-4 years as a Staff/Principal Engineer at L4.), From Engineering Manager (External) (Typically 3-5 years as an Engineering Manager at another organisation, with a track record of managing managers.) and From Technical Architect / Head of Architecture (Typically 5-7 years in a dedicated architectural role, with some leadership experience.). Times vary with prior experience.

Where can a Director of Engineering progress to?

This role can lead on to VP of Engineering (3-5 years in the Director of Engineering role.) and Principal Architect / Distinguished Engineer (IC Path) (3-5 years in the Director of Engineering role.), depending on the skills you build.

What new skills matter most for a Director of Engineering?

Increasingly, AI-Driven Engineering Management and Advanced Cloud Cost Optimisation (FinOps Leadership). 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

18Where to go from here

Other roles at Level 6

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 involved in this role transfer to other technology companies, startups and consulting work. Experience in building and scaling engineering organisations, cloud, and DevOps applies across most industries.

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 Director of Engineering 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.