United Kingdom · Customer Service · Mid-Level (2-5 years)

Technical Support Assistant

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 toTechnical Support Manager
UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Customer Support Engineer · Product Support Specialist · Helpdesk Analyst (Tier 2)

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 Technical Support Assistant

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 the person our customers turn to when their software isn't quite doing what it should. This isn't just about answering questions; it's about getting to the bottom of tricky technical issues, making sure our users can actually get their work done. Think of yourself as a detective, but instead of solving crimes, you're solving software glitches. You'll be working independently on most days, handling a steady stream of tickets, and sometimes helping out the newer folk.

2What you'd actually use

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

You'll independently log, update, route, and close tickets. You'll use macros, create custom views to manage your queue, and understand how to pull basic reports on your own performance.

TeamViewer / AnyDesk (or similar remote access)Intermediate

You'll confidently initiate secure remote sessions with customer permission, navigate their environments, and diagnose/fix issues directly on their systems without needing constant guidance.

Confluence / Guru (or similar knowledge base)Intermediate

You'll not only search for and apply existing articles but also draft, edit, and contribute new knowledge base content, helping to keep our collective wisdom up-to-date and useful.

Slack / Microsoft Teams (for internal comms)Intermediate

You'll use these for quick team queries, escalating issues to specific subject matter experts, and participating in discussions. You might even set up simple workflows for common requests.

Datadog / Splunk (for log analysis)Intermediate

You'll independently query logs, filtering by time, source, and keywords to identify error messages, patterns, or anomalies that point to the root cause of a customer's issue. You might even create a basic dashboard.

Talkdesk / Aircall (for telephony/CCaaS)Intermediate

You'll handle incoming and outgoing calls, manage call queues, perform warm transfers, and use the system's features to manage your call flow efficiently. You'll also pull basic call metric reports.

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
Troubleshooting Path for a Known Issue	Follows a prescribed script or KB article, seeks supervisor approval if deviation is needed.	Independently chooses the most efficient troubleshooting path, adapting standard approaches as needed. Consults manager for novel situations.	Defines and refines troubleshooting paths for new and complex issues, often creating the scripts for others.
Customer Workaround Approval	Escalates all workaround requests to supervisor for approval.	Approves standard, low-risk workarounds within defined parameters. Escalates high-risk or non-standard workarounds.	Designs and approves complex workarounds, assessing technical risk and business impact, consulting with Product/Engineering as needed.
Escalation to Engineering	Escalates upon supervisor's instruction or after exhausting all Tier 1 steps as documented.	Independently decides when an issue requires Engineering involvement, ensuring all 'repro steps' and logs are provided. Consults manager on critical P1 escalations.	Acts as the primary liaison with Engineering, pre-qualifying issues, streamlining communication, and pushing for timely resolutions.
Knowledge Base Contribution	Flags outdated articles or suggests new topics to supervisor.	Drafts and submits new KB articles or updates existing ones for review by a Senior or Manager. Can make minor edits independently.	Authors, edits, and approves new KB articles, ensuring adherence to KCS principles and accuracy. Mentors others on KB best practices.

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.

First Contact Resolution (FCR)

The percentage of technical issues you solve on the very first interaction, without needing further follow-up or escalation.

Target · >75%

You resolve 80 out of 100 tickets on the first call or email. That's a good FCR, meaning you're efficient and knowledgeable.

Customer Satisfaction (CSAT) Score

The average rating customers give your support after their issue is resolved. We usually send a quick survey after you close a ticket.

Target · >90%

If 92 out of 100 customers rate your support as 'satisfied' or 'very satisfied', you're hitting the mark. It shows you're not just fixing the problem, but doing it well.

Average Handle Time (AHT)

The average amount of time you spend actively working on a ticket, from opening to closing. This includes talk time, research, and documentation.

Target · Within team baseline (typically 15-20 minutes for Tier 2)

If the team's average is 18 minutes, and your AHT is 17 minutes, you're efficient. Too low might mean you're rushing, too high might mean you're getting stuck.

Ticket Hygiene Compliance

How well you're documenting your tickets – making sure all fields are filled, internal notes are clear, and categorisation is correct.

Target · 100% compliance

Your manager reviews 10 of your closed tickets and finds all of them have clear 'repro steps', a detailed resolution, and correct tags. Spot on!

Troubleshooting Depth

Your ability to go beyond the obvious fix and truly diagnose the root cause of a problem, even when it's complex or obscure.

You'll be able to explain your diagnostic process clearly in ticket notes. Your manager will see you're not just applying quick fixes but genuinely understanding the underlying issue. Other team members might come to you for help on tricky problems.

Customer Communication Clarity

How well you explain complex technical concepts to non-technical users in a way they can understand, without being condescending.

