United Kingdom · Technical roles · Mid-Level (2-5 years)

Automation Developer

Here is the whole job, in plain words. What it is, a real day, 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.

Experience bandMid-Level (2-5 years)
Direct reportsNo direct reports
Reports toSenior Automation Developer or Lead Automation Engineer
UK framework levelUsually a coordinator, or early in a professional job

Also advertised as RPA Developer · Bot Developer · Automation Engineer

Built on an analysis of 43,079 real UK job descriptions · grounded in qualifications employers recognise

Start with a free Future Fluency check, tuned to Automation Developer

Ten quick questions, one per Future Fluency, asked against this role rather than a generic one. About five minutes, and no card.

Start the check, free

1What this role really is

You'll be building the actual 'digital workforce' that helps our business run smoother. This isn't just about making things faster; it's about making them more reliable and freeing up our colleagues to do more interesting work. You'll take a process, figure out how to automate it, then build, test, and get the bot running. It's hands-on, problem-solving work, and you'll see the direct impact of what you create.

2What you'd actually use

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

UiPath Studio/Automation Anywhere CreatorAdvanced

Building, testing, and deploying moderately complex automation workflows, including robust error handling and data manipulation.

UiPath Orchestrator/AA Control RoomIntermediate

Monitoring bot performance, managing queues, scheduling automations, and troubleshooting production issues.

Python (pandas, requests, Selenium)Expert

Writing scripts for complex data manipulation, web scraping, API interactions, and developing custom activities for RPA platforms.

Direct API Calls (REST/SOAP)Intermediate

Using Python's `requests` library or built-in RPA connectors to perform simple data lookups or updates directly with other systems.

AWS S3/Azure Blob StorageIntermediate

Using cloud storage for input/output files for automation processes, ensuring secure and scalable data handling.

Jira/ServiceNowAdvanced

Managing automation development tickets, tracking progress, providing status updates, and documenting resolution steps for bot issues.

Excel/Google SheetsExpert

Advanced data analysis, creating pivot tables and charts for weekly status reports, and manipulating data for bot inputs/outputs.

3What 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 choice	Coming in	Where you are now	The step above
Technical Approach for a New Bot	Proposes an approach to senior developer for approval; follows detailed instructions.	Independently designs the bot's technical architecture and workflow; consults lead on complex integrations or novel challenges.	Defines the technical approach and standards for multiple bots or a workstream; reviews and approves approaches from junior developers.
Troubleshooting Production Bot Failure	Escalates immediately to senior developer with initial findings.	Diagnoses the issue, implements a fix, and informs lead of resolution; escalates if unable to resolve within a defined timeframe or if impact is critical.	Leads the troubleshooting effort, coordinates with IT, and makes decisions on hotfixes or temporary workarounds; communicates impact to stakeholders.
Changes to Project Scope/Timeline	Informs supervisor of any potential delays or scope creep.	Identifies potential impact of changes, proposes adjusted timelines, and discusses with lead before committing.	Negotiates scope changes with business stakeholders, assesses impact on workstream, and makes recommendations to programme manager.
Selection of Automation Tools/Libraries	Uses tools/libraries as directed by senior developer.	Selects appropriate built-in RPA activities or Python libraries for specific tasks; researches and proposes new, small-scale tools for specific problems to lead.	Evaluates and recommends new tools or frameworks for the team's tech stack; sets standards for tool usage.

4How you'll be judged

The scoreboard, honestly: the hard targets, how often each one is actually looked at, and the quiet human signals that never make it onto a dashboard.

Bot Error Rate

The percentage of times your deployed automations fail or require human intervention.

Target · Below 3% for owned bots

If your bot processes 1,000 transactions and 25 need manual fixing, that's a 2.5% error rate – which is good.

Development Velocity

How quickly you deliver automation components or entire bots, compared to initial estimates.

Target · Within +/- 10% of story point estimates

If a task was estimated at 8 story points and you finished it in a timeframe equivalent to 7.5 or 8.5 points, you're spot on.

