AI Adoption Specialist
Rollenübersicht von JobGrid
AI Adoption Specialist at Tomoro: Edinburgh, Vereinigtes Königreich; Hybrid; Vollzeit; IT; Solutions / Architektur. JobGrid adds normalized role facts, source context, and a path to the employer application page so candidates can compare the listing before applying.
- Location and workplace: Edinburgh, Vereinigtes Königreich, Hybrid
- Role classification: IT, Solutions / Architektur, Vollzeit
- Source freshness: checked by JobGrid on 2026-05-28.
- Application path: candidates continue to the employer application page with non-personal referral tags.
About Human Productivity
The Role
As an AI Adoption Specialist, your job is to help enterprise teams work better with AI by changing how work gets done.
You’ll sit at the intersection of workflow design, AI literacy, and the effective use of state-of-the-art general purpose AI tools. Some weeks you're embedded with a client team, observing how work really happens and redesigning it so AI carries the load. Other weeks you're creating the assets and approaches that make the new way of working stick: prompts, skills, quality checks, lightweight automations/ integrations, and simple tools built collaboratively alongside client teams.
You'll work alongside Tomoro's AI Engineers. They build production-grade AI systems. You make sure the humans around those systems (and the humans who don't yet have those systems) are getting the most out of AI, every day.
Think of the goal as five days of outcomes in three days of effort.
What You'll Be Doing
Workflow Discovery and Redesign
- Embed with client teams to understand how work actually happens, not how it's supposed to happen. Follow the time, find the friction, and surface the real bottlenecks rather than the ones on the process diagram.
- Redesign workflows around AI: accelerating what's already there, removing the drudgery, and unlocking things that weren't previously possible. Measure impact at the workflow level — cycle time, rework, quality consistency, throughput — and track adoption signals as evidence the change is sticking.
- Build momentum through short, focused engagements: co-labs, sprints, 1-to-1 and small group coaching that make progress visible fast.
Creating What Teams Need to Adopt AI
- Co-create and ship assets teams actually reuse: prompts, custom instructions, skills, QA checks, evaluation prompts, and playbooks. If it isn't reusable, it isn't finished.
- Use AI-assisted development tools (Claude Code, Codex, MCP) as your default for building small automations and integrations that remove friction, inside the platforms teams already use: ChatGPT, Adobe, Slack, Microsoft Teams. Connect tools and data sources so teams stop copy-pasting and start flowing.
- Build to reflect how the client actually operates: their tone, constraints, risk posture, and governance expectations. Know the ceiling too. When off-the-shelf tools run out of road on reliability, integration, or scale, help shape the next step with Tomoro's AI Engineering team.
Coaching and Sustaining Capability
- Move people from "I should use AI" to "AI is my default first step" by working and building alongside them, not by putting them in a room with slides.
- Build trust quickly with people who are sceptical, overwhelmed, or both. The antidote isn't a workshop. It's doing real work together and letting the outcomes speak. Coach prompting and verification without being dogmatic, and build the champions and routines that keep improving after you leave.
- Help define the conditions for lasting adoption: new habits, processes, incentives, and ways of working. Where you find people who want to go further, help them grow into AI builders themselves.