Agentic AI for Enterprise Teams
Six weeks for engineering teams, delivered against your own systems and constraints. Same agentic engineering as the open cohort, taught…
Cohorts forming for the 2026 intake — dates and fees confirmed before you commit.
Register interest →Four tracks — foundations, core AI engineering, responsible engineering, and sovereign AI. Every program ends in a working artifact you own.
Register NowFIRE runs four tracks. Foundations covers Python, machine learning and the engineering practice AI work assumes. Core builds LLM and agent systems. Responsible Engineering covers evaluation, governance and security. Sovereign AI covers local models, data residency and the trade-offs against frontier APIs.
Most people take one track. Engineers switching into AI usually start in Foundations and finish with the agentic capstone. Enterprise teams typically start in Core or Responsible Engineering, delivered against their own systems.
Three things, regardless of level. You build something that runs. You write the evaluation that proves it works. You leave with the artifact on your own GitHub, not a completion certificate.
That is deliberate. A certificate says you attended. A working agent with a test harness and a failure analysis says you can do the job — and it is what a technical interviewer will actually ask you to walk through.
We do not guarantee placement, and we would be sceptical of anyone who does. We are not a university and we do not award degrees or diplomas. What we award is a certificate of completion issued by FIRE, and the artifacts you built to earn it.
Six weeks for engineering teams, delivered against your own systems and constraints. Same agentic engineering as the open cohort, taught…
Eight weeks building one substantial system against a real brief, with weekly review and a final defence to a technical…
A half-day briefing for boards and leadership teams: where AI exposure sits, what you are accountable for, what evidence to…
Three weeks attacking AI systems — your own first. Prompt injection direct and indirect, tool abuse, scope escalation, data exfiltration,…
Six weeks on operating AI systems after launch: tracing, cost control, model routing, incident response, and the deployment patterns that…
Two-week electives applying the core curriculum to one domain — financial services, healthcare, public sector or energy. Same engineering, different…
A two-day or five-day intensive delivered on campus. Students leave having built and deployed a working AI system, not having…
Six weeks on what machine learning actually does, so you can reason about model behaviour rather than treat it as…
Two weeks certifying your faculty or internal enablement team to deliver FIRE curriculum independently, with materials, assessment rubrics and ongoing…
Eight weeks building retrieval-backed LLM systems that hold up on real documents and real questions. You will build a working…
Six weeks of Python written the way AI systems need it: typed, tested, async where it matters, and structured so…
Four weeks bringing an organisation's AI use under control: an inventory of what is actually running, evaluation standards, approval processes,…
Four weeks turning an existing AI system into one you can defend: evaluation harnesses, approval gates, audit trails and the…
Four weeks on the engineering practice AI work assumes but rarely teaches: version control that survives collaboration, APIs that fail…
Three weeks for regulated organisations deciding what can leave their boundary and what cannot — with the architecture, cost model…
A two-day intensive for leadership teams facing a sovereignty decision: what residency actually requires, what self-hosting costs, and how to…
Four weeks on running capable AI inside a boundary you control: selecting and serving open-weight models, quantisation, routing between local…
These run once a cohort fills. Register interest and we’ll confirm dates and fees first.
12 weeks · Intermediate