Manual Hours Automated

The estimated time saved by the business due to the automations you've built and deployed.

Target · Contributes to projects saving 500-2,000 hours/year

Your new invoice processing bot saves the Finance team 40 hours a month, contributing 480 hours to the annual target.

Bot Uptime

The percentage of time your critical bots are running as expected, without unplanned downtime.

Target · Achieves >98% uptime for owned production bots

If your bot is meant to run 24/7, and it's down for less than 3.5 hours in a month, you're hitting the target.

Code Quality & Maintainability

How clean, well-structured, and easy to understand your automation code is, including comments and adherence to best practices.

Positive feedback during code reviews from senior developers
minimal refactoring needed by others
clear documentation within the code itself.

Proactive Problem Solving

Your ability to spot potential issues before they become major problems, or to quickly diagnose and fix bot failures.

Identifying a potential application change that could break a bot and addressing it before it happens
quickly troubleshooting and resolving production bot errors with minimal guidance
proposing improvements to existing automations.

Stakeholder Communication

How effectively you communicate progress, issues, and technical details to non-technical business users and your team.

Business users understand bot functionality and limitations
clear and concise status updates
proactively asking clarifying questions during requirements gathering to avoid rework.

Contribution to Team Knowledge

Sharing your learnings and helping other team members improve their skills.

Informally guiding new joiners
contributing to internal knowledge base articles
actively participating in team discussions and sharing insights from your projects.

5Would you like it

The honest version. What people enjoy, and what grinds them down.

What people enjoy

Solving Puzzles & Building Solutions

You get a real kick out of taking a complex, manual process, breaking it down, and then seeing your bot handle it perfectly. The satisfaction of a clean, efficient automation running without a hitch is what drives you.

You've just finished a bot that processes 500 invoices a day, error-free. You see the Finance team celebrating their early month-end close, and you know you made that happen.

Seeing Tangible Impact

You want to build things that actually get used and make a difference. The idea of your work directly improving efficiency, saving time, or reducing errors for colleagues is a big draw.

An Operations manager tells you how your new bot has cut their team's data entry time by 30%, allowing them to focus on customer service instead.

Continuous Learning & Mastery

You're always keen to learn a new trick, a new feature in the RPA platform, or a better way to handle exceptions. You enjoy diving into documentation and experimenting with new approaches.

You spend a Saturday morning playing around with a new Python library that you think could make your next bot's data manipulation much faster.

What frustrates people

Automating Undocumented Processes: Being asked to automate a critical process that exists only in the head of a 30-year veteran who is about to retire, forcing you into a painful forensic documentation exercise.
The Maintenance Iceberg: Stakeholders see the upfront development cost but vastly underestimate the long-term effort required to maintain, update, and support a growing fleet of bots as underlying applications and processes change.
The UI Change Domino Effect: The Salesforce team rolls out a minor UI update over the weekend, and you come in Monday to 500 alert emails because half your bot fleet is broken and can't find the buttons they need to click.
The 'Pave the Cowpath' Pressure: Being pressured to automate a clearly inefficient process without fixing it first, which feels like cementing bad practice in code.

What this role does not give you

A perfectly stable, unchanging technical environment – things will break, and systems will evolve.
Complete autonomy over strategic direction – you'll be building solutions, not setting the overall automation strategy.
A role focused purely on cutting-edge research – this is about practical, applied automation for business problems.

6Who you work with

Your work directly improves operational efficiency and data accuracy across various business functions. Essentially, you're building the digital cogs that keep the business machine turning smoothly, allowing human colleagues to focus on higher-value tasks and reducing the risk of manual errors. If your bots are reliable, the business benefits from speed and precision; if they're not, it can cause significant operational disruption.

Inside the business

Operations teams (who use your bots)
Finance (for month-end processes)
IT Support (for infrastructure and troubleshooting)
Product teams (when integrating with new systems)

Outside the business

Software vendors for RPA platforms (e.g., UiPath, Automation Anywhere)