Customers rarely ask for clarification after your explanations. You get positive comments in CSAT surveys about your communication. Your written responses are concise, easy to follow, and avoid jargon where possible.

Proactive Knowledge Contribution

Your willingness to identify gaps in our knowledge base and contribute new articles or update outdated ones.

You'll regularly flag outdated articles or suggest new ones. You might even draft a few new articles each month for common issues you've resolved. You're not just consuming knowledge, you're creating it.

Team Collaboration & Support

How effectively you work with your team, offering help when needed and asking for it when you're stuck, contributing to a positive team environment.

You're active in team Slack channels, offering advice or resources. You participate constructively in team meetings. Junior team members might ask you for informal guidance, and you're happy to provide it.

5Would you like it

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

What people enjoy

Solving Complex Puzzles

You get a real buzz from figuring out a tricky bug or an obscure configuration issue that others might have given up on. That feeling when you finally crack it? That's what keeps you going.

Spending an hour debugging a customer's unique integration issue, finally pinpointing a misconfigured API key, and seeing their system spring back to life.

Helping People Directly

You genuinely enjoy making someone's day better by resolving their problem. The 'thank you' from a relieved customer is a big part of your job satisfaction.

A customer calls in a panic about a critical report not generating, and you guide them through the steps to fix it, hearing the relief in their voice.

Continuous Learning

Our product evolves, and so do the problems. You're always keen to learn about new features, new troubleshooting techniques, and new tools to get better at your job.

Taking the initiative to learn about a new product release before issues start coming in, or researching a new log analysis tool in your spare time.

What frustrates people

Vague tickets with no useful context or error messages.
Customers who haven't done basic troubleshooting (e.g., rebooting).
Sales-driven urgency overriding actual technical priority.
Outdated knowledge base articles that waste your time.
Getting a well-documented ticket bounced back from Engineering with 'cannot reproduce'.
Being the bearer of bad news about unfixable bugs or missing features.

What this role does not give you

A quiet, uninterrupted work environment – it's customer service, so expect calls and constant communication.
A predictable 9-to-5 schedule every single day – urgent issues can pop up.
Complete autonomy over product direction – you're solving problems, not designing features.
A role where you never have to repeat yourself or explain the same thing twice.

6Who you work with

This role directly impacts customer satisfaction and retention. Happy customers stay with us, recommend us, and ultimately drive revenue. You're the frontline, often the only human interaction a customer has when things go wrong, so your ability to resolve issues efficiently and empathetically is crucial for our reputation and bottom line. Get it right, and you're building loyalty. Get it wrong, and you're risking churn and negative word-of-mouth.

Inside the business

Product Management (for bug reports and feature requests)
Engineering Team (for deep technical issues and fixes)
Sales & Account Management (for client-specific issues and escalations)
Customer Success Managers (for customer health and retention)

Outside the business

Our customers (end-users, system administrators)
Third-party software vendors (when integrating with other tools)

7What you need before you start

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

At least 2 years of hands-on experience in a technical support role, ideally for a SaaS product or similar software.
Proven ability to independently troubleshoot complex technical issues, moving beyond basic scripts.
Demonstrable experience with at least one major ticketing system (e.g., Zendesk, Salesforce Service Cloud) and remote access tool (e.g., TeamViewer).
A solid understanding of basic networking concepts and how they impact software applications.
Experience in explaining technical concepts clearly and patiently to non-technical users.
A track record of maintaining high customer satisfaction scores (CSAT).

8What to practise next

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

Advanced API Troubleshooting

More and more of our customers are integrating our product with other systems via APIs. When these integrations break, you'll need to understand how to diagnose issues beyond just checking our UI.

HTTP Status Codes · JSON/XML Structure · Authentication Methods · Using API Clients (e.g., Postman)

This quarter: Take an online course on 'API Fundamentals for Support Professionals'.
Next 6 months: Shadow a Senior Support Technician on API-related tickets, asking lots of questions.
Within 9 months: Take ownership of at least one complex API integration issue per week.
Within 12 months: Be able to use Postman to diagnose and replicate API issues independently.

Quick win: Familiarise yourself with our public API documentation and try to understand the basic request/response cycles for our most common integrations.

Cloud Environment Diagnostics (AWS/Azure/GCP)

Our infrastructure is increasingly cloud-based, and some customer issues can stem from their own cloud environments or how they interact with ours. A basic understanding will help you diagnose these faster.

Cloud Resource Monitoring · Network Security Groups/Firewalls · Log Aggregation in Cloud · Basic Cloud Services

This quarter: Complete a 'Cloud Fundamentals' course (e.g., AWS Cloud Practitioner, Azure Fundamentals).
Next 6 months: Ask to shadow our DevOps or Engineering team during incident reviews involving cloud infrastructure.
Within 9 months: Be able to identify potential cloud-related issues from customer descriptions and logs.
Within 12 months: Independently troubleshoot basic connectivity or performance issues related to cloud infrastructure.

