As a 330 TA, you get to help continue the tradition of 330 being the best class.
You get to contribute directly to almost all aspects of the course, which in turn
means you get to help influence hundreds of students per semester.
We also believe that learning does not stop once you become a TA. We train our TAs in
a variety of industry and non-industry tools like Git/Github, Docker, Bash, and LOLCODE.
To be a TA in the CS Department, the following must be true:
- You must have a cumulative GPA over 3.0
- You must have received or are projected to receive an A- or higher
- You must not be a TA for any other department
You can read more about this on the department website.
FAQ
How many slots do you have open?
Not sure. Depends on how many current TAs graduated and the enrollment numbers of the course.
Do you have any further restrictions than the departmental ones?
Nope! In fact, I try to waive the A- requirement. Just because you did well in the course does not mean you make a good TA.
What are you looking for in a TA?
Try to think about TAs you have had or have currently. What qualities do you like about them, and what qualities do you not like about them? Channel the former and not the latter.
Do you have a distinction between discussion TAs and grading TAs?
Nope. Everyone grades. If you want to do more you can lead a discussion, but that is considered extra to your TA duties.
Can I lead multiple discussions?
Depends on demand. I try to give everyone who wants a discussion the opportunity. There may be more pigeon holes than pigeons or vice versa.
Do I get a rubber duck?
Yes! I give you one (1) rubber duck each semester you TA for me.