7What you need before you start

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

2-5 years of hands-on experience building and deploying automations using a leading RPA platform (e.g., UiPath, Automation Anywhere), or equivalent experience in software development with a strong focus on process automation.
Demonstrable proficiency in Python for scripting, data manipulation, and API interactions. We'll want to see some of your work.
A solid understanding of software development principles, including version control (Git), testing methodologies, and debugging techniques.
Experience working with business stakeholders to gather requirements and translate them into technical solutions.
A good grasp of how to design resilient automations that can handle exceptions and unexpected scenarios.

8What to practise next

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

Advanced Data Engineering for Automation

As automations become more sophisticated, they'll need to handle larger, more complex datasets. You'll need to move beyond basic data manipulation to more robust data pipelines.

Data warehousing concepts · ETL/ELT processes · Cloud data services (e.g., Azure Data Factory, AWS Glue)

This quarter: Take an online course on SQL optimisation or data modelling.
Next quarter: Work on a project that involves pulling data from multiple, disparate sources for an automation.
Within 6 months: Explore a cloud data service and try to build a simple data pipeline for a bot.

Quick win: Refactor an existing bot's data input process to make it more efficient and less prone to errors.

Cloud-Native Automation Orchestration

More and more of our infrastructure is moving to the cloud. Your bots won't just run on virtual machines; they'll be part of larger, event-driven cloud workflows.

Serverless functions (AWS Lambda/Azure Functions) · Event-driven architectures · Cloud monitoring and logging

This quarter: Deploy a simple Python script as an AWS Lambda function or Azure Function.
Next quarter: Integrate one of your bots with a serverless function to handle a specific task.
Within 6 months: Learn about message queues (e.g., SQS, Azure Service Bus) and how they can orchestrate automation workflows.

Quick win: Get familiar with the basics of our chosen cloud platform (AWS or Azure) and its core services.

9Staying current once you are in

What people here do to keep up

Actively participate in online automation communities (e.g., UiPath Forum, Automation Anywhere A-People Community) to learn from peers and share your knowledge.
Attend webinars and virtual conferences on RPA, intelligent automation, and emerging AI technologies.
Dedicate time each week to exploring new features in our RPA platforms or experimenting with new Python libraries.
Seek out opportunities to mentor junior developers or new joiners, even informally – teaching is a great way to solidify your own understanding.
Take online courses (e.g., from Coursera, Udemy, Pluralsight) on advanced Python, cloud computing, or specific integration technologies.

10How the AI economy is changing work like this

Before we ask anything of you, here's what we can already say about AI and work of this kind:

The new skill this role is being asked for: Prompt Engineering & LLM Integration

Honestly, large language models (LLMs) like ChatGPT are changing how we interact with data and generate content. Competitors are already using them to draft reports in 10 minutes that used to take 2 hours. Developers who figure this out will outproduce peers 3:1, and we want you to be one of them.

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

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

Honestly, large language models (LLMs) like ChatGPT are changing how we interact with data and generate content. Competitors are already using them to draft reports in 10 minutes that used to take 2 hours. Developers who figure this out will outproduce peers 3:1, and we want you to be one of them.

Context windows and token limits
Temperature settings for different tasks
RAG (Retrieval-Augmented Generation) architectures
Output validation and hallucination detection
Prompt chaining for complex analysis

Low-Code/No-Code Platform Integration

Business users are increasingly empowered to build their own simple automations or apps using platforms like Microsoft Power Automate or Appian. Your role will shift from building everything from scratch to integrating with and governing these 'citizen developer' solutions.

Citizen Developer Governance
API-first integration
Workflow orchestration
Security and compliance in low-code

What you’ll use

Skills this role draws on

Technical