Quick win: Watch some introductory videos on AWS or Azure to get a feel for their consoles and common services.

9Staying current once you are in

What people here do to keep up

Regularly engage with our internal product documentation and release notes to stay ahead of new features and changes.
Participate in online forums or communities related to our product or relevant technologies to learn from others' experiences.
Take advantage of any internal training programmes on new tools or troubleshooting techniques.
Seek out opportunities to shadow senior technical support staff or engineers to learn advanced diagnostic methods.
Attend industry webinars or virtual conferences on customer service or technical support best practices.

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: AI-Assisted Troubleshooting & Prompt Engineering

AI tools are getting incredibly good at sifting through data, suggesting fixes, and even drafting responses. Technicians who can effectively 'talk' to these AIs (prompt engineering) will be significantly more efficient and effective.

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.

AI-Assisted Troubleshooting & Prompt Engineering

AI tools are getting incredibly good at sifting through data, suggesting fixes, and even drafting responses. Technicians who can effectively 'talk' to these AIs (prompt engineering) will be significantly more efficient and effective.

Effective Prompting
AI Output Validation
Integrating AI into Workflow
Ethical AI Use

What you’ll use

Skills this role draws on

Technical

ITIL Framework (Incident & Problem Management)
Troubleshooting Methodologies (e.g., 5 Whys, RCA)
Knowledge-Centered Service (KCS) Principles
Ticket Triage & Prioritisation
SLA/SLO Management

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
Associate Support Technician (L1) Promotion
1.5 - 2.5 years
Skills to master
- Consistently achieving high FCR and CSAT, independently resolving routine Tier 1 issues, demonstrating proactive learning of the product and systems, and contributing to basic knowledge base updates.
You're ready to move on when
- Can handle 90% of Tier 1 tickets without supervision.
- Consistently receives positive customer feedback.
- Proactively identifies and flags system issues or knowledge gaps.
- Shows initiative in learning complex product areas.
2
External Hire (from similar SaaS support role)
Immediate (upon hiring)
Skills to master
- Quickly learning our specific product and internal processes, adapting to our tools and methodologies, and building rapport with the team and customers.
You're ready to move on when
- Demonstrated 2-5 years experience in a comparable technical support role.
- Strong understanding of SaaS environments and troubleshooting.
- Excellent communication and problem-solving skills validated through interview and technical assessment.
- Ability to quickly integrate into a new team and system.
3
Internal Transfer (from non-technical customer service)
2 - 3 years (with dedicated technical upskilling)
Skills to master
- Developing a solid technical foundation (networking, cloud basics, API concepts), mastering troubleshooting methodologies, and gaining hands-on experience with our core tech stack. This usually involves a dedicated learning programme.
You're ready to move on when
- Completed internal technical training programmes or external certifications.
- Successfully shadowed technical support teams and handled basic technical queries.
- Demonstrated strong aptitude for logical problem-solving.
- Proactive in self-directed technical learning.

11Where this role leads

The long view:Your journey here isn't a fixed path; it's a launchpad. We're committed to helping you grow, whether that's becoming a top-tier technical expert, moving into leadership, or even exploring different functions within the company. Your development is our priority, and we'll provide the resources and opportunities to help you build a truly rewarding career.

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 Technical Support Assistant 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:

Providing technical sales and marketing support for engineering activitiesLevel 3

Applied to your work in Technical Support Assistant

This unit aims to develop the skills and behaviours required to provide technical sales and marketing support for engineering activities. Learners will be able to use company information, produce compliant sales and marketing materials, and adhere to health and safety regulations. This will enable them to effectively contribute to the sales and marketing efforts of an engineering organisation.

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 Technical Support Assistant

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.

First Contact Resolution (FCR)The percentage of technical issues you solve on the very first interaction, without needing further follow-up or escalation.You resolve 80 out of 100 tickets on the first call or email. That's a good FCR, meaning you're efficient and knowledgeable.>75%
Customer Satisfaction (CSAT) ScoreThe average rating customers give your support after their issue is resolved. We usually send a quick survey after you close a ticket.If 92 out of 100 customers rate your support as 'satisfied' or 'very satisfied', you're hitting the mark. It shows you're not just fixing the problem, but doing it well.>90%
Average Handle Time (AHT)The average amount of time you spend actively working on a ticket, from opening to closing. This includes talk time, research, and documentation.If the team's average is 18 minutes, and your AHT is 17 minutes, you're efficient. Too low might mean you're rushing, too high might mean you're getting stuck.Within team baseline (typically 15-20 minutes for Tier 2)
Ticket Hygiene ComplianceHow well you're documenting your tickets – making sure all fields are filled, internal notes are clear, and categorisation is correct.Your manager reviews 10 of your closed tickets and finds all of them have clear 'repro steps', a detailed resolution, and correct tags. Spot on!100% compliance

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 Technical Support Assistant to Senior Technical Support Assistant (L3), and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Senior Technical Support Assistant (L3)→ your design

