From Scholar to Agent Engineer: My AWS AI & ML Scholars Journey
On October 8, 2026, I finished the Future AWS Agent Engineer Nanodegree. That same day, my third agent system passed all 120 points of its official test suite.
Most of my work has been computer vision on edge devices: cameras on plant floors, OpenVINO pipelines, Jetson boards in the field. Language models came into that work from the side, first as a way to summarise alerts and later as a way to reason over sensor data. In 2026 I wanted to learn properly how to build AI agents: systems that decide, call tools, keep state and recover from errors. The AWS AI & ML Scholars program gave me a structured way to do that.
How the program works
AWS AI & ML Scholars is run by AWS and Udacity in two phases. The Challenge phase is free and self-paced: it follows the AWS AI Practitioner learning plan and includes hands-on work with Amazon PartyRock and Amazon Bedrock. Up to 100,000 learners can take part. An assessment follows, and the top 4,500 learners receive a fully funded Udacity Nanodegree in one of three tracks. I chose the most technical one: Future AWS Agent Engineer.
Three projects, each harder than the last
- August: Customer Support Chatbot. One agent on an AgentCore Harness with three fixed routes and one database tool. The lesson: let the model suggest, and let code decide.
- September: AI Support Agent. One agent with six capabilities: Gateway tools, a Knowledge Base, Memory, Code Interpreter and Browser. The lesson: test the final reply, not just the tool output.
- October: NovaMart Multi-Agent RAG. A supervisor with four specialist agents, three knowledge bases searched at once, and shared state with version checks. The lesson: give each agent one job and keep their shared state consistent.
The main thing I learned: an agent isn't production-ready because it handles a good demo. It's ready when you can show what it did, why it did it, and that it does nothing when it shouldn't act.
Habits I'm keeping
- Separate the model's suggestion from the decision. The model can choose a route. Plain code checks that the required fields are present before anything is written to the database.
- Keep evidence. Each project shipped with recorded transcripts, screenshots, evaluation datasets and trace maps, so anyone can check the results.
- Tear everything down. Every project ended with a check that no AWS resources were left running. It's easy to skip and expensive when you do.
- Plan for production from the start. Even coursework should include notes on authentication, idempotent refunds and how long customer memory is kept.
The next three articles cover one project each, including the architecture, the mistakes and the evidence. If you're applying to the next round of the scholarship, I hope they help.