12
Students per cohort
8
Weeks of build time
3
Teams of 4 to 5
1
Live pitch at corporate

Application Required Only 12 Seats Available. Apply before the cohort closes.

The application takes about 20 minutes to complete. We use it to score, balance the cohort, and place each student on the right team.


HOW THE 8 WEEKS UNFOLD

From a real problem to a live pitch.

Every week has a clear goal. Students don’t follow worksheets. They define a problem, build a solution, and ship working software with AI as a tool, not a crutch.

Frame and plan

Weeks 1–2 • Jun 15 – Jun 28

Students are placed in skill-balanced teams of 4 to 5, choose a real iCode problem to solve, and learn to build with AI from intent to implementation.

Build the foundation

Weeks 3–4 • Jun 29 – Jul 12

The app comes to life. Teams ship their first working features, connect a real database, and meet with their assigned industry mentor.

Integrate and polish

Weeks 5–6 • Jul 13 – Jul 26

End-to-end user flows. AI integration where it makes sense. By Week 6, the MVP is locked. No new features after that.

Test, story, pitch

Weeks 7–8 • Jul 27 – Aug 7

Internal testing, narrative building, dress rehearsals. Week 8 ends with a live pitch at iCode Corporate. Certificates awarded.


What they’ll actually build

Three real problems, three real solutions.

Each of the three teams in the cohort takes on one of these challenges. Real operational pain points sourced from iCode, not invented exercises.

Track 1: Material Inventory System

Build a tool that helps iCode locations track equipment, supplies, and consumables across classrooms. Real inventory, real data, real decisions.

Track 2: Video Pool System

Build a platform for organizing, tagging, and searching the growing library of iCode instructional videos so the right content reaches the right student.

Track 3: Belt Assessment Bot

Build an AI-powered assistant that helps instructors evaluate student progression through the iCode belt system more consistently and faster.


The Six Most Important Things to Have Ready Day One of College Applications

Robot in Classroom

Item 01: A portfolio-ready project

A working software product on their personal GitHub. Built with Next.js, MongoDB, and Google Gemini. Code they own and can show on any application or interview.

Item 02: A corporate internship certificate

Awarded at the final pitch event at iCode Corporate, signed by leadership. Recognizes completion of a real, demanding program. Not a participation award.

Item 03: Mentorship from working professionals

Each team is paired with a tech mentor from industry. Mentors give product feedback in Week 4 and attend the final pitch. Relationships that often outlast the program.

Item 04: Real team experience on real problems

Students don’t solve textbook exercises. They tackle actual operational challenges sourced from iCode and other companies. Their work could become a real tool someone uses.

Item 05: Live pitch experience

The program ends with each team presenting to leadership and developers at iCode Corporate. Five to ten minutes, live demo, Q&A. The kind of moment that builds real confidence.

Item 06: A personalized college pathway plan

Based on your student’s strengths during the build, our instructor drafts a plan suggesting tech career directions, college programs, and next steps to consider.


What parents ask first

The questions we hear most, answered plainly.

My child has never coded before. Is this program for them?

Yes, if they have genuine curiosity and can commit to the time. We intentionally select for motivation and willingness to learn, not prior coding experience. Beginners thrive in this program because they use AI tools that translate their ideas into working code. What we cannot teach in 8 weeks is curiosity. That has to come with them.

How much time will my student actually spend on this?

Four hours of guided sessions per week — two sessions of two hours each — plus open lab time for self-paced work. Most students put in an additional 2 to 4 hours per week outside of sessions during the build phase. Total commitment is roughly 6 to 8 hours per week across the 8 weeks.

Will my student work alone or in a team?

In a team. The cohort of 12 is divided into three teams of 4 to 5, balanced by skill profile. Each student takes on a primary role — builder, AI thinker, product thinker, or communicator — and contributes across areas. Working in a team is part of the value. It’s how real software gets built.

What if my student misses a session?

Occasional absences happen. We ask you to disclose any planned absences on the application so we can plan around them. Students can use open lab time to catch up. However, students who miss multiple sessions struggle to keep up with their team, so consistent attendance matters.

Is the application competitive?

Yes. Enrollment is limited to 12 students per cohort, and we typically receive more applications than seats. Selection is based on motivation, commitment, communication skills, and how a student’s skill profile fits the cohort. We score every application against a published rubric and select for balance, not just top scores.

What technology will my student use?

The same tools used in industry. GitHub for version control, Next.js for the application framework, MongoDB for data, Google Gemini for AI workflows where applicable, and iCode’s NEXUS IDE for project management. Students leave with transferable experience on real-world software, not toy tools.

What does my student need to bring?

A laptop they can install software on — Mac or PC, less than 5 years old preferred — and an active interest in solving problems. We provide everything else: accounts, tools, mentorship, and the project.

How and when do we find out if my student is accepted?

Applications are reviewed within two weeks of the deadline. You’ll receive a decision by email: accepted, waitlisted, or not selected this cohort. Accepted students receive program details, enrollment instructions, and a welcome packet.