AI Literacy Trainer

What they do

They start by finding out who the learners are and what tasks they do. Then they build training around those tasks, not around generic AI theory. That means workshops, notebooks, sample applications and short written guides. They show where a tool helps and where it gives confident wrong answers. They design practical exercises and checks that show whether people can do the work safely. They run sessions, watch where people struggle, and rewrite the material. They also work with legal, security and team leads so the guidance matches company policy.

What a strong hire delivers

In the first months, a strong hire delivers a training programme built for one clear audience, with practical competency checks attached. They produce a baseline of what people can do before training and evidence of what changes after it. They leave behind maintained documentation, reusable exercises and a simple way to update content as tools and company rules change. Teams know when to trust outputs and when to check.

How you can tell they are good

Ask them to show a training programme they built and explain who it was for. Look for tasks, not slides. Ask how they tested whether people could actually do the work afterwards. Ask them to walk through a failure case they teach, such as a fabricated source, and how they get learners to catch it. Good candidates adapt to context and can describe what they changed after sessions went badly.

Why it is hard to fill

Few people sit exactly here. Titles vary: enablement, learning, developer education, technical writing. Many teachers lack hands-on technical depth, and many engineers have never designed instruction or measured learning. Candidates who can do both are rare, and they often don't search under this title. Hiring managers also struggle to judge quality, because a polished workshop can hide weak assessment. We screen for evidence of competency checks and real technical fluency.

Where to find them

Look in technical writing teams, developer education and developer relations, and internal enablement or learning functions at software companies. Some come from teaching, corporate training or instructional design and have since built technical skills. Others are engineers or analysts who ran internal workshops and enjoyed it more than the coding. Consultancies and software firms with large customer onboarding programmes are also good sources.

Skills that matter

• Technical communicationAdvancedExplain evidence and limitations to relevant readers
• Change management and trainingAdvancedSupport adoption through learning and organisational change
• User researchWorkingStudy user needs, context and behaviour
• PythonWorkingDevelop tested numerical and data software