FAQ
Questions, answered plainly
Who can apply?
Undergraduate and master's students, any major. Tell us about yourself and what you've made in the application form.
Do I need to know how to code?
No. You'll build with AI coding tools, and week 0 sets everything up. You do need to be willing to learn by doing.
How much time does it take?
About 10 hours a week for 8 weeks, mostly on your own schedule, plus one hour of group review a week. If you can't commit that, please wait for a later cohort.
What if my product fails?
That's allowed. A well-documented failure counts as a Completed outcome, and an honest case study of why it didn't work is worth more than a made-up success.
How are applications reviewed?
By a person, with school names removed. We look at three things: did you ship the 48-hour task, is your account of it honest, and are you working on a real problem for real people.
Who runs STARC, and who reviews my work?
A small team. We don't list names yet; we'd rather be judged by our published rules and our students' public work. AI helps summarize and draft feedback, that's always labeled, and a person reads everything before it's sent.
Will I get a certificate or a recommendation letter?
No certificate. Your proof is a public link to your product, your numbers and your logs. We don't sell recommendation letters.
Will my build logs be public?
Only if you agree, one log at a time, with your name or anonymously. You can withdraw a published log.
How is this different from other programs?
We don't promise outcomes, we don't do the work for you, and we judge you by what you actually built. If a program can't tell you exactly what you'll do each week, ask why.
Does STARC help publish papers for students?
No. The research track puts you inside real research. If the work merits publication, that's the outcome of the work, never something we sell or promise.
Something not covered? Email info@starc.institute.