← Back
AWS ML Blog

From theory to delivery: How Atos upskilled 400 engineers in agentic AI

•12 min read•
#agents#deployment#llm
Level:Intermediate
For:AI Engineers
✦TL;DR

Atos upskilled 400 engineers in agentic AI by running a three‑day AWS AI League that required participants to build multi‑agent systems using native AWS services such as Amazon Bedrock, Bedrock AgentCore, AWS Lambda, Kiro, and Amazon SageMaker. The event combined hands‑on development, a live leaderboard scoring functional completeness and efficiency, and a competitive format to accelerate practical capability. Engineers progressed from limited exposure (5 % with no prior knowledge) to delivering end‑to‑end agentic solutions, demonstrating that structured, competition‑driven workshops can bridge theory‑to‑delivery gaps at scale. This model gives engineering leaders a repeatable blueprint for rapid, production‑ready AI skill development.

⚡ Key Takeaways

  • 400 engineers participated, with 5 % having no prior agentic AI knowledge and 20 % already experienced with agentic AI services.
  • Built multi‑agent systems incorporating pathfinding, guardrails, memory, and fine‑tuned models using Amazon Bedrock, Bedrock AgentCore, AWS Lambda, Kiro, and Amazon SageMaker.
  • Leaderboard scores measured both functional completeness and solution efficiency, creating a clear performance‑cost trade‑off.
  • Event delivered through AWS Workshop Studio, requiring only a few API calls to set up logistics and participant registration.
  • Prerequisite: participants needed at least basic AWS access; those without prior AWS experience received introductory support during kickoff and office‑hour sessions.
💡 Why It Matters

Engineers can acquire production‑grade agentic AI skills in days rather than months, directly applying AWS services to client projects and reducing time‑to‑value for multi‑agent deployments.

✅ Practical Steps

  1. Use AWS Workshop Studio to create an AI League event, following the standard setup calls to define logistics and collect participant info.
  2. Conduct the three‑day schedule: 2‑hour kickoff introducing the challenges and services, daily 1‑hour office‑hours calls for support, and a 1‑hour finale to announce the champion.
  3. Build and submit agentic solutions that integrate Amazon Bedrock, Bedrock AgentCore, AWS Lambda, Kiro, and Amazon SageMaker, then monitor leaderboard scores for functional and efficiency metrics.

Want the full story? Read the original article.

Read on AWS ML Blog ↗

More like this

Censored vs. Truncated Regression in Python, Explained

Towards Data Science•#llm

New in AWS Quick: More capable flows, an updated web experience, and agents that work together

AWS ML Blog•#agents

Three insights you may have missed from theCUBE’s coverage of the Dell Technologies New York Symposium

SiliconANGLE AI•#deployment

How Google Duplex evolved to also call businesses for you in Gemini

Google Research•#agents

EXPLORE AI NEWS

Daily hand-picked stories on LLMs, RAG, agents and production AI — curated for engineers who ship.

BROWSE NEWS

GET THE WEEKLY DIGEST

Join engineers getting the Monday signal-over-noise AI breakdown. No spam, unsubscribe anytime.

LEARN AI ENGINEERING

Curated courses, research papers, repos and tutorials built for engineers leveling up in AI.

START LEARNING