Applications for the Spring 2019 semester are CLOSED.
Overview
If you have taken a CompSci course previously, then you know there are many other people helping the professor to support your learning in that course, e.g., returning feedback about your assignments, reviewing concepts in a recitation section. Most of these duties are done by undergraduate students just like you! Here, you can get a chance to take part in a rewarding job, allowing you to help your fellow students out as they go through the same journey you once did.
We select UTAs on a rolling basis, so please apply as soon as possible, especially before the last day of class (Friday December 7, 2018). Depending on which course(s) you applied for, you may receive separate emails with follow up surveys or questions. Students applying for 101, 201, and 250 will likely have to interview.
Our goal is to get back to you early winter break. However, keep in mind various faculty have different timelines for selecting their UTAs.
Contact the Ugrad Program Coordinator, Georgia Tse, georgia@cs.duke.edu if you have any questions about being a UTA.
Consideration
Ideally, you loved the course that you want to UTA for! You should have at least taken the course before and have done well, or communicate with the professor that you feel confident that you grasped the materials covered in the course you would like to UTA.
For 101/201 -- If you choose one as a first choice and the other as a second choice, you will not likely be considered for the second choice course, regardless if you were a previous UTA for that course. For example, if you put 101 as your first choice and 201 as your second choice, you will not be considered for 201 because it is your second choice, and vice versa. This is only the case for 101/201 because of the number of applications we receive.
Courses that need UTAs for Spring 2019
| Course | Expected Duties | Consideration |
| CompSci 94.01: Programming/Problem Solving (Rodger) |
|
Min Requirement: Completion of CompSci 101. Must have availability to attend lecture sections TuThu 10:05-11:20am in LSRC D106. |
| CompSci 101: Intro to Computer Science (Stephens-Martinez): |
|
Recitations are throughout W 11:45am-7:30pm Lab training is M/Tu 6:15-7:15pm |
| CompSci 116: Foundations of Data Science (Forbes) |
|
You can apply if you have Python, stats, or data science experience. Must have availability to attend lectures TuTh 3:05-4:20pm |
| CompSci 201: Data Structures and Algorithms (Astrachan) |
|
Must have availability to lead a recitation section, which are throughout M 10:05am–5:55pm. |
| CompSci 216: Everything Data (Machanavajjhala, Forbes) |
|
Min requirement: CompSci Major. Completion of CompSci 216 or 316. Experience with Python, Git, and Jupyter notebooks. Availability to attend the course, TuTh 1:25pm-2:40pm, but not necessary. |
| CompSci 230 Discrete Math for CompSci (Panigrahi) |
|
You can apply if you have at least completed CompSci 230 or equivalent. You should be able to handle the concepts the students work with in this course. Recitation is various times on Fri 10:05am-4:20pm. |
| CompSci 250: Computer Architecture (Sorin, ECE) | Pick at least 2 of the following:
|
Recitation is various times on Th 3:05-7:30pm. |
| CompSci 270: Intro to AI (Conitzer) |
|
Min Requirement: CompSci 270 or 570 or indicate a strong interest in these topics and have a strong programming or math background. |
| CompSci 290.5: Software Rapid Prototyping (Azhar) |
Mentor 2-4 student development teams of 2-6 students each
|
Min Requirement: Internship experience or CompSci 207, 308, or 408 |
|
CompSci 307: Software Design and Implementation (Duvall) |
|
Min Requirement: Completion of CompSci 308 Indicating preference for one of 307D/308 will put you in the same consideration pool, so you don't have to put both courses in your preferences. |
| CompSci 308: Advanced Software Design and Implementation (Duvall) |
|
Indicating preference for one of 307D/308 will put you in the same consideration pool, so you don't have to put both courses in your preferences. |
| CompSci 310: Intro to Operating Systems (Lebeck) |
|
|
| CompSci 316: Intro to Database Systems (Roy) |
|
|
| CompSci 330: Design/Analysis Algorithms (Ge) |
|
|
| CompSci 334: Mathematical Foundations (Rodger) | Background working with JFLAP | |
| CompSci 342: Information and the Internet (Astrachan) | info pending |
|
| CompSci 590.01: Computer Security (Maggs) |
If there is a course not listed here that you have been asked to UTA, or have heard needs UTAs, you may list the course number in the last free response question on the application. If you are willing to TA multiple courses, indicate that in the last free response question.
Duties and Commitment
Being a UTA is a serious obligation that requires a firm and substantial weekly commitment on your part. It requires timely checking and responses to communication (e.g. email, Slack, Piazza). It is a semester-by-semester job that extends from the first day of classes through the end of final exams. You must re-apply each semester.
All UTAs will be required to attend a training session at the beginning of the semester before school starts.
Duties will vary between classes, but you can generally expect to do some of the following:
- Grade – Responsibilities range from students’ assignments or in upper-level courses, projects. Sometimes a professor may have UTAs grade student exams.
- Hold office hours – Most courses will have office hours in the evening. Office hours are used to answer student questions about topics covered in lecture, homework problems, etc.
- Lead a recitation/lab – Lower level courses such as 101, 201, 230, etc. have a discussion section where students will get more application problems on topics covered in class. UTAs will lead students through the problems and facilitate collaboration and discussion among students about the topic. UTAs will have to prepare beforehand by attending a lab meeting, and/or looking over the material, and/or doing the problems beforehand so that they can come prepared for answering questions.
- Answer Piazza questions – Most courses use Piazza as a tool where instructors can post course announcements, and communicate important information to students. Students can use this platform to ask questions about logistics of the course, get clarification on the homework, or a study problem. The professor cannot answer all questions in a timely manner, so UTAs will also respond to questions that students may have.
- Attend planning meetings – Faculty will arrange a regular meeting to gather all their UTAs so that they can prepare UTAs for the upcoming week or address questions and concerns that UTAs may also have.
- Meet with student groups – Some project-based courses such as 308 or 316 will require that UTAs independently meet with the group of students that they are assigned to.
- Administrative duties - If you are a Head UTA, you may have to send out emails and organize various UTAs for specific duties. The professor will be in close contact and instruct you.
- Attend lecture - Some faculty need UTAs during regular class time because the course is structured like a lab.
Compensation
The pay begins at $10 per hour with opportunities for promotions and increases after the third semester of serving as a UTA. You must detail your hours biweekly and fill out a timecard on time.
Work Study
Work study is not required for this job, but it is encouraged. You do not have to be on financial aid to be on work study. Please see the Duke Financial Aid Work Study section for more information on how to sign up for work study.