Waterloo Software Engineering AIF, Interview and SE Form
Waterloo Software Engineering applicants complete three things beyond grades: the Admission Information Form, the online Engineering interview, and a Supplementary Information Form about programming experience that only Software Engineering asks for. This guide covers what each means for SE specifically, what Waterloo says the program is looking for, and practice prompts. The general AIF and video format is in the Waterloo Engineering guide.
The three parts, and which one is SE-only
Waterloo’s Admission Information Form page lists what Engineering applicants complete: the AIF, the online video interview (“required for admission”), an optional Engineering program alternate-choice form, and, for Software Engineering applicants only, a Supplementary Information Form “where they share details about their programming experience and demonstrated interest in the field.” The program page turns that into a requirement: “You’re required to have experience in a programming course (such as Grade 11 or 12 computing and/or information science or equivalent) or self-study and a demonstrated interest in solving open problems, debugging code, testing code, and learning new software languages.”
The rest is the same as every Waterloo Engineering program. SE is offered jointly by the Faculty of Engineering and the Faculty of Mathematics, co-op only, and the published admission average is “individual selection from the low to mid-90s,” the highest band Waterloo publishes for its engineering programs. Ontario prerequisites are Advanced Functions, Calculus and Vectors, Chemistry, Physics and ENG4U, each at a minimum of 70 per cent. Waterloo states that academic performance, the AIF and the online interview together carry more weight than its school-based adjustment factor.
The video question is published
Waterloo’s online Engineering interview page prints the one graded question: “What experience(s), inside or outside the classroom, motivated you to apply to your chosen engineering program?” There is a 90-second response limit and one attempt, on Kira Talent, with practice questions beforehand. A second, ungraded yes/no question asks whether you have participated in FIRST Robotics. Waterloo says the assessment “focuses on the content of your response rather than polished presentation skills,” that strong responses share genuine experiences, explain how they shaped the program interest, reflect on goals and show the program fits, and that the response may also count for scholarships.
Knowing the question in advance is a trap for SE applicants in particular, because the obvious answer is a list: I started with Scratch, then Python, then a hackathon, then a personal project. Lists are not experiences. Pick one experience, ideally one where you were stuck, and use it to explain why software engineering rather than computer science, which is the choice the reader knows you had. Waterloo’s own SE page draws the line: SE “focuses on the design, development, testing and maintenance of software systems” and applying engineering principles to it; CS concentrates on the theoretical foundations of computation. If your story is about the moment you cared whether the thing shipped and kept working, you are describing SE.
What the AIF asks, read for SE
The five questions are the same for every Waterloo applicant and the Waterloo Engineering guide covers each at its 150-word limit. What changes for SE is where the programming evidence goes. Question 1 (a passion or strong interest, how and when it began, what it taught you about yourself) is the natural home for the project you cannot stop working on. Question 4 (your primary goal for attending Waterloo, whether you have explored the field, who you turned to for advice) is where co-op belongs: SE students alternate school and work every four months from first year, and the AIF reads for co-op readiness. Do not put the programming course list in the AIF; that is what the Supplementary Information Form is for, and the AIF is reviewed both by trained readers and by AI with identifying details removed, so it rewards a specific claim with evidence over a résumé.
The Supplementary Information Form
Waterloo describes what it wants in one sentence: programming course experience or self-study, plus demonstrated interest in solving open problems, debugging, testing and learning new languages. Those four verbs are the rubric you have. For each, have one concrete instance ready: a problem with no given answer you worked at, a bug you hunted and how, a time you wrote tests or found out why you should have, and a language you picked up because a project needed it. The form is not the place to be modest, and not the place to claim a language you could not write a loop in tomorrow.
A note on Systems Design
Systems Design Engineering applicants complete the same AIF and the same online interview, with a published average of high 80s to low 90s and no programming form. Older cycles gave SYDE applicants a second video question used for scholarship consideration; the current interview page does not mention it, so confirm on the official page rather than preparing for it blind.
Eight practice prompts for SE applicants
These are AcceptMe’s practice prompts, written to the four verbs on Waterloo’s SE requirement, to the published interview question, and to the AIF themes. They are not Waterloo’s questions, apart from the fact that the real interview question is printed above and you should practice that one too. Run the video ones on a short prep timer and a 90-second clock; draft the written ones at 150 words.
- Tell us about the bug that took you longest to find. What did you try, in order, and what finally showed you where it was?
- Describe a program you wrote that other people used. What broke once it left your machine, and what did you change?
- You picked up a new language or framework because a project needed it. How did you learn it, and what did you get wrong for the first week?
- Why Software Engineering at Waterloo rather than Computer Science at Waterloo? Use one experience, not a comparison of course lists.
- Tell us about a problem with no given answer that you worked at anyway. How did you decide you were done?
- Your first co-op interview is in September of first year. What would you put on the résumé today, and what is the gap you would spend the summer closing?
- Written, 150 words: a passion or strong interest you have had for more than two years. When did it start, and what has it taught you about how you learn?
- Written, 150 words: describe a time you disagreed with a teammate about how to build something. How did you settle it, and was the result right?
A worked answer
The experience that pushed me toward software engineering specifically was a scheduling tool I wrote for my school’s peer tutoring program. Writing it took a weekend. The next six months were the real project. The first week a tutor booked two students at once because I had not handled time zones for the one kid who was abroad. The second month it stopped sending emails because the free service I used changed its limits. By spring I had a list of things people wanted that would have broken things other people relied on, and I had to say no to some of them and explain why. None of that was the interesting computer science; it was all the part where software meets people who depend on it. I liked that part more than I expected to. When I read that Waterloo’s SE program is about the design, testing and maintenance of systems, and that co-op starts in first year, that was the description of the six months, not the weekend. I asked our computer science teacher whether that meant SE rather than CS, and she said if maintenance was the part I liked, yes. That is why I applied.
One experience, an honest sequence of things going wrong, a reason for SE over CS drawn from that experience, one person consulted, and a last sentence ready before the clock runs out. It answers every clause of Waterloo’s question without listing a single language.
Mistakes specific to Software Engineering
- Not finding the Supplementary Information Form. It is SE-only and appears in the portal, not on the OUAC application. Check every link the portal shows.
- Answering the video question with a language timeline. The question asks for an experience.
- Treating SE and CS as the same application. They are in different faculties with different deadlines; if you apply to both, the Engineering date of February 1 governs, and the reader will want to know why SE.
- Claiming demonstrated interest without a demonstration. Four verbs, four instances. If one is missing, spend the next month getting it.
- Reading a memorized answer to a question you knew was coming. Waterloo says content over polish; a script sounds like polish and reads as no content.
Where to go from here
The Waterloo Engineering AIF and video guide walks through all five AIF questions at 150 words and the 90-second format. If you have also applied to Waterloo Computer Science, the Math and CS AIF guide covers the Faculty of Mathematics version, including the contest section. The guide to Kira Talent interviews explains what the platform lets you do with practice questions and notes, and the why-this-program guide has a four-beat structure that fits the published question exactly. Then run the real question through an AcceptMe custom interview at a short prep window and a 90-second clock, and read the transcript for the moment your one experience turned back into a list.
Keep reading
- Waterloo Engineering AIF and Video: Sample Answers and Prep How Waterloo reads the AIF's 150-word answers, what the mandatory video interview asks, fifteen practice questions and a worked answer about a build.
- Waterloo Math and CS AIF: Questions and Sample Answers The Waterloo Faculty of Mathematics AIF question by question, the contest section, how it is scored alongside grades, and a worked 150-word answer.
- Why Do You Want to Study This Program? Sample Answers A four-beat structure, worked answers for commerce, engineering and health sciences, the answers that lose, and a 20-minute program research method.