Intelligent Automation (IA) Principles
Agile for Automation Delivery
Exception Handling & Resilience Design
Process Analysis & Optimisation

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
Junior Automation Developer
1-2 years
Skills to master
- Building simple, linear automations from detailed specifications
- rigorous testing
- basic debugging
- understanding core RPA platform features.
You're ready to move on when
- Consistently delivers assigned automation components on time and with minimal errors.
- Can independently troubleshoot basic bot failures.
- Demonstrates a solid understanding of our chosen RPA platform's core functionalities.
- Proactively asks clarifying questions during requirements gathering.
2
IT Support / Operations Analyst with Scripting Experience
2-3 years
Skills to master
- Translating operational pain points into automation opportunities
- strong scripting (e.g., Python, PowerShell) for task automation
- understanding of IT systems and infrastructure.
You're ready to move on when
- Has successfully automated routine IT or operational tasks using scripts or basic tools.
- Possesses a deep understanding of specific business processes that are ripe for automation.
- Can articulate the business value of automation beyond just 'saving time'.
- Shows a keen interest in learning and applying RPA technologies.
3
Business Analyst with Technical Aptitude
2-4 years
Skills to master
- Detailed process mapping and requirements gathering
- understanding of business logic
- ability to translate business needs into technical specifications
- some exposure to coding or scripting.
You're ready to move on when
- Excellent at documenting 'as-is' and 'to-be' processes with high fidelity.
- Can clearly articulate business problems and potential automation solutions.
- Has a basic understanding of programming concepts and logical flow.
- Demonstrates a strong desire to move into a hands-on development role.

11Where this role leads

The long view:Your journey as an Automation Developer is just the beginning. The skills you master here are in high demand and will open up a world of opportunities, whether you choose to deepen your technical expertise or move into leadership. We're excited to see where you take it.

Pay & demand

Pay and demand for this role will appear here, each figure traced to a named authoritative source (e.g. the ONS Annual Survey of Hours and Earnings, under the Open Government Licence). We don’t show numbers we can’t attribute.

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 Automation Developer is actually changing. In about two minutes, the free confidence check asks where you stand on each of the ten. That's the whole check, and it's what makes the plan yours rather than generic.

12The team that's yours

No two people are taught the same way. This is one-to-one, not one-to-many.

Zavmo is a hyper-personalised AI learning platform. Twelve virtual tutors, each with a different way of teaching, and one orchestration agent that picks the right one for the moment. So every single lesson is shaped around you, your role, and the way you learn. Not a course everyone sits through. A conversation built for you, and no one else.

…and nine more, matched to you after your first chat. Meet all twelve

Start free and meet yours

13What it feels like

A conversation, not a course

Because your tutor knows your role, your projects and your last session, learning sounds like this. And it's different for every single person:

Automation Systems and Industrial RoboticsLevel 3

Applied to your work in Automation Developer

This unit aims to provide learners with a comprehensive understanding of automated systems and industrial robotics within manufacturing environments. Learners will explore the components, functions, and integration of control, sensing, and actuation systems within automated work-cells, enabling them to understand the design and operation of these systems.

How the thinking builds

Remember
Understand
Apply
Analyse
Evaluate
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.

One to one, not one to many

No two people run this the same way

A course is written once and handed to everyone. This is assembled around you, and keeps changing as it learns you. Five things it reads, and what each one changes.

Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
What you already know The first conversation finds your starting point, so you skip what you can already do and spend the time on what you cannot.
The conditions you learn under Not a learning-styles quiz. The evidence does not support those. The dimensions the research does back, read once and used to shape the plan.
How far you got last time It picks up mid-thought. The tutor knows what you said, what you struggled with, and what it asked you to try.
Which tutor suits the moment Twelve of them, each for a different kind of thinking. The one who walks you through a first idea is not the one who stress-tests it.

See how you learn, free. Eight questions, no sign-up. A directional taster; the diagnostic inside Zavmo goes deeper and keeps adapting.

DemonstrateIllustration

Evidenced on your work in Automation Developer

You do not finish by watching something. You finish by showing it on the work you already do, against the measures this job is judged on.

