Training and Enablement

Overview#

Most teams adopting AI infrastructure underestimate the people-side cost. A platform that works for the first product team often fails the second team because the runbook never got written down. A migration that lands cleanly in dual-run gets undone in week three because the SRE team has not yet seen the platform under real production load. A Yobibyte workspace that ought to take an hour to set up takes three days because the customer's developers have never used an OpenAI-compatible endpoint that is not OpenAI. Training and Enablement is Yobitel's structured response to that people-side cost.

The service is organised around curriculum tracks (what is taught) and delivery formats (how it is taught). Curriculum tracks match the four customer roles that most often interact with the Yobitel stack: Architect, SRE, Data Scientist, and Developer. Delivery formats match how customers actually book training — instructor-led cohorts for a named team, on-demand modules for individuals, and blended programmes that combine the two for larger rollouts.

Every track is taught by Yobitel engineers who also build or operate the platform — not a separate training organisation. The Yobibyte track is taught by engineers who would otherwise be extending Yobibyte; the NeoCloud SRE track is taught by engineers who would otherwise be on the NOC rota. The teaching cost is real, the credibility is direct, and the runbook authored in the cohort is the same runbook used in production.

Yobitel Communications, the UK-headquartered AI infrastructure company that delivers Training and Enablement, sells the service per-learner or per-cohort in USD. Pilots, enterprise rollouts, and partner-NeoCloud certification cohorts are the three most common purchase shapes. UK NCSC OFFICIAL alignment is the default for the lab environments; on-premise and air-gapped labs are available for regulated customers.

Quick start — booking a cohort#

Booking a cohort is a guided console flow that takes most customers from initial conversation to cohort kickoff over two to six weeks. The learning lead on the customer side and the Yobitel cohort coordinator are the joint owners.

The customer's learning lead opens the Training console (under the main Yobitel console navigation) and chooses three things — the curriculum track (Architect, SRE, Data Scientist, or Developer), the delivery format (instructor-led, on-demand, or blended), and the cohort size and date. The console quote covers the cohort fee in USD, the included lab hours, and the certification fee per learner.

Once the cohort is confirmed, learners are invited via the customer's identity provider. Each learner gets a personal lab environment — a Yobitel-operated sandbox NeoCloud workspace with GPU capacity pre-allocated for the duration of the cohort — and access to the on-demand module library where applicable. The cohort follows the published schedule; live sessions run on Microsoft Teams, Google Meet, or Zoom per the customer's preference, with recordings published for 90 days afterwards.

Certification is awarded on completion of the competency assessment. The assessment is a mix of multiple-choice, hands-on lab tasks (deploy an Inference on Yobibyte, scale a NeoCloud reservation, debug an alert on a sandbox cluster), and a short written reflection. Pass rates are published per track for transparency; the average first-attempt pass rate sits in the high-70s across all four tracks.

Concepts#

Training and Enablement exposes a small set of concepts that match how a learning lead thinks about a structured upskilling programme. The mental model is the cohort at the centre, with curriculum track, delivery format, and certification around it.

• Cohort — the grouping of learners moving through a programme together. Standard cohorts run 6 - 24 learners; bespoke cohorts can be smaller (1:1 executive sessions) or larger (enterprise rollouts of 100+ learners).
• Curriculum Track — what the cohort learns. Architect (target-state design), SRE (operate the platform), Data Scientist (build on Yobibyte and AI Applications), Developer (consume the OpenAI-compatible API). Tracks have a defined module sequence and can be customised at the edges for specific customer stacks.
• Format — how the cohort consumes the curriculum. Instructor-led (live, scheduled sessions), on-demand (self-paced modules), or blended (instructor-led plus on-demand modules between sessions).
• Certification — the Yobitel-issued credential awarded on passing the track's competency assessment. Valid for 24 months; renewal cohorts available.
• Hands-on Lab — the sandbox environment learners use for hands-on tasks. A Yobitel-operated NeoCloud sandbox workspace with GPU capacity pre-allocated. Air-gapped on-premise labs available for regulated customers.
• Curriculum Customisation — the optional layer where Yobitel adapts a standard track to the customer's specific stack, sovereignty pin, or operational rhythm. Lightweight customisation is included with enterprise cohorts; deep customisation runs as a separate Professional Services engagement.
• Renewal Cohort — the shortened recertification programme run for learners whose 24-month certification is expiring. Typically half the length of the original track.

Curriculum tracks#

Four tracks cover the bulk of customer needs. Each track has a defined module sequence, a competency assessment, and a recommended audience.

Cohort size and cadence#

