// parents' faq
What parents ask us.
My child has never coded. Where do they start?
Foundations. Ages 8–10 start with block-based coding and simple machines; ages 11+ with no experience start in an accelerated bridge unit that reaches Python within ten weeks. Nobody is placed by age alone — we do a short, friendly placement session before the first class.
How much screen time is this, really?
Less than you'd think. Robotics sessions are mostly hands on hardware — wiring, building, testing on the floor mat. Coding sessions are on screens, but writing and debugging a program is closer to building with LEGO than to watching videos. There is no homework app and no gamified points system.
What does my child actually have at the end of a unit?
Something that works, and a record of how it got there: a demo-day presentation, the project itself, and their engineering notebook. By the end of a full track, older students have a small portfolio they can genuinely show a high school or future employer.
Who teaches, and how are they vetted?
Lead instructors must have professional software or hardware experience plus teaching experience; assistants are typically engineering students. All staff will be background-checked before the first session, and we'll publish our instructor standards in full before enrollment opens.
Is this only for kids who want engineering careers?
No. Debugging teaches patience; robotics teaches that failure is information; competition teaches teamwork under pressure. Those transfer to any path. Some of our future students will become engineers — all of them will become better problem-solvers.
When and where do classes start?
We're planning the first Chicago location now. Dates, address, and tuition will be announced to the waitlist before anywhere else — joining the waitlist is free and commits you to nothing.