Bot Error RateThe percentage of times your deployed automations fail or require human intervention.If your bot processes 1,000 transactions and 25 need manual fixing, that's a 2.5% error rate – which is good.Below 3% for owned bots
Development VelocityHow quickly you deliver automation components or entire bots, compared to initial estimates.If a task was estimated at 8 story points and you finished it in a timeframe equivalent to 7.5 or 8.5 points, you're spot on.Within +/- 10% of story point estimates
Manual Hours AutomatedThe estimated time saved by the business due to the automations you've built and deployed.Your new invoice processing bot saves the Finance team 40 hours a month, contributing 480 hours to the annual target.Contributes to projects saving 500-2,000 hours/year
Bot UptimeThe percentage of time your critical bots are running as expected, without unplanned downtime.If your bot is meant to run 24/7, and it's down for less than 3.5 hours in a month, you're hitting the target.Achieves >98% uptime for owned production bots

These are this job's own measures, with its own targets. Nothing is marked evidenced, because nobody has started this yet. Yours would fill in from the work you bring.

Your passport

This isn't a certificate you file away. It's a passport to the life you're designing.

Every credit you earn and every fluency you build adds up: evidence where it counts, carried with you. Zavmo keeps the map: where you are, where you're heading, and the next step, at your pace, around your life. From Automation Developer to Senior Automation Developer, and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior Automation Developer→ your design

Where this takes you

Your journey as an Automation Developer is just the beginning. The skills you master here are in high demand and will open up a world of opportunities, whether you choose to deepen your technical expertise or move into leadership. We're excited to see where you take it.

See Your Progress GrowIllustration

Automation Developer

Intelligent Automation (IA) Principles
Agile for Automation Delivery
Exception Handling & Resilience Design
Process Analysis & Optimisation

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.

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

Automation Developer is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

Senior Automation Developer
2-3 years from this role
You'll move from independently building solutions to leading the design of complex automations and mentoring others.
- Advanced Solution Design: Architecting resilient, scalable automation solutions for entire workstreams.
- Reusable Component Development: Building and maintaining a library of shared automation assets.
- Performance Optimisation: Identifying and implementing ways to make bots run faster and more efficiently.
- Security by Design: Ensuring all automations adhere to the highest security standards from the outset.

Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, a lot of what we do as Automation Developers involves digging through data, drafting documents, and figuring out the best way to tackle a problem. What if you could cut down on those time-consuming tasks and focus more on the actual building and problem-solving? That's where AI comes in.

You're already building the future with automation, so why not use AI to make your own work smarter? We're embracing AI as a co-pilot for our developers, helping you tackle everything from identifying new opportunities to drafting communications. It's about augmenting your skills, not replacing them, so you can deliver more value, faster.

Pipeline Generation Assistant

Imagine using AI-powered process mining tools (like Celonis) to analyse system logs from our core applications. Instead of manual workshops, AI can automatically generate a data-backed, prioritised list of the top 10 automation opportunities, complete with estimated ROI. This means you're building the *right* bots, not just the ones people *think* they need.

Business Case Co-Pilot

Need to justify a new automation project? Use a generative AI model, trained on our company's financial data, to draft the initial business case. You can prompt it with specifics like 'Draft a business case for automating AP invoice processing, assuming 5 FTEs, 20,000 invoices/month, and an error rate of 4%.' This frees you up from crunching numbers from scratch.

Risk & Compliance Scanner

Before you even start coding, use an AI tool to scan your Process Design Documents (PDDs) and even early bot code. It can check against our internal compliance rules (like GDPR or SOX) to flag potential risks, such as handling sensitive data incorrectly or lacking proper audit trails. This catches problems early, saving painful rework later.

Stakeholder Comms Generator

You'll need to keep various people updated. Use generative AI to draft tailored weekly progress updates for different audiences. Ask it to 'Summarise our automation progress this week for an executive audience, focusing on ROI and business impact.' Then, 'rewrite it for the IT Security team, focusing on compliance and credential management.' It saves you hours of fiddly re-wording.

Common questions

How do you become an Automation Developer?

