Toronto: Computer Science / supplemental short answer
Short written response in the program supplemental application (length varies by program; keep it tight and specific)
Tell us about your experience with programming or computer science and what draws you to the field.
Several Toronto programs add a short-answer supplemental, and Computer Science (St. George and Mississauga) now requires one designed to assess skills and interest beyond grades. A representative version asks about your actual programming experience and why the field draws you. Treat it as a focused short answer, not an essay.
CS at Toronto is one of its most competitive admits, and strong grades alone no longer distinguish applicants. The committee wants proof you have engaged with computing on your own terms: code you have written, a problem you solved, a thing you were curious enough to build. They are filtering for genuine interest, not buzzwords.
Name one concrete thing you built or coded, however small, and what it does.
Describe a bug you chased, a problem you decomposed, or a trade-off you made.
Say what kind of problems you want to work on, and why Toronto fits that interest.
“In today's world, technology is everywhere, and I have always been passionate about computers and coding.”
“My first program was a script to sort my music library, and it broke the instant a song title had a comma in it.”
- 1Opens with a real, mundane problem instead of a claim of lifelong passion. Toronto's CS prompt rewards tight, specific evidence, so a concrete origin beats abstract enthusiasm.
- 2Shows learning driven by a real need rather than a course requirement, which reads as genuine initiative.
- 3Names specific concepts (loops, off-by-one errors) to prove genuine hands-on experience rather than buzzwords.
- 4Demonstrates progression from a tool to a real language with a modest, honest scope. The unembarrassed pride reads as an authentic applicant voice.
- 5Articulates a real, thought-through reason for the field, showing the clear thinking and genuine fit the school screens for rather than a generic love of technology.
- 6Ends by naming a concrete limit of self-teaching and a shift toward deeper questions, signaling readiness for a rigorous program and fit with university study.
- What is one thing I have actually coded or built, even a tiny one?
- What bug or problem taught me something about how systems really behave?
- What kind of computing problems do I want to work on next?
- Did I show real, specific programming experience rather than claiming passion?
- Did I reveal how I think and solve problems?
- Is it concise and clearly tied to computer science at Toronto?
Drafted it? Get an honest, admissions-style read, free.
Score my essay