Cohort sizing balances effective small-group teaching against per-learner cost. The table below reflects mid-2026 production cohorts; bespoke shapes (1:1 executive sessions, very large enterprise rollouts) are accommodated separately.

Completion and pass-rate reporting#

Learning leads on the customer side get a dedicated dashboard covering cohort completion rates, certification pass rates, lab usage, and learner satisfaction (NPS). Yobitel publishes anonymised aggregate pass rates per track each quarter so customers can benchmark their cohorts against the wider Yobitel learner population.

The signals below feed Yobitel's curriculum-review cycle, so a track with a falling pass rate triggers a curriculum refresh rather than a quiet drift.

• Completion rate — percentage of learners who complete all required modules and the competency assessment. Yobitel's published target is above 85%.
• Certification pass rate — first-attempt pass rate on the competency assessment. Published per track quarterly; current average sits in the high-70s.
• Lab usage — hours per learner per week. Helps spot disengaged learners early; learning leads can intervene before the cohort closes.
• Learner NPS — published per cohort and aggregated quarterly. Drives curriculum refresh priorities.
• Cohort runbook adoption — for SRE cohorts, the proportion of cohort-authored runbooks adopted into the customer's production runbook library.

Pricing#

Training and Enablement is priced per-learner or per-cohort in USD. Per-learner pricing applies to on-demand and public instructor-led cohorts; per-cohort pricing applies to private and enterprise cohorts. Certification fees are separate from cohort fees; lab usage is included up to the per-cohort limit. Enterprise customers can prepay for a learner pool at a discount.

Security and compliance#

Lab environments run inside Yobitel-operated NeoCloud sandbox regions and inherit the same control set as NeoCloud production. UK NCSC OFFICIAL alignment is the default; air-gapped on-premise labs are available for regulated customers. Learner data (identity, progress, certification) is held under GDPR with EU SCCs available for non-EU customers.

• NCSC Cloud Security Principles — default posture for the sandbox lab environment.
• G-Cloud — listed under Cloud Support (Lot 3).
• Cyber Essentials Plus — current certificate.
• ISO 27001:2022 — current certificate covering the training organisation and learner data.
• SOC 2 Type II — annual third-party audit.
• GDPR / UK DPA 2018 — DPA, sub-processor list, EU SCCs available.
• Air-gapped on-premise lab — available for regulated customers; lead time required.
• Learner data — held for the duration of certification validity (24 months) plus required regulatory retention; deletion on request.
• Identity — OIDC federation for cohort enrolment supported (Okta, Microsoft Entra ID, Auth0, Keycloak).
• Background-checked trainers — all Yobitel trainers cleared to BS 7858 (UK) and equivalent jurisdictions.

Alternatives#

Training and Enablement is one option for upskilling teams on AI infrastructure. The honest read: LinkedIn Learning and Coursera are great for broad foundations but have no Yobibyte or NeoCloud coverage and no hands-on labs on the real platform; hyperscaler training (AWS, Azure, GCP) covers their own services well but stops at the cloud boundary and does not address sovereignty or cross-vendor depth; an in-house enablement function gives full control at the cost of building and maintaining curriculum, labs, and assessments — typically a 4-8 quarter investment before it pays back. Yobitel Training sits in the middle as the structured upskilling path for teams adopting the Yobitel stack, taught by engineers who operate it.

Common cohort issues and how they are handled#

Training and Enablement is a service contract rather than a product, so 'troubleshooting' is reframed as the common cohort issues that come up and how they are handled.

Where Training and Enablement fits in the Yobitel stack#

Training and Enablement is the people layer of the Yobitel stack. NeoCloud Operations builds the facility and platform; Training prepares the people who will run it. Professional Services designs and implements; Training transfers the knowledge so customers are not perpetually dependent on Yobitel. Managed Operations runs the day-two estate, often alongside ongoing Training subscriptions so customer engineers remain current as the platform evolves.

The boundary with Professional Services is deliberate. Professional Services delivers paired-engineering knowledge transfer to the specific team adopting the work it builds; Training delivers structured cohort upskilling to broader customer populations. A typical enterprise adoption looks like an Architecture engagement, a Build engagement, an SRE cohort, a Developer cohort, and a transition to Managed Operations — all under a single Customer Excellency-owned relationship.

Most customers run cohorts twice in the first year of adoption (initial onboarding plus a follow-up six months later) and an annual renewal cohort thereafter. The annual renewal is also when the customer's team absorbs new platform features and re-aligns on operating practice; the recurring rhythm keeps the customer's certified engineer pool current as the platform evolves.