Common routes in include Junior Automation Developer (1-2 years), IT Support / Operations Analyst with Scripting Experience (2-3 years) and Business Analyst with Technical Aptitude (2-4 years). Times vary with prior experience.

Where can an Automation Developer progress to?

This role can lead on to Senior Automation Developer (2-3 years from this role), depending on the skills you build.

What level is an Automation Developer in the UK?

This role aligns to RQF Level 3 on the UK framework, a guide to the depth of qualification it maps to, not a hard entry bar.

What new skills matter most for an Automation Developer?

Increasingly, Prompt Engineering & LLM Integration and Low-Code/No-Code Platform Integration. These are the areas where the higher-paid, future-proof work is heading.

The honest bit

You’ve started things before

Most of them were built for a room full of people who aren’t you. A cohort moves on whether or not your week allowed it, and by the third week the thing you’re behind on becomes the reason you stop opening it.

There’s no cohort here, and no timetable to fall behind. Before anything starts, Zavmo asks when you’re sharpest and how long you can realistically sit down for, then builds the sessions around those answers. A bad fortnight changes your pace. It doesn’t put you behind.

And you only pay once you start learning. Searching and planning are free, and you can cancel any time — so the cost of finding out is an afternoon, not a year.

What it costs

Less than one coaching session. Every month.

A single career-coaching hour costs more than a month of this, and it ends when the hour does. Zavmo doesn't. It's £70 a month, about £2.30 a day, for a companion that knows an Automation Developer, works on the job you actually do, and keeps going at your pace rather than a timetable's.

Searching and planning stay free. You only pay when you start learning.
Your credits are yours. Regulated, and they don't vanish when a subscription ends.
Cancel any time and billing stops. No notice period, no minimum term.

Your path, personalised

You have the map. Walking it is the part we do together.

This route runs to 3 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming an Automation Developer: personal to you, and it still counts. The first steps are free.

Independent research finds well-designed intelligent tutoring performs nearly as well as one-to-one human tutoring: VanLehn (2011), Educational Psychologist.

A private tutor in the UK averages £35–40 an hour . Zavmo is £70/month.

A Zavmo curriculum screen: a three-month plan built for a customer support lead, five Ofqual-regulated units and a hundred and ninety-six credits. — A real plan on learn.zavmo.ai: Ofqual-regulated units, credits, and a three-month run at your own pace.

Start free No commitment. See your first steps free.

15Where to go from here

Other roles at Level 3

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

Other roles in Technical roles

Stay in the field you know and move sideways rather than up.

If you leave this industry

The skills you'll gain here – process analysis, solution design, technical problem-solving, and working with various business functions – are highly transferable. You could move into broader software engineering roles, business process improvement, data engineering, or even product management for automation tools in other industries.

Not sure this is the right direction?

Work out what you actually want from work first, then come back and see which roles fit it. Takes about ten minutes.

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. Build my plan, free Here's the first ten minutes: a 2-minute confidence check → your personalised roadmap → meet the tutors matched to you. No card, cancel any time. 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.

Automation Developer

What's rising in its place

Prompt Engineering & LLM Integration

Low-Code/No-Code Platform Integration

Skills this role draws on

Technical

How you actually get there, here

Junior Automation Developer

IT Support / Operations Analyst with Scripting Experience

Business Analyst with Technical Aptitude

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

Roles this leads to

No two people are taught the same way. This is one-to-one, not one-to-many.

A conversation, not a course

No two people run this the same way

This isn't a certificate you file away. It's a passport to the life you're designing.

Your journey as an Automation Developer is just the beginning. The skills you master here are in high demand and will open up a world of opportunities, whether you choose to deepen your technical expertise or move into leadership. We're excited to see where you take it.

Everything else the record holds

The career path, and where it branches

Senior Automation Developer

Where AI is starting to help

Pipeline Generation Assistant

Business Case Co-Pilot

Risk & Compliance Scanner

Stakeholder Comms Generator

Common questions

You’ve started things before

Less than one coaching session. Every month.

You have the map. Walking it is the part we do together.