AARI Impact and Cohort Results

Proof from the rooms where students build.

AARI's work is visible in student sessions, partner visits, lab tables, data center discussions, Smart Illuminating Helmet reviews, and applied AI infrastructure presentations.

Summer 2026 Cohort

Eight scholars. Real systems. Work you can review.

Eight scholars completed the Summer 2026 cohort. The available six-participant weekly ledger includes the September 4 closeout submission that arrived after the August 28 cumulative report. It documents 483 participant-hours, at least 150 participant-days, and 35 weekly entries across seven reporting periods. Because only one of six expected final-week reports was present, these figures are documented minimums, not a complete cohort total.

483

Documented participant-hours

150+

Recorded participant-days

35

Weekly progress entries

83%

Weekly-ledger coverage, 35 of 42 expected entries

60%

Entries with a labeled evidence section

5 of 7

Accessible resumes that included AARI experience

What changed over the cohort

Weeks 1-2

Access and foundations

Linux terminals, Git and SSH, ROS 2 orientation, cloud workflows, interview practice, equipment inventory, and initial system access.

Weeks 3-4

System bring-up

Raspberry Pi imaging, firmware, networking, firewall work, robot components, virtual machines, and simulated telemetry.

Weeks 5-6

Integration and delivery

Infrastructure monitoring, GPU visualization, a security dashboard and threat map, robot integration, curriculum, and technical videos.

Closeout

Handoff and career translation

A resume review, data-engineering and cloud-architecture sessions, and a submitted perception-curriculum handoff. Weekly reporting was incomplete.

Learning insight

Students learned to move between layers.

The strongest evidence is not tool exposure. Students changed layers when a system failed: an unavailable static IP became a virtual-machine and simulated-data workflow; headless-device failures moved to direct-display diagnosis; an incompatible operating system was replaced; and an installation problem was resolved with SSH keys.

That is the infrastructure-up model in practice: hardware, operating systems, networking, cloud services, applications, and documentation became one connected problem rather than separate classes.

Delivery insight

Software outputs closed faster than physical integration.

By late August, the data-center and cybersecurity work included a completed monitoring application, GPU visibility, a security dashboard, a live threat-map feature, and instructional videos. Robotics reports still listed the robot, LiDAR integration, and ROS 2 certification as next deliverables.

The difference points to dependency risk, not a lack of effort. Hardware availability, firmware, operating-system compatibility, networking, and shared build time created a longer integration path than software-only work.

Workforce insight

Building skill and proving skill were separate jobs.

Seven resume files were accessible at closeout, but five included AARI experience. The August 31 review repeatedly called for clearer ownership, metrics, working GitHub links, READMEs, project sites, and reproducible demonstrations.

Students had work to describe. The unfinished step was converting that work into evidence that a recruiter or technical reviewer could evaluate without explanation.

Program insight

Closeout must begin before the final week.

The retained closeout tracker was created September 2 for a September 4 deadline, and access requests were still arriving September 3. The weekly ledger, closeout roster, and outcome scoreboard also contained different participant counts.

The next cohort will use one roster, validate access before work begins, require a direct artifact every week, and start README, demo, resume, and handoff reviews before the final sprint.

Sources: the de-duplicated cumulative weekly ledger through August 28, the September 4 individual closeout report, the closeout tracker, accessible resume files, and cohort-session records from August 31 and September 4. Student work and hours are participant-reported unless a public artifact is linked; certification, hiring, and placement claims remain unpublished without confirmation. Results are published only as de-identified whole-cohort aggregates. Read the impact methodology.

Student Workshops

Corporate Exposure

Robotics and Edge AI Labs

Smart Illuminating Helmet

AARI Leadership

Proof, Not Theater

Students do not just hear about AI, robotics, cloud, edge computing, and infrastructure. They see it, touch it, question it, and build with it.

Partner With AARI

What students built

Summer 2026 Scholar Case Study

Rasheed Jeheeb: participation becomes technical evidence.

8.5→15.5weekly hours
82%increase
FIRSTmentor pathway
“Because of AARI, I can see myself becoming a successful and passionate expert in robotics and a practicing engineer.”

His reflection connects robotics, data-center infrastructure, mentorship and technical evidence to an engineering career direction.

Read Rasheed Jeheeb’s transcript

Hi, I'm Rasheed. I'm the newest member of the Robotics Cohort in the Atlanta AI and Robotics Initiative in summer 2026. This summer, I've had the opportunity to have hands-on experience in hardware manufacturing, robotics, and just old-fashioned programming as well. Across the board, it's been great to have access to resources like mentorship from cutting-edge entrepreneurs in the tech space and experienced professionals in the corporate technology world as well from companies like Waymo and Amazon. Also, and a personal favorite part of the program for me has been the ability to work with budding scientists from starting from ages 14 and up on robotics projects that interest us both and allow us both to grow and learn together. I think if you're interested in technology in general, if you're interested in pursuing mentorship or certification in technology, then the Atlanta AI and Robotics Initiative is something that can really jumpstart your career and put you in the right mindset to make a difference here in Atlanta, but also in any room you walk into.

Automatically transcribed from the student testimonial.

Video summary: Rasheed reflects on practical robotics, data-center and hardware experience, mentorship, certifications and his future as an engineer.

Student spotlight: Leland Wang

Read Leland Wang’s transcript

Hi, my name is Leland Wang, a rising sophomore at Morehouse College studying applied physics and mechanical engineering. I was given the opportunity to work with Atlanta AI and Robotics Initiative where I gained a lot of hands-on experience dealing with Edge AI, AWS, along with deploying models on the NVIDIA Jetson Nano as well. And during my time working there, I was really surprised by how much integration goes between hardware, software, and AI. That integration is then used to solve a lot of real-life problems. I was also surprised by how much mentorship and guidance came from AARI where I was able to learn a whole lot more and do a whole lot of hands-on projects to then complement my skills. I would definitely recommend AARI to any student who's looking to not just participate in something but really learn and grow from something as well. Yes, AARI has permission. Use my quote, name, image, video for social media and program promotion.

Automatically transcribed from the student testimonial.

Video summary: Leland Wang shares his experience as an AARI student.