Where this takes you

Your journey here isn't a fixed path; it's a launchpad. We're committed to helping you grow, whether that's becoming a top-tier technical expert, moving into leadership, or even exploring different functions within the company. Your development is our priority, and we'll provide the resources and opportunities to help you build a truly rewarding career.

See Your Progress GrowIllustration

Technical Support Assistant

ITIL Framework (Incident & Problem Management)
Troubleshooting Methodologies (e.g., 5 Whys, RCA)
Knowledge-Centered Service (KCS) Principles
Ticket Triage & Prioritisation
SLA/SLO 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.

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

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

Senior Technical Support Assistant (L3)
2 - 3 years
You'll move from independently solving problems to becoming an escalation point for others, tackling the really complex, non-routine issues, and actively improving our support processes. You'll also start mentoring junior team members.
- Advanced Log Analysis & Monitoring (e.g., building custom dashboards)
- Deep Product Specialisation (becoming the go-to expert for a specific feature)
- Complex API Integration Troubleshooting
- Contributing to RCA documents and proactive problem management

Working with AI on the job

Working with AI

Where AI is starting to help

Imagine spending less time on the tedious, repetitive stuff and more time on genuinely interesting technical challenges. That's the reality with our new AI tools. We're not looking to replace you; we're giving you superpowers to make your job easier and more impactful.

For a Technical Support Assistant, AI isn't some far-off future tech. It's here, right now, helping you get through tickets faster, find answers quicker, and even draft better responses. It means you can focus your brainpower on the really tough problems that only a human can solve, rather than getting bogged down in routine tasks.

Automated Ticket Triage

An AI model reads new incoming tickets, automatically figures out what the issue is (e.g., 'Billing query,' 'Bug report,' 'Password reset'), sets a preliminary priority based on keywords and the customer's history, and then routes it straight to the right person or team. No more manually sifting through the queue just to assign tickets.

Instant Knowledge Surfacing

As you're typing in a ticket or on a call, an AI assistant works in the background, scanning the conversation. It'll proactively suggest relevant knowledge base articles, similar past tickets that were resolved, and even specific troubleshooting commands from our internal docs. It's like having a super-smart assistant whispering answers in your ear.

Intelligent Response Generation

Got a common query? AI can draft a solid first response for you. It can take a long, technical log and summarise it into a simple, customer-friendly explanation, or whip up a polite 'we're looking into it' message that includes the customer's specific details. You just review, tweak, and send. Saves you loads of typing time.

Sentiment Analysis & Escalation Warning

Our AI keeps an eye on the tone of customer interactions in real-time. If it detects frustration, anger, or even sarcasm in their messages, it can automatically flag the ticket for a manager's review. This means we can often jump in and de-escalate a situation before the customer even thinks about formally complaining or asking for an escalation.

Common questions

How do you become a Technical Support Assistant?

Common routes in include Associate Support Technician (L1) Promotion (1.5 - 2.5 years), External Hire (from similar SaaS support role) (Immediate (upon hiring)) and Internal Transfer (from non-technical customer service) (2 - 3 years (with dedicated technical upskilling)). Times vary with prior experience.

Where can a Technical Support Assistant progress to?

This role can lead on to Senior Technical Support Assistant (L3) (2 - 3 years), depending on the skills you build.

What level is a Technical Support Assistant in the UK?

This role aligns to RQF Level 2 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 a Technical Support Assistant?

Increasingly, AI-Assisted Troubleshooting & Prompt Engineering. 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 a Technical Support Assistant, 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 10 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 a Technical Support Assistant: 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 of nine units, ninety credits, each one an Ofqual-regulated unit the learner can tick or untick before starting. — 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 2

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

Other roles in Customer Service

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

If you leave this industry

The skills you'll pick up here – deep technical troubleshooting, customer communication, problem-solving, and working with various tech stacks – are highly transferable. You could easily move into other SaaS companies, IT services, or even into roles like technical writing or training in almost any tech-driven industry. Good technical support is always in demand.

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.

Technical Support Assistant

What's rising in its place

AI-Assisted Troubleshooting & Prompt Engineering

Skills this role draws on

Technical

How you actually get there, here

Associate Support Technician (L1) Promotion

External Hire (from similar SaaS support role)

Internal Transfer (from non-technical customer service)

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.

Everything else the record holds

The career path, and where it branches

Senior Technical Support Assistant (L3)

Where AI is starting to help

Automated Ticket Triage

Instant Knowledge Surfacing

Intelligent Response Generation

Sentiment Analysis & Escalation Warning

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.