diff --git a/404.html b/404.html index ac9d769..f1d8863 100644 --- a/404.html +++ b/404.html @@ -1,4 +1,4 @@ 404 Page not found | Princeton COS Undergraduate Course Assistants Program - +

404

Page Not Found

Princeton COS Undergraduate Course Assistants Program

\ No newline at end of file diff --git a/categories/index.html b/categories/index.html index 95fd212..0cf888e 100644 --- a/categories/index.html +++ b/categories/index.html @@ -1,5 +1,5 @@ Categories | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/applicants/apply/index.html b/docs/applicants/apply/index.html index a88c535..422cead 100644 --- a/docs/applicants/apply/index.html +++ b/docs/applicants/apply/index.html @@ -5,7 +5,7 @@ Applications are submitted on the TigerUHR registration page. Transcript Information # As part of the application process, TigerUHR will ask that you submit an up-to-date transcript. These documents can be obtained from TigerHub. Internal Transcript # Also acceptable: Degree Progress Report # ">How/When to Apply | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/applicants/choice/index.html b/docs/applicants/choice/index.html index bffbeca..8488f8e 100644 --- a/docs/applicants/choice/index.html +++ b/docs/applicants/choice/index.html @@ -1,7 +1,7 @@ Rules for Choosing a Job | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/applicants/index.html b/docs/applicants/index.html index 69f41ba..6a2084d 100644 --- a/docs/applicants/index.html +++ b/docs/applicants/index.html @@ -1,5 +1,5 @@ <strong>For Prospective Applicants</strong> | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/applicants/interview/index.html b/docs/applicants/interview/index.html index 20eb3ec..3dca7f0 100644 --- a/docs/applicants/interview/index.html +++ b/docs/applicants/interview/index.html @@ -5,7 +5,7 @@ COS 126 Lab TA COS 2xx Lab TA Because scheduling and giving interviews takes time, these jobs usually have an earlier deadline than most jobs. Information about the COS Lab Interview Process # Julia Ruskin BSE ‘22, Head Lab TA in 2021, describes the interview process for the Intro COS Lab in the following way: We interview to get a sense for how the candidates would act when interacting with students.">Jobs that Require An Interview | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/applicants/jobs/index.html b/docs/applicants/jobs/index.html index 223f5a1..590abe3 100644 --- a/docs/applicants/jobs/index.html +++ b/docs/applicants/jobs/index.html @@ -2,8 +2,8 @@ General Job Categories # The department employs undergraduates to assist with many COS courses. The jobs are divided into three categories (most paid $18/hr): Lab TAs who help students in undergraduate-staffed office hours Graders who grade assignments and (in some courses) exams In-class TAs who help students in the classroom (these positions are called facilitators or precept assistants) Some Independent Work (IW) seminars also hires 1-2 UCAs to do a combination of all three jobs (assisting in class to provide feedback to student presenting their projects, grading projects, and providing office hours for students to get help with their projects).">COS UCA Job Catalog | Princeton COS Undergraduate Course Assistants Program - +Lab TAs who help students in undergraduate-staffed office hours Graders who grade assignments and (in some courses) exams In-class TAs who help students in the classroom (these positions are called facilitators or precept assistants) Some Independent Work (IW) seminars also hires 1-2 UCAs to do a combination of all three jobs (assisting in class to provide feedback to student presenting their projects, grading projects, and providing office hours for students to get help with their projects).">COS UCA Job Catalog | Princeton COS Undergraduate Course Assistants Program +
@@ -57,8 +57,8 @@ with the course

COS 240: Reasoning About Computation #

For description and past ratings, see course page on Princeton Courses

Grader position -#

Supervised by Prof. Iasonas Petras (Spring 2024)

Team communication: Email

Description:

The COS 240 grader grades COS 240 students’ work and provides feedback.

Responsibilities:

  • Grade (asynchronously) students’ work and provide feedback for ~5-7 hours a week (on weeks when grading takes place, which is more or less every 2 weeks).

  • Attend (and participate in) grading consistency meetings (most likely online) taking place on Thursdays 4:30PM-5:30PM

  • Attend (and participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM

  • Meet grading deadlines consistently

Requirements:

  • Having taken COS 240 and performed well

  • Must have satisfactorily answered the supplemental survey

Lab TA position -#

Supervised by Prof. Iasonas Petras (Spring 2024)

Description:

The COS 240 Lab TA holds office hours where COS 240 students can ask questions on and discuss the course material and the course’s assignments. "

Responsibilities (~6 hrs/week):

  • Hold 4 hours of office hours per week.

  • Attend (and participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM

Requirements:

  • Having taken COS 240 and performed well

  • Must have satisfactorily answered the supplemental survey

COS 302: Mathematics for Numerical Computing and Machine Learning +#

Supervised by Prof. Iasonas Petras (Fall 2024)

Team communication: Email

Description:

The COS 240 grader grades COS 240 students’ work and provides feedback.

Responsibilities:

  • Grade (asynchronously) students’ work and provide feedback for ~5-7 hours a week (on weeks when grading takes place, which is more or less every 2 weeks).

  • Attend (and actively participate in) grading consistency meetings (most likely online) taking place on Thursdays 4:30PM-5:30PM

  • Attend (and actively participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM

  • Meet grading deadlines consistently

Requirements:

  • Having taken COS 240 and performed well

  • Must have satisfactorily answered the supplemental survey

Lab TA position +#

Supervised by Prof. Iasonas Petras (Fall 2024)

Description:

The COS 240 Lab TA holds office hours where COS 240 students can ask questions on and discuss the course material and the course’s assignments. "

Responsibilities (~6 hrs/week):

  • Hold 4 hours of office hours per week.

  • Attend (and actively participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM

Requirements:

  • Having taken COS 240 and performed well

  • Must have satisfactorily answered the supplemental survey

COS 302: Mathematics for Numerical Computing and Machine Learning #

For description and past ratings, see course page on Princeton Courses.

Supervised by Prof. Ryan Adams (Fall 2023)

Team communication: a course staff Slack channel

Description: This position grades assignments and exams. In both cases, submissions will be done through Gradescope. Generally there are two kinds of problems on the assignments: conceptual math problems, and practical work in Python. The Python is submitted as a colab notebook. Graders are expected to provide helpful and fair feedback that encourages understanding.

Responsibilities (~5 hrs/week:)

  • Graders are expected to be reasonably responsive after assignment submission in order to determine who will grade what problems and to ask for help as necessary. My goal is to provide grades and feedback within a week.

Requirements:

  • Familiarity with the material

COS 324: Introduction to Machine Learning @@ -140,6 +140,6 @@ #

See academic website.

Team communication: Slack

Description:

This position supports the course infrastructure and assists students in using it.

The course infrastructure consists of virtual machines and services hosted by Amazon, Microsoft, and Google. The purpose of this course is to gain experience using and configuring distributed systems. Experience with kubernetes, S3, EC2, Azure, or any other cloud-hosted services and cloud providers will be helpful. TAs will ensure virtual services remain available, help configure them correctly for the course, and help students effectively use these resources.

Responsibilities (~8 hrs/week):

  • Attend weekly 30min/week sync-up meeting to check on status of course infrastructure and assign action items

  • Take direct responsibility for a particular cloud service or vendor

  • Configure networking and services on virtual machines

  • hold 2-4 hours / week of office hours for students attempting to use these services

  • communicate availability and summarize expected progress with cloud-specific tasks

  • monitor course email and slack

  • monitor assigned cloud services

Requirements:

  • experience using linux-based systems

  • comfort on the command line

  • familiarity with at least one cloud service

Prof. Huacheng Yu #

See -academic website.

Team communication: Email

Description:

UCAs participate in in-class discussions, give quick feedbacks to the student presentations in class and project proposal and mid-term reports, and hold office hours.

Responsibilities (~3 hrs/week):

  • Attend weekly class meetings (80 minutes)

  • Hold a 1-hr office hour every week

  • Attend TA meetings before “grading” the proposal and mid-term report

Requirements:

  • Must be COS or ORFE/MAT majors

  • Must have taken a COS 4xx (and gotten an A- or better) or a 5xx-level theory course

\ No newline at end of file diff --git a/docs/employees/index.html b/docs/employees/index.html index 5efd146..706bc94 100644 --- a/docs/employees/index.html +++ b/docs/employees/index.html @@ -1,5 +1,5 @@ For Current Employees | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/employees/payroll/index.html b/docs/employees/payroll/index.html index d504e4f..3e98d8e 100644 --- a/docs/employees/payroll/index.html +++ b/docs/employees/payroll/index.html @@ -1,7 +1,7 @@ Before Getting Paid… | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/employees/slack/index.html b/docs/employees/slack/index.html index 8444a80..b0ee060 100644 --- a/docs/employees/slack/index.html +++ b/docs/employees/slack/index.html @@ -3,7 +3,7 @@ The rosters for this Slack are automatically synchronized based on TigerUHR’s rosters. You will automatically be placed in the appropriate channels.">The UCA Slack | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/employees/time-collection/index.html b/docs/employees/time-collection/index.html index 114d7df..edbd26a 100644 --- a/docs/employees/time-collection/index.html +++ b/docs/employees/time-collection/index.html @@ -1,5 +1,5 @@ How to Declare Your Hours | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/general/contact/index.html b/docs/general/contact/index.html index 7839f9c..4e3fc01 100644 --- a/docs/general/contact/index.html +++ b/docs/general/contact/index.html @@ -5,7 +5,7 @@ UCAs provide support in a couple dozen of courses of the Department of Computer Science, they are one of the most prized resources of Princeton. Because our program is so large, because we have such a diverse array of courses staffed with UCAs, the experience of being a UCA can have some variability. We strive to meticulously follow the official guidance policy set forth by the Office of the Dean of the College, in consultation with the McGraw Center for Teaching and Learning.">Contact Us / Report a Problem | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/general/contribute/index.html b/docs/general/contribute/index.html index 7b8b65c..6fdad63 100644 --- a/docs/general/contribute/index.html +++ b/docs/general/contribute/index.html @@ -1,7 +1,7 @@ How to Contribute to this Site | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/general/index.html b/docs/general/index.html index 09f9761..15140e0 100644 --- a/docs/general/index.html +++ b/docs/general/index.html @@ -1,5 +1,5 @@ <br/><strong>General Information</strong> | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/general/past-ucas/index.html b/docs/general/past-ucas/index.html index 09097e1..73f67a3 100644 --- a/docs/general/past-ucas/index.html +++ b/docs/general/past-ucas/index.html @@ -3,7 +3,7 @@ Alex Daifotis Erica Portnoy and Utsarga Sikder Curtis Belmont Diana Liao Sally Jiao Benjamin G. Schiffer Justin Chang and Lily Zhang Julia Ruskin Diana Espindola and Austin Li Past Tool Builders # Vinay Ayyala ‘16 (codePost) Alex Daifotis ‘14 (LabQueueV1) James Evans ‘16 (codePost) Richard Freling ‘16 (codePost) Lance Goodridge ’17 *19 (TigerUHR and LabQueueV3) Aaron Lichtblau ‘22 (LabScheduler) Moin Mir ‘23 (subswap) Jeremy Dapaah ‘24 (QTrack) ">Past Helpers | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/general/staff/index.html b/docs/general/staff/index.html index 6a2c684..e7bac58 100644 --- a/docs/general/staff/index.html +++ b/docs/general/staff/index.html @@ -1,5 +1,5 @@ Current Staff | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/index.html b/docs/index.html index 5bdd486..1878f56 100644 --- a/docs/index.html +++ b/docs/index.html @@ -1,5 +1,5 @@ Docs | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/students/index.html b/docs/students/index.html index 3df86a4..1633c9d 100644 --- a/docs/students/index.html +++ b/docs/students/index.html @@ -1,5 +1,5 @@ For Students | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/docs/timeline/index.html b/docs/timeline/index.html index b6f50c4..fd283fc 100644 --- a/docs/timeline/index.html +++ b/docs/timeline/index.html @@ -1,6 +1,6 @@ TIMELINE FOR HIRING | Princeton COS Undergraduate Course Assistants Program - +
diff --git a/en.search-data.min.4ba023eccb056c518af111f9343b02c4ed9289ee7688d8f83e117ebd476177c3.json b/en.search-data.min.4ba023eccb056c518af111f9343b02c4ed9289ee7688d8f83e117ebd476177c3.json new file mode 100644 index 0000000..8234569 --- /dev/null +++ b/en.search-data.min.4ba023eccb056c518af111f9343b02c4ed9289ee7688d8f83e117ebd476177c3.json @@ -0,0 +1 @@ +[{"id":0,"href":"/docs/general/contact/","title":"Contact Us / Report a Problem","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":"The Department of Computer Science runs a very large Undergraduate Course Assistant (UCA) program.\nUCAs provide support in a couple dozen of courses of the Department of Computer Science, they are one of the most prized resources of Princeton.\nBecause our program is so large, because we have such a diverse array of courses staffed with UCAs, the experience of being a UCA can have some variability.\nWe strive to meticulously follow the official guidance policy set forth by the Office of the Dean of the College, in consultation with the McGraw Center for Teaching and Learning.\n➡️ Please read this guidance to understand what are the expectations that the University places on the department and the faculty in the department, in terms of providing UCAs with proper oversight, management and support.\nIf you have any question, concern, feedback about any part of the process, please email the COS UCA hiring coordinators (Xiaoyan Li: xiaoyan@cs.princeton.edu, and Christopher Moretti: cmoretti@cs.princeton.edu).\n"},{"id":1,"href":"/docs/applicants/jobs/","title":"COS UCA Job Catalog","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"This page provides a general description of the responsibilities of all the jobs that are available to UCAs in Princeton University\u0026rsquo;s Department of Computer Science. It also provides a description of the different job categories.\nGeneral Job Categories # The department employs undergraduates to assist with many COS courses. The jobs are divided into three categories (most paid $18/hr):\nLab TAs who help students in undergraduate-staffed office hours Graders who grade assignments and (in some courses) exams In-class TAs who help students in the classroom (these positions are called facilitators or precept assistants) Some Independent Work (IW) seminars also hires 1-2 UCAs to do a combination of all three jobs (assisting in class to provide feedback to student presenting their projects, grading projects, and providing office hours for students to get help with their projects).\nFinally, some courses also hire a higher-level position (paid $21/hr):\nManagers who coordinate and supervise the work of other UCAs (typically managers have already worked in the course in a previous semester) Specific Job Categories # In addition to the general jobs, there are some specific jobs.\nFor instance, the Intro COS Lab (which centralizes the undergraduate-staffed office hours for COS 109, 126, 217, and 226) hires a Head Intro Lab TA or Team. The Intro COS Lab also hires a team of Interviewers, who interview prospective Intro Lab TAs.\nSeveral courses may hire UCAs on an ad-hoc basis to help with course development or tool building.\nJobs # Below is a description of all the jobs that are available, with a description of their responsibilities.\nThese jobs are not always hiring every semester, so please check TigerUHR directly for the list of jobs currently hiring.\nIntro COS Lab TA Program # Supervised by UCA hiring coordinators and the Head Lab TA Team.\nTeam communication: Slack ( central COS UCA Slack: #lab-announcements, #126-lab, #2xx-lab)\nThe Intro COS Lab, currently in Lewis 121 and 122, is a place where students taking introductory courses can go for help in debugging their programs. The Intro Lab TAs are those glorious individuals working on the front lines, providing that help. The lab is available to students taking COS 109, COS 126, 217, and 226. The Intro Lab TAs are coordinated by the Head Intro Lab TA (possibly with an Assistant), who is an undergraduate. Most of the shifts are on evenings or weekends, and they last 2 hours. Typically, a TA either has two shifts per week, or is a substitute TA.\nFor more information about the job, the conditions for applying, and the pay rate, please see this page about becoming an Intro Lab TA job.\nThe Intro COS Lab uses the LabQueue to manage the queue of students waiting for help.\nRead specific information about the job responsibilities for:\nthe Intro Lab TA job (which requires an interview if you are a first-time Intro Lab TA) the Interviewers job (apply directly by contacting the Head Intro Lab TA) the Head Intro Lab TA job COS 109: Computers in Our World # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Brian Kernighan (Fall 2023)\nTeam communication: Email\nDescription:\nAssist students in understanding problem sets and completing labs\nResponsibilities (6-8 hours/week):\nAssist in the scoring of 5 assignments spread out over the term\nAssist in the scoring of lecture or guest speaker reflections or book reports\nRequirements:\nMust have taken the class and gotten B+ (by default), Must have prior experience as a UCA (in this course), Must be COS majors, Must be specific applicant(s) that have contacted Prof. Brian Kernighan COS 126: Computer Science: An Interdisciplinary Approach # For description and past ratings, see course page on Princeton Courses\nGrader position # Supervised by Prof. Sebastian Caldas (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #126-grading)\nDescription:\nThis position grades the programming assignments and programming exams, in Java.\nGraders work through codePost to provide high-quality and supportive feedback to introductory CS students. A detailed rubric is included. The work consists of reading and understanding the student\u0026rsquo;s code, and providing feedback on the code\u0026rsquo;s correctness, efficiency and clarity.\nResponsibilities (~4-5 hrs/week):\nAttend weekly grader meeting (2-3h/week) to review the rubric and start grading synchronously. Grade late and remaining assignments asynchronously (~1h/week).\nRequirements:\nHaving taken COS 126 (B+ or better typically) Strong empathetic skills\nGood written communication skills\nPrecept Assistant position # Supervised by Prof. Sebastian Caldas (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #126-precept-assistants)\nDescription:\nPrecept assistants are responsible for helping students understand the solutions to a set of active learning exercises during precept (e.g., Java programming exercises, worksheets). You will work alongside a graduate student or faculty preceptor to help students work on these exercises and will answer questions regarding the course material.\nA great precept assistant is enthusiastic and patient. They can connect with a wide variety of students, encouraging them to ask questions while explaining the course material in a variety of ways.\nA precept assistant may also be hired as a grader or as a COS Lab TA.\nResponsibilities (~2-4 hrs/week) :\nPrepare by reviewing upcoming precept exercises before class (1h/week)\nAttend two precepts per week and answer students’ questions (2-3h/week)\nWork under the direction of a preceptor\nRequirements:\nHaving taken COS 126\nBeing able to communicate effectively with a diverse group of students\nSchedules (updated for Spring 2023):\nBefore applying to this position, please confirm you are available for one of the scheduled precepts for COS 126, which you can find here.\nCOS 217: Introduction to Programming Systems # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Christopher Moretti (Fall 2024)\nTeam communication: Slack ( central COS UCA Slack: #217-grading)\nDescription:\nThe COS 217 grader evaluates COS 217 assignment transcripts and code to grade and provide high-quality, supportive feedback on students\u0026rsquo; submissions. Grading is done via codePost using primarily pre-defined rubric notes and deductions.\nResponsibilities (~6-10 hours/week):\nAttend weekly grader meeting ~1 hour per week (Spring 2024: likely to be Thursdays 5:00-~6:00pm). During weeks an assignment is due, this meeting will refresh your memory of that assignment, describe common errors, and review the rubric and codePost items to prepare for grading. During weeks between assignment due dates, this meeting will serve as a grading session to do some synchronous grading and get questions answered.\nGrade 8-15 submissions asynchronously. Typically this accounts for 4-8 hours per week, though some assignments may grade faster or slower than others.\nRequirements:\nHaving taken COS 217 and earned an A- or better. (Lower grades will be considered on a case-by-case basis.) COS 226: Algorithms and Data Structures # For description and past ratings, see course page on Princeton Courses\nGrader position # Supervised by Prof. Pedro Paredes (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #226-grading)\nThis position grades the programming assignments in Java, which happen about once every two weeks. It involves reading complex code, with the need to understand errors in the running time or memory efficiency of the code.\nResponsibilities (~4-6 hrs/assignment) :\nAttend weekly grader meeting (2-3h/assignment) to review the rubric and start grading synchronously.\nGrade late and remaining assignments asynchronously (~2-3h/assignment).\nRequirements:\nFor Freshman/Sophomores: Having taken COS 226 (B+ or better typically)\nFor Juniors: Grading experience in any course (or being a lab TA)\nFor Seniors: Grading experience in COS 226\nGrading Manager position # Supervised by Prof. Pedro Paredes (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #226-grading)\nDescription:\nThis position is for students that are interested in contributing to improve the class and can involve multiple things depending on your interests (see responsibilities below for examples), some of which don\u0026rsquo;t necessarily involve grading (despite the title name).\nGrading managers will work closely with Prof. Paredes\nResponsibilities (time commitment variable):\nFor students interested in grading it can be any of the following:\nSupervising the COS 226 graders (e.g. answering their questions, grading tougher submissions). Creating new materials to support the grading mission (such as the style guide, automation scripts, preparing grading briefs). Audit a subset of submissions to ensure quality of grading. For students interested in interacting with other students, responsibilities might include holding office hours, assisting in precepts and attending staff meetings with the course instructors and graduate preceptors.\nFor students interested in creating new material for the course, responsibilities might include revising assignment statements, revising precept handouts, beta testing new assignments, creating supplemental material.\nRequirements:\nHaving been a COS 226 grader for at least one semester\nA vision on what can be done to do to improve COS 226\nCandidates will be asked a few questions about what they are interested in doing for the course as well as their past experience with the course\nCOS 240: Reasoning About Computation # For description and past ratings, see course page on Princeton Courses\nGrader position # Supervised by Prof. Iasonas Petras (Fall 2024)\nTeam communication: Email\nDescription:\nThe COS 240 grader grades COS 240 students\u0026rsquo; work and provides feedback.\nResponsibilities:\nGrade (asynchronously) students\u0026rsquo; work and provide feedback for ~5-7 hours a week (on weeks when grading takes place, which is more or less every 2 weeks).\nAttend (and actively participate in) grading consistency meetings (most likely online) taking place on Thursdays 4:30PM-5:30PM\nAttend (and actively participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM\nMeet grading deadlines consistently\nRequirements:\nHaving taken COS 240 and performed well\nMust have satisfactorily answered the supplemental survey\nLab TA position # Supervised by Prof. Iasonas Petras (Fall 2024)\nDescription:\nThe COS 240 Lab TA holds office hours where COS 240 students can ask questions on and discuss the course material and the course\u0026rsquo;s assignments. \u0026quot;\nResponsibilities (~6 hrs/week):\nHold 4 hours of office hours per week.\nAttend (and actively participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM\nRequirements:\nHaving taken COS 240 and performed well\nMust have satisfactorily answered the supplemental survey\nCOS 302: Mathematics for Numerical Computing and Machine Learning # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Ryan Adams (Fall 2023)\nTeam communication: a course staff Slack channel\nDescription: This position grades assignments and exams. In both cases, submissions will be done through Gradescope. Generally there are two kinds of problems on the assignments: conceptual math problems, and practical work in Python. The Python is submitted as a colab notebook. Graders are expected to provide helpful and fair feedback that encourages understanding.\nResponsibilities (~5 hrs/week:)\nGraders are expected to be reasonably responsive after assignment submission in order to determine who will grade what problems and to ask for help as necessary. My goal is to provide grades and feedback within a week. Requirements:\nFamiliarity with the material COS 324: Introduction to Machine Learning # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Sanjeev Arora and Prof. Elad Hazan (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #324-uca)\nDescription:\nThis position is a joint grader and office hour position.\nFor grading, you will be part of the team that grades our weekly assignments, which typically alternate between a written homework (i.e. pen-and-paper pset) and a programming assignment (i.e. IPython notebook). Typically, you will grade one problem or sub-problem most weeks according to a rubric as well as handle regrade requests for your problem. Depending on the number of UCAs on the course, you may not be assigned grading every week (though you should be prepared to grade each week).\nFor office hours, you will host a weekly 2-hour office hours (either in-person or virtual, we try to offer roughly 50%-50% options) primarily for helping students get unstuck on our weekly assignments. Office hours will also provide prep support before our midterm and final.\nResponsibilities (~5-10 hrs/week, depending on whether you\u0026rsquo;re assigned grading in a given week):\nAttend and actively participate in 1-hour staff meeting each week (Mon 4:30-5:30pm for Fall 2023, most weeks on Zoom, ~1/month in-person)\nPrep for hosting office hours each week (i.e. do assignment yourself, ~2 hours/week)\nHost 2-hour office hour block each week\nGrade asynchronously one problem or sub-problem (~3-5 hours/most weeks) for the entire class (weekly grading period starts Saturday and is due Tuesdays EOD for Fall 2023)\nRequirements:\nHaving taken COS 324 and received a B+ or better\nStrong written communication skills (for grading)\nStrong oral communication and relational skills (for facilitating office hours)\nPreferred:\nPrior experience as a UCA (in any course) COS 326: Functional Programming # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Andrew Appel (Fall 2023)\nTeam communication: a course Slack\nDescription: The \u0026ldquo;COS 326 UCA\u0026rdquo; position includes grading homeworks, holding in-person office hours (typically focused on homeworks), and answering questions on Ed.\nResponsibilities (~6 hrs/week:)\nYou should regularly monitor the COS326 slack where the course staff (including UCAs) will communicate.\nGrading is asynchronous and on-line; there are 7 homeworks and for each one theres a 2-3 day window in which it ought to be graded. Since you\u0026rsquo;ve taken the course, you have a pretty clear idea what those homeworks are.\nIf you are assigned certain days/times to cover Ed, you should monitor Ed from time do time during those hours.\nIf you are assigned in-person office hours, you should be there and be helpful.\nRequirements:\nMust have taken the class and gotten B+ (by default), Must pass an interview COS 333: Advanced Programming Techniques # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Bob Dondero (Spring 2023)\nTeam communication: Email, and staff mailing list cos333instructors@lists.cs.princeton.edu\nDescription:\nA COS 333 UCA works with a graduate student TA to grade some semester-long projects.\nResponsibilities:\nThese responsibilities refer to \u0026ldquo;Reading Period\u0026rdquo; and \u0026ldquo;Dean\u0026rsquo;s Date\u0026rdquo; as defined in the Registrar\u0026rsquo;s Office\u0026rsquo;s academic calendar.\nEach UCA will participate in a ~2 hour Zoom pre-grading meeting with the lead instructor and graduate student TAs. During that meeting they will discuss the project grading rubrics. That meeting will occur sometime during Reading Period.\nAfter Dean\u0026rsquo;s Date each UCA will grade 4-to-6 projects, approximately one per day. Some slippage of that schedule will be fine. The grading will be mostly asynchronous, but could involve some synchronous interaction with the members of the teams whose projects are being graded. An UCA will devote ~5 hours to grading each project.\nFinally, each UCA will participate in a final ~4 hour Zoom meeting with the lead instructor and graduate student TAs. During that meeting they will finalize the project grades. That meeting will occur shortly before the day when course letter grades are due at the Registrar\u0026rsquo;s Office.\nRequirements:\nHaving taken COS 333 and gotten an A- or better COS 343: Algorithms for Computational Biology # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Ben Raphael (Spring 2023)\nTeam communication: Slack ( central COS UCA Slack: #343-grading)\nDescription:\nThe primary responsibility of this position is to grade 5 homework assignments, midterm, and final exam. HW assignments consist of written exercises and short programming exercises. The written exercises are graded for correctness and clarity using a detailed rubric that will be provided. Programming exercises are graded for correctness, but not for quality of code.\nUCAs who are interested in other tasks such as helping answer questions on Ed, holding office hours to answer student questions, or contributing to the development/debugging of new assignments are welcome to do so, and will be paid for time spent on these activities.\nResponsibilities (~ 5-8 hrs/week):\nAttend bi-weekly in-person staff meeting (\u0026lt;1hr)\nConsistently meet grading deadlines\nRequirements:\nMust be COS or ORFE/MAT majors (other majors acceptable with relevant experience)\nMust have taken COS 226 with a grade of B+ or better\nMust be interested in course topics (computational biology)\nPSY/COS 360: Computational Models of Cognition # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Tom Griffiths (Fall 2023)\nTeam communication: a course Slack\nDescription: This position is for a grader who will help with grading of problem sets involving programming problems and written answers. The programming problems are in Python. An auto-grader will be used, and you will interpret ambiguous cases flagged by the auto-grader and provide feedback on the code. You will also help to test problem sets and develop questions.\nResponsibilities (~10 hrs/week:)\nAttend weekly meeting (1 h/week) to coordinate on grading and course goals for the week Read rubric for grading assigned problems Test solve assigned homework problems Grade asynchronously for about 6-8h/week, flexible timing Requirements:\nMust pass an interview, Prefer students with experience in ML, e.g. COS 324 COS 375: Computer Architecture and Organization # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. David August (Fall 2023)\nTeam communication: a course Slack\nDescription: This position involves helping students with the course and grading the programming assignments.\nResponsibilities (Flexible 4~10 hrs/week:)\nOnce a week office hours or on request, and grade a few times over the semester. Requirements:\nMust have taken the class and gotten B+ (by default), Strong performance having taken COS/ECE375. Must pass an interview COS 418 Distributed Systems # For description and past ratings, see course page on Princeton Courses.\nSupervised by Supervised by Prof. Michael J. Freedman and Wyatt Lloyd (Spring 2024)\nTeam communication: a course Slack\nDescription: As a LabTA for COS 418 you will provide students with support working on our challenging programming assignments.\nResponsibilities (~5.25 hrs/week:)\n4 hours of office hours per week, typically in 2 separate 2-hour chunks 1 hour of answering questions on EdStem per week (in a defined 1-hour window) course staff meeting to initially discuss responsibilities and later to discuss office hours for 1 hour roughly once a month Requirements:\nMust have taken the class and gotten B+ (by default) COS 423 Theory of Algorithms # For description and past ratings, see course page on Princeton Courses.\nSupervised by Supervised by Prof. Robert Tarjan (Spring 2024)\nTeam communication: TBA\nDescription: In this course, UTAs help students complete their coursework. They hold office hours, help in precept, answer questions on Ed, and participate in the grading team. .\nResponsibilities (10 hrs/week:)\nAttend a weekly staff meeting to plan the week. Solve this year\u0026rsquo;s version of the assignments, which will differ a bit from those of previous years. Hold office hours. Help answer questions on Ed. Help the grading team. Requirements:\nMust have taken the class and gotten B+ (by default), Must pass an interview COS 426 Computer Graphics # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Adam Finkelstein (Fall 2023)\nTeam communication: centralized Slack if available\nDescription: In this course, UTAs help students complete their coursework. They hold office hours, help in precept, answer questions on Ed, and participate in the grading team. .\nResponsibilities (10 hrs/week:)\nAttend a weekly staff meeting to plan the week. Solve this year\u0026rsquo;s version of the assignments, which will differ a bit from those of previous years. Hold office hours. Help answer questions on Ed. Help the grading team. Requirements:\nMust have taken the class and gotten B+ (by default), Must pass an interview COS 429: Computer Vision # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Felix Heide and Prof. Vikram Ramaswamy (Spring 2024)\nTeam communication: a course Slack\nDescription:\nWe are looking for students with strong background in computer vision to help in this next iteration of the course.\nAll UCAs will be expected to assist with grading of assignments and exams.\nBeyond that, we would welcome help with:\nUCA-run office hours\nUCA support to help guide the final projects\nUCA support with debugging any new assignments\nUCA support with grading the poster session and/or the final project reports\nUCA support with the two exam review sessions\nResponsibilities (~5-10 hrs/week, depending on whether there is grading in a given week):\nThere are 4 assignments and 2 exams. These will be due approximately every 2 weeks and need to be graded within a week. UCAs will be expected to be available to turn the grading around within about 5 days, and to work closely with the grad TA responsible for each assignment.\nRequirements:\nHaving taken COS 429 and gotten an A- or better COS 433: Cryptography # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Zeev Dvir (Spring 2023)\nTeam communication: Email\nDescription:\nThe position is for helping grade problem sets (about one Pset every other week). In addition, if the applicant is interested, they can also hold weekly office hours for additional pay.\nResponsibilities (~6-10 hrs/week):\nAttend grading meetings (about once in two weeks) to agree on grading rubrics.\nGrade about one problem in each Pset (for all ~60-70 students of the course in Spring 2023) on Gradescope. There will be about 4-5 Psets in the semester.\nRequirements:\nHaving a strong mathematical background. COS 435: Introduction to Reinforcement Learning # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Benjamin Eyesenbach and Prof. Mengdi Wang (Spring 2024)\nTeam communication: A course Slack\nDescription:\nThis position grades written and coding assignments. The coding assignments will be written in Python + PyTorch. You will work together with the graduate TAs to come up with a rubric for grading each problem. If time permits and if interested, you\u0026rsquo;re welcome to also help out in writing and testing assignments\nResponsibilities (10 hrs/week):\nWe aim to have all assignments graded within 24 hrs of submission. This means that you\u0026rsquo;ll have to block out some hours in the day after the submission for grading. Clear communication (i.e., staying on top of Slack messages from the rest of the course staff, letting us know if you\u0026rsquo;re unable to grade for some week) You won\u0026rsquo;t be expected to join the weekly staff meetings (though are welcome to if interested). Requirements:\nAn \u0026ldquo;A\u0026rdquo; in COS 324 (or equivalent). Some experience with RL. COS 445: Economics and Computation # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Matt Weinberg and Dr. Marcel Dall\u0026rsquo;Agnol (Spring 2024)\nTeam communication: Email + a course Slack\nDescription:\nUCAs for COS 445 are primarily responsible for grading (PSets, midterm, and final). That is, every UCA must grade assignments, and it is common for most UCAs to only grade assignments.\nUCAs who are interested in other tasks (such as helping answer questions on Ed, providing advice on course policy, etc.) are definitely welcome to do so (and be paid to do so, and appreciated for doing so), but the primary need is grading.\nAdditionally 1-3 UCAs can instead volunteer to be the \u0026ldquo;Strategy Design Czar(s)\u0026rdquo;. The Strategy Design Czars do not grade assignments, but are responsible for maintaining the codebase for strategy design assignments. This role requires significant independence in comparison to grading, but would be fun for students who enjoyed the strategy designs more than the PSets. If you are interested in this, you should email Matt ( smweinberg@princeton.edu) and Marcel ( dallagnol@cs.princeton.edu) to discuss.\nResponsibilities (~3-4 hrs/week):\nAttend weekly in-person meeting Thursdays 4:30PM-5:30PM. These meetings will tee up grading for the most recently submitted assignment, and we will ask you to stay for the entire hour to grade assignments with other course staff in the room.\nNote:\nWe will always be as efficient as possible with these meetings (e.g. we won\u0026rsquo;t force you to show up if you\u0026rsquo;ve already finished grading). However, we do ask that you think of in-person attendance every week as the default, and block this time off on your calendar.\nMany weeks, Matt and/or Marcel will take a subset of interested staff out for bubble tea at 5:30PM.\nGrade asynchronously ~6 hours every 2 weeks. PSets are due every other Monday. Grading tees off on Thursday, and is due 10 days later on Monday. Because the next cycle starts soon after, we do need to be sticklers about deadlines.\nBe available for ~6-8 hours (total) of grading the final on May 16/17 (the two days right after the university take-home final deadline). If you\u0026rsquo;re on-campus, we\u0026rsquo;ll ask that you grade in-person (and provide food/bubble tea). If you\u0026rsquo;re off-campus (which is completely fine), we\u0026rsquo;ll ask that you grade remotely. If your travel plans prevent you from grading (even remotely) during this period, please let Matt/Marcel know this in advance (but you do not need to change your travel plans to be available).\nThere will be no staff meeting during Spring Break, and it is entirely feasible to complete your responsibilities without working at all over Spring Break. However, some UCAs prefer to grade the midterm over Spring Break, and we will have an optional remote tee-off meeting for those who want to do so.\nBe prepared to give actual feedback on written PSet submissions to help students improve. We will try our best to make this as efficient as possible, but you should be prepared that any assignment that doesn\u0026rsquo;t receive full credit does typically require you to write something specific to that submission (copy/pasting comments across solutions historically leads to confusion by the students and results in appeals that we have to resolve anyway).\n[For Strategy Design Czars only] There is a codebase for strategy designs on github that, afaik, is complete, bug-free, etc. However, every SD still requires an initialization (TigerFile submission needs to be set up for every SD, sample files need to be uploaded for students, files need to be downloaded from TigerFile), and a run (some submissions have bugs and will crash the execution, you\u0026rsquo;ll need to figure out which ones and edit/remove them, etc.). You will also be responsible for answering any questions about the coding portion of the SDs (because Matt/Marcel may not know the answer). This requires more independence than a typical UCA role, because this has always been designed/maintained by UCAs (there is a detailed SD czar onboarding document, and previous years\u0026rsquo; czars are often happy to answer quick questions).\n[For Strategy Design Czars only] You are free to do more interesting things with the SD codebase, if that interests you. For example, you are free to add more \u0026lsquo;check submitted files\u0026rsquo; test cases so that there\u0026rsquo;s fewer buggy submissions, write more efficient code, write new \u0026lsquo;staff solutions\u0026rsquo;, or develop any new infrastructure that you think would be beneficial. But this is entirely optional\u0026ndash;your \u0026lsquo;responsibility\u0026rsquo; is just to make sure that SD files are uploaded in a timely fashion, and grades are computed in a timely fashion as well.\nRequirements:\nMust have taken COS 445 and gotten an A- or better. (If you have taken COS 445 and are interested in being a UCA, but did not earn an A- or better, feel free to reach out to Matt and/or Marcel to discuss).\nMust be available for a weekly 4:30PM-5:30PM staff meeting on Thursdays, in-person.\nIf you apply for this position, we will assume that you\u0026rsquo;ll block off every Thursday 4:30PM-5:30PM for an in-person meeting. Exceptions are possible (and we understand there will be sporadic absences), but you should email Matt ( smweinberg@princeton.edu) and Marcel ( dallagnol@cs.princeton.edu) with your situation before applying for this position.\nCOS 448: Innovating Across Technology, Business, and Marketplaces # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Robert Fish (Fall 2023)\nTeam communication: centralized Slack (TBD)\nDescription: Students will assist the class AI’s in scoring assignments and speaker reflections based on a rubric. They will also be able to attend class and listen to the lectures and guest speakers in this new and highly sought-after class. .\nResponsibilities (6~10 hrs/week:)\nAssist in the scoring of 5 assignments spread out over the term\nAssist in the scoring of lecture or guest speaker reflections or book reports\nRequirements:\nMust be interested in the course subject matter\nGood written communication analysis skills, must be better than ChatGPT.\nAny applicant will be interviewed by the course staff prior to hire and we would like to see a writing sample.\nCOS 461: Computer Networks # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Kyle Jamieson (Spring 2023)\nTeam communication: Course Slack\nDescription:\nThis position supports and grades the programming assignments for COS 461 (see https://github.com/kyleatprinceton/COS461-Public), supports precept content development, and other miscellaneous course duties.\nResponsibilities (~2-10 hrs/week):\nAttend weekly grading meetings\nHold supplemental office hours before programming assignment deadlines\nHold supplemental office hours before exams\nRequirements:\nHaving taken COS 461 and gotten an B+ or better COS 471: Blockchains, Decentralized Trust, and Their Applications # Supervised by Prof. Rob Fish and Prof. J. P. Singh (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #471-uca)\nDescription:\nStudents will assist the class AI\u0026rsquo;s in scoring programming assignments and speaker assignments based on a rubric. They will also be able to attend class and listen to the lectures and distinguished guest speakers in this class.\nResponsibilities (~6-10 hrs/week):\nAssist in the scoring of 2-3 programming assignments\nAssist in the scoring of lecture or guest speaker-based assignments\nAssist in the scoring of projects\nRequirements:\nMust be interested in the course subject matter\nGood written communication analysis skills, must be better than ChatGPT.\nAny applicant will be interviewed by the course staff prior to hire\nCOS 484: Natural Language Processing # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Karthik Narasimhan (Spring 2024)\nTeam communication: Course Slack\nDescription:\nThis position is a joint grader and office hour position.\nFor grading, you will be part of the team that grades our assignments: there are 4 + 1 assignments throughout the semester (including one warm-up), and each assignment has a written component, and a programming component based on Colab. Typically, you will grade one problem (or part of a problem) a week according to a rubric.\nFor office hours, you will host a weekly 1-hour office hours primarily for helping studying get unstuck on our assignments, or provide prep support before midterm, or provide guidance on their final project.\nResponsibilities (~4-8 hrs/week, depending on whether there is grading in a given week):\nAttend and actively participate in 30-min staff meeting each week (Thursday 4:30-5pm in COS 401)\nPrep for hosting office hours each week (0.5~2 hours; this really depends on your familiarity of the course materials. For the weeks that have an assignment due, you are expected to do the assignment yourself and it will take longer)\nHost 1-hour office hour block each week\nGrade asynchronously one problem/sub-problem (~4-6 hours for each assignment; there are 4+1 assignments in total throughout the semester) for the entire class.\nResponsible for regrade requests after the grades are released (0-3 hours for each assignment; really depends on how many issues we may have).\nHelp with answer questions on Ed together with graduate TAs\nRequirements:\nHaving taken COS 484 and gotten an A- or better\nIdeally have prior experience as a UCA (in any course)\nStrong written communication skills (for grading)\nStrong oral communication and relational skills (for facilitating office hours)\nExternal Courses Jobs # Occasionally, the Department of Computer Science will hire UCAs for courses outside of the COS department. These positions are listed below, and may not recruit every semester. Please check the TigerUHR application for confirmation.\nEGR 154: Foundations of Engineering: Linear Systems # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Bernard Chazelle and Kritkorn Karntikoon (Spring 2024)\nTeam communication: Email\nDescription:\nUCAs, working under the direction of the instructor and head TA will do one of the following three tasks (based on their preference): helping craft homework problems, grading, and facilitating help sessions.\nResponsibilities (~3-5 hrs/week):\nUCAs work from the second week of classes to the last day of classes. UCAs will not have to work during midterm week, spring break, or after Dean\u0026rsquo;s Date.\nUCAs can work in person or entirely remotely depending on their preference.\nUCAs will work about 3 hours per week and not more than 5 hours.\nThere is a weekly 30-minute meeting via Zoom (based on everyone\u0026rsquo;s availability)\nUCAs can pick from among three different tasks depending on their preference:\nGrading, which happens remotely every Friday via Gradescope with a rubric provided by the head TA. Assignments are submitted on Thursday and we always return grades within 24 hours. UCAs will not be responsible for grading the midterm exam or final exam. Facilitating help sessions, which are on Monday and Wednesday from 4:30PM-7:30PM in COS 301. UCAs can help with all or part of one or both of these help sessions. Working with the head TA to create the homework, which must be done by each Wednesday, so we can post the assignment on Thursdays. Requirements:\nMust have taken EGR 154 and gotten an A, or have taken MAT 202/217 and having gotten a B+ or higher\nMust be reliable and consistent\nMust be communicative via email, and respond to emails within a few hours\nIW Seminar Jobs # The Department of Computer Science offers \u0026ldquo;IW seminars\u0026rdquo; for its majors, in which a faculty advises a group of 8-10 students each on their own project around a theme of the faculty\u0026rsquo;s choosing.\nGenerally, the faculty member is responsible for the overall theme of the seminar, and the UCA(s) is/are responsible for the logistics of the seminar. The UCA(s) is/are expected to be available to answer questions from students, to help students with their projects, and often to provide feedback during the group meeting time.\nThe meeting times as well as the specific themes of each seminars are updated every term on the IW seminar page of the Department of Computer Science.\n➡️ Please note that a UCA for a seminar is expected to be able to make the class meeting time for the seminar. It is your responsibility to check that you are available for the IW seminar for which you apply to be a UCA.\nProf. Ryan Adams # See academic website.\nTeam communication: Course Slack\nDescription:\nThis position is to provide support for students taking the IW seminar. UCAs will be expected to attend some of the weekly class meetings, hold office hours, and provide support for students on, e.g., Slack. The primary aim will be to offer guidance, conceptual help, and troubleshooting.\nResponsibilities (~5-6 hrs/week):\nAttend the weekly class meeting at a frequency jointly determined with the instructor.\nHold 2 hours of office hours a week, with extra before significant deadlines.\nBe responsive on Slack to issues raised by students in the class.\nRequirements:\nMust pass an interview, Must have previously completed an IW. Prof. Suma Bhat # See academic website.\nTeam communication: Course Slack\nDescription:\nThis position primarily assists students in the seminar course.\nA UCA attends (most of) the weekly seminars, listens to the students\u0026rsquo; project updates and holds office hours.\nResponsibilities (~3 hrs/week):\nAttend the weekly seminar (Spring 2023: Fridays 11AM-12:20PM) and listens to the students\u0026rsquo; project updates and action items\nHold office hours for ~3 hours/week for students to stop by around key deadlines (beginning of semester, midpoint checkpoint) and clarify conceptual questions and troubleshooting implementations\nRequirements:\nMust have been an UCA for an IW seminar or COS 333 Prof. Chistiane Fellbaum # See academic website.\nTeam communication: Email\nDescription: This position requires assisting seminar participants in conjunction with the instructor. The UCA should attend some of the weekly seminars, specific dates to be agreed upon with the instructor. The UCA is expected to familiarize themselves with the students’ projects and to hold office hours addressing the students’ questions.\nResponsibilities (Approximately 5-6 hours/week):\nAttend approximately half of the weekly seminar meeting (Fridays 11AM-12:20PM) , give feedback in class, and review the students’ project updates and action items presented there. Hold office hours for ~3 hours/week for students to stop by esp. around key deadlines (beginning and end of semester, midpoint checkpoint) and clarify conceptual questions, troubleshoot technical problems. Approximately 5-6 hours/week. There\u0026rsquo;ll be less in the middle of the semester and more at the beginning and the very end. Requirements:\nSome familiarity with NLP and ML. Prof. Felix Heide # See academic website.\nTeam communication: A course Slack\nDescription: This position supports training job running and bringup of the base IW codebase on research clusters.\nResponsibilities (Approximately 5 hours/week):\nAttend weekly sync up meetings.\nSupport in environment bringup and testing of base code structure for IW projects.\nAid in IW code architecture bringup.\nRequirements:\nMust have prior experience as a UCA (in any course), Must be COS majors, Strong communication skills. Prof. Robert Fish # See [academic website]( https://www.cs.princeton.edu/courses/archive/fall23/cosIW04/ https://www.cs.princeton.edu/courses/archive/spring24/cosIW03).\nTeam communication: Email\nDescription: This position provides near-peer support for students in IW seminar, particularly those who have never done an IW before. UCA should be available to come to the seminar and find out what projects the students are doing. They should also have some office hours at convenient times to work with students to overcome barriers to success, particularly programming issues.\nResponsibilities (Approximately 6-10 hours/week):\nCome to seminar Have office hours at convenient times and be flexible about meeting students Able to check a GitHub or similar repo Willing to help with programming issues Requirements:\nMust pass an interview, Should have completed an IW project before Prof. Xiaoyan Li # See academic website.\nTeam communication: Email\nDescription:\nThis position holds office hours to help answer students\u0026rsquo; questions on using ML packages or coding with Python. The UCAs are also expected to help organize students\u0026rsquo; project presentation in class and check their weekly progress.\nResponsibilities (~7 hrs/week):\nAttend weekly class meeting ~1.5h/week or 3h/week (Fall 2024: Wednesdays 11AM-12:20PM or 3:00PM-4:20PM)\nHold office hours 1h or 2h/week\nRead students\u0026rsquo; weekly progress report 2h or 3h/week\nRequirements:\nPassing an interview with Prof. Xiaoyan Li\nHaving completed an IW in machine learning or data science\nGood programming skills with Python\nGood verbal and written communication skills\nProf. Mae Milano # See academic website.\nTeam communication: Slack\nDescription:\nThis position supports the course infrastructure and assists students in using it.\nThe course infrastructure consists of virtual machines and services hosted by Amazon, Microsoft, and Google. The purpose of this course is to gain experience using and configuring distributed systems. Experience with kubernetes, S3, EC2, Azure, or any other cloud-hosted services and cloud providers will be helpful. TAs will ensure virtual services remain available, help configure them correctly for the course, and help students effectively use these resources.\nResponsibilities (~8 hrs/week):\nAttend weekly 30min/week sync-up meeting to check on status of course infrastructure and assign action items\nTake direct responsibility for a particular cloud service or vendor\nConfigure networking and services on virtual machines\nhold 2-4 hours / week of office hours for students attempting to use these services\ncommunicate availability and summarize expected progress with cloud-specific tasks\nmonitor course email and slack\nmonitor assigned cloud services\nRequirements:\nexperience using linux-based systems\ncomfort on the command line\nfamiliarity with at least one cloud service\nProf. Huacheng Yu # See academic website.\nTeam communication: Email\nDescription:\nUCAs participate in in-class discussions, give quick feedbacks to the student presentations in class and project proposal and mid-term reports, and hold office hours.\nResponsibilities (~3 hrs/week):\nAttend weekly class meetings (80 minutes)\nHold a 1-hr office hour every week\nAttend TA meetings before \u0026ldquo;grading\u0026rdquo; the proposal and mid-term report\nRequirements:\nMust be COS or ORFE/MAT majors\nMust have taken a COS 4xx (and gotten an A- or better) or a 5xx-level theory course\n"},{"id":2,"href":"/docs/applicants/choice/","title":"Rules for Choosing a Job","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"Every semester, the Department of Computer Science processes about over 500 applications, for more than 250 positions (some UCAs work in several positions). We are very grateful for the interest in our courses, and we are committed to providing a fair and transparent process for all applicants.\nOur promise to you is to ensure that our process is free from bias and provides every student an opportunity to work in an interesting, résumé-building job, as expected of us by the official guidance set forth by the Office of the Dean of the College.\nLifecycle of a UCA Application # How to decide which jobs to apply to # Every job listed on TigerUHR should have a corresponding sub-section in our UCA job catalog.\nFor every job, the catalog provides you with:\nA link to the course, in which you will be able to see the course description.\nThe description of the job, which will provide you an overview of how the job fits into the course.\nThe responsibilities of the job, are an itemized list of the specific tasks you will be asked to do, helping set your expectations.\nThe requirements of the job, are an itemized list of how likely you are to be hired, if you apply for this job.\nThis information is provided to help you make an informed decision about which jobs you would like to apply for.\nHow to express your preferences # When the applications open, you may go to TigerUHR\u0026rsquo;s registration page.\nFor each UCA job, you can indicate that STRONG, WEAK or NO interest.\nThere are a few rules to consider:\nStaffing the Intro COS Lab program is the highest priority, as it serves a very large population of non-major students, and support the introductory curriculum of the department (COS 126, 217, 226 and occasionally COS 109). For this reason, if you apply, are interviewed and offered a job of Intro Lab TA, it will override your preferences, you will be assigned to it and cannot turn it down; on the flip side, this means if you are unsure whether you might get a UCA job, applying to the Intro COS Lab increases your chances significantly.\nYou may be found suitable for multiple jobs, and you will be hired first in the highest priority jobs for which you have expressed a STRONG preference. If you turn down an offer for your highest priority job AND you had expressed a STRONG preference for this job, we will not offer you a position in another course and you will not be offered an UCA job for this campaign.\nYou may accept positions for multiple courses, up to your discretion. However it is very important that you do not turn down a job you have already accepted; failure to abide by these terms may result in a mark in your record.\nThese rules are intended to provide stability for the faculty and to ensure that our most important courses are properly staffed.\nWhen you are hired # Once you have been hired for a position, you will receive an email from the faculty supervisor for that position around the beginnin of the second week of the semester. (You can also log into TigerUHR to check the status of your application.)\nAfter that point, the responsibility will be to the faculty supervisor to follow up with you and get you on-boarded.\nIf you have been hired for a job, but have not been onboarded, please contact us.\nWhen you are not hired # If all positions have been filled, we will send out an email to all applicants who are not hired for any position for this term.\n"},{"id":3,"href":"/docs/timeline/","title":"TIMELINE FOR HIRING","section":"Docs","content":"This page contain details about the timeline. (Subject to change)\nFall 2024 campaign # August 19: TigerUHR open for UCA applications September 2: Deadline to apply for a COS UCA job September 9-14: Decisions for UCA hiring "},{"id":4,"href":"/posts/2022-12-02-recruiting-ucas-for-spring-2023/","title":"Recruiting UCAs for Fall 2024","section":"Announcements\u003cbr/\u003e\u003cbr/\u003e","content":"We are testing the new TigerUHR system which will be used to accept UCA applications for Fall 2024. All undergraduate students will receive an email from the department with the link and instructions for applicaition about two weeks before the start of the semester.\n"},{"id":5,"href":"/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/","title":"COS Lab Recruiting for Fall 2021","section":"Announcements\u003cbr/\u003e\u003cbr/\u003e","content":"Today we sent the following announcement to all COS undergraduate students, with broader diffusion of this message to follow:\nHello, and I hope your summer is going well!\nThe Department of Computer Science is hiring enrolled undergraduates (that\u0026rsquo;s you!) to assist in many of our COS courses as Undergraduate Course Assistants (UCAs). This is an opportunity to gain teaching experience, work with and get to know faculty, and contribute back to our undergraduate curriculum.\nEvery term, we hire undergraduates in two steps:\n— We first recruit applicants for the COS Lab TAs positions. These are the undergraduate-staffed office hours for the COS 126 and COS 226/217 courses where you will help current students with the programming assignments, and teach them how to debug. We are collecting applications starting now and until August 20th, 2021. This is to allow for the longer interviewing process involved with that position. If you are interested in a Lab TA position, please apply as soon as possible.\n— We will then hire applicants for general positions (grader, facilitator, office hours in other courses) starting August 20th, 2021, and until the term begins. Some positions are already open and you are free to start applying to them, others will be opened up at the end of next week.\nThe web form below will allow you to apply for these positions. You do NOT need to be a COS concentrator, but you must be a current Princeton undergraduate, and must have taken the classes corresponding to the position you are applying for.\nThe pay rate for all positions is $15.50/hour. More details are provided on the form. To apply, please fill out the form:\nhttps://www.tigeruhr.io/register/\nYou can apply to additional jobs after your first application. Note, you will need to submit a .PDF copy of your Degree Progress Report (available on TigerHub) in order to finalize the form.\nThe general deadline is August 20th at midnight. Julia Ruskin ‘22 will make lab TA hiring decisions in consultation with the department. Applications submitted after the deadline may not be considered.\nIf you have technical difficulties when filling out the form or have any other questions about the program, please contact the head lab TA, Julia Ruskin ‘22, at jruskin@princeton.edu.\nBest wishes,\nThe COS UCA Program Coordinators.\n"},{"id":6,"href":"/posts/2021-07-29-launch-of-site/","title":"Launching the New Site","section":"Announcements\u003cbr/\u003e\u003cbr/\u003e","content":"This is a website to document the valuable contribution that undergraduate students provide the teaching mission of Princeton University\u0026rsquo;s Deparment of Computer Science, and to provide information on this program.\nThe goal of the website will be, among other things, to help provide information to both prospective applicants and current students about the different roles and jobs fulfilled by Undergraduate Course Assistants.\nThe website is built using the Hugo static site generator, the Hugo Book theme, and is hosted on GitHub Pages.\n"},{"id":7,"href":"/docs/employees/payroll/","title":"Before Getting Paid\u0026hellip;","section":"For Current Employees","content":" Summary # Before being added to department payroll, you need to complete your tax paperwork (I-9 and W-2 forms) either at the Office of Student Employment, or online on JobX. This paperwork will only need to be filed once during your time at Princeton; for legal reasons, it can only be filed when you have a job offer.\nOnce your tax paperwork is filed, you can be added to the Department of Computer Science\u0026rsquo;s payroll, and start declaring hours using the TimesheetX platform.\nThe most common issue that new hires face is that they do not complete their tax paperwork, and they cannot be added to TimesheetX. The best person to contact for any issues having to do with payroll is Louis Riehl.\nOverview # Before getting paid by the Department of Computer Science, you need to be registered in two different places:\nYou need to be registered with the Student Employment Office to be added to University payroll: They will check your eligibility to work, and collect the necessary tax forms. This is a necessary step for any job on campus, but must only be done once during your time at Princeton.\nOnly once you are registered with the Student Employment Office, can you be added to the department\u0026rsquo;s time collection payroll. This is a step we will do for you, once you have filed your paperwork with the University and been hired in one of our jobs. Only when this step is complete are you allowed to begin work and declare your hours. If you have not completed the first step, our financial administrator will not be able to select you to be added to our payroll.\nOnce these steps have been completed, you will be ready to find out How to Declare Your Hours to get paid.\nYou will typically do Step 1 as soon as possible; if the current procedure outlined by the Student Employment Office, you should aim to take care of the paperwork in your first week on campus. Step 2 can be accomplished as needed as you are hired. Submitting the Student Employment Office Paperwork # Students who are not already on the payroll, can find instructions on the necessary forms to complete at this section of the Student Employment Office website. Since March 2020, the Student Employment Office has allowed these documents to be verified remotely, using video conference; it is unclear how long this practice will continue to be used. Previously, documents needed to be manually brought to the office for verification.\nAs part of your hiring, you will need to fill to U.S. federal tax forms:\nan I-9 form, the purpose of which is to verify that you are eligible to work under U.S. employment law. This will require you to show some documents to prove your identity and your authorization to work in the U.S.;\na W-4 form, the purpose of which is to determine how much the University must withhold from your paycheck to prepay federal taxes. This amount is an approximation of the taxes you might owe, usually an over-approximation which explains why consistently over 80% of U.S. tax-payers get a federal tax refund.\nGetting Added to the Department\u0026rsquo;s Payroll # You need to complete your Student Employment Office Paperwork as soon as possible ideally, before being hired by the department.\nYou have or will apply for a job with the department on TigerUHR. Once you have been hired into a job, you will be added to queue that will notify our financial assistant, Elizabeth Wang, to add you to the department payroll for the corresponding job.\nIf you have not filed the necessary paperwork, you will not be available to be added to the department\u0026rsquo;s payroll, and an email will be sent to you to let you know that you need to file paperwork before we can take further action.\nSample Hiring Confirmation Message # Once you have been hired, you will be typically receive an email from Louis Riehl outlining the most important aspects of declaring hours.\nThis is a sample message from February 2021:\nThis is to inform you that you have been added to the Payroll System as a XXXXXXXX in Computer Science.\nPlease go to https://princeton.studentemployment.ngwebsolutions.com/Cmx_Content.aspx?cpId=6 (“Student Employees” -\u0026gt; ”My Timesheets”) for instruction on how to enter your hours. If you have multiple roles at Princeton for which you are paid, please be sure to enter your hours associated with the correct role. For example, this includes if you are both a grader and a TA for Computer Science (we pay out these roles on different chart strings, and need an accurate accounting of each).\nPlease also note, if you do not enter your hours by the end of a pay period, you will not get paid on time! (Current period ends 2/21/2021.) Hours need to be entered by the Monday after every 2-week pay period in order to be logged in time for Payroll to process with regular paydays. Hours entered retroactively get paid as backpay, and are delayed. Please enter your hours by the end of every 2-week pay period!\nLet me know if you have any trouble entering your hours.\n"},{"id":8,"href":"/docs/general/staff/","title":"Current Staff","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":" TBD # "},{"id":9,"href":"/docs/employees/time-collection/","title":"How to Declare Your Hours","section":"For Current Employees","content":" Summary # Once you have been added to the department\u0026rsquo;s payroll, you can declare the hours that you work in the TimesheetX platform and get paid every few weeks. Overview: What are JobX and TimesheetX? # Princeton University uses JobX to advertise and solicit applications for most student employment jobs on campus (recruiting both undergraduate and graduate students). These jobs are typically hourly jobs, and student employees declare their hours on TimesheetX. Below is information on how to use the latter to declare your hours for COS jobs.\nFor most UCA jobs, the Department of Computer Science does its hiring through TigerUHR. However some jobs, in particular summer research internships, are advertised through JobX.\nYou cannot be added to the payroll for an hourly job until you have completed your official employment paperwork. Please make sure you follow all steps outlined in the Before Getting Paid page. How to Get Help # If you have any questions about getting added to payroll or declaring hours, you may contact Elizabeth Wang, who oversees the department\u0026rsquo;s payroll for Undergraduate Course Assistants.\nIf you belong to the UCA Slack, you can also ask her questions in the #payroll channel.\nOfficial Instructions # The Student Employees portal contains several useful resources, including:\nTutorial on JobX and TimesheetX: JobX is the platform on which you can search for a large number of student employment jobs on campus; TimesheetX is the platform on which you will declare your hours once hired.\nQuick Tips for Time Sheet Entry\nStep-by-Step Guide # Go to TigerHub.\nHours must be reported separately for each category of job (grader, facilitator, etc.) that you may be hired in. Begin by selecting a category in which to declare hours. This will process have to be repeated for other jobs.\nClick on \u0026ldquo;Start time sheet\u0026rdquo; on the most recent pay period.\nEnter every shift you worked. For each shift, click \u0026ldquo;Add a new entry.\u0026rdquo;\nEnter the details of the entry.\nOnce done entering all your hours for a given pay period, click \u0026ldquo;Submit Time Sheet.\u0026rdquo; Note: Only one time sheet can be submitted per period; and time sheets cannot be edited once submitted. For this reason, it is important to only submit at the end of pay period, once all entries have been submitted.\nReview the accuracy of your submission, before it is sent to our administrative coordinator and financial assistant.\nAnd confirm a second time.\nOnce your submission has been made, review the details of when we will have reviewed it, and when it will be transferred to Princeton\u0026rsquo;s financial department for disbursement to you.\n"},{"id":10,"href":"/docs/applicants/apply/","title":"How/When to Apply","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"The deparement will send all COS undergraduate students an email with instructions for UCA application about 2 weeks before the start of the semester.\nApplications are submitted on the TigerUHR registration page.\nTranscript Information # As part of the application process, TigerUHR will ask that you submit an up-to-date transcript. These documents can be obtained from TigerHub.\nInternal Transcript # Also acceptable: Degree Progress Report # "},{"id":11,"href":"/docs/general/past-ucas/","title":"Past Helpers","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":"This page lists past employees.\nPast Head Lab TAs # In chronological order, since 2013:\nAlex Daifotis Erica Portnoy and Utsarga Sikder Curtis Belmont Diana Liao Sally Jiao Benjamin G. Schiffer Justin Chang and Lily Zhang Julia Ruskin Diana Espindola and Austin Li Past Tool Builders # Vinay Ayyala \u0026lsquo;16 (codePost) Alex Daifotis \u0026lsquo;14 (LabQueueV1) James Evans \u0026lsquo;16 (codePost) Richard Freling \u0026lsquo;16 (codePost) Lance Goodridge ’17 *19 (TigerUHR and LabQueueV3) Aaron Lichtblau \u0026lsquo;22 (LabScheduler) Moin Mir \u0026lsquo;23 (subswap) Jeremy Dapaah \u0026lsquo;24 (QTrack) "},{"id":12,"href":"/docs/applicants/interview/","title":"Jobs that Require An Interview","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"Some jobs require an interview, currently this includes the following jobs:\nCOS 126 Lab TA COS 2xx Lab TA Because scheduling and giving interviews takes time, these jobs usually have an earlier deadline than most jobs.\nInformation about the COS Lab Interview Process # Julia Ruskin BSE \u0026lsquo;22, Head Lab TA in 2021, describes the interview process for the Intro COS Lab in the following way:\nWe interview to get a sense for how the candidates would act when interacting with students. Since we get so many more applicants than we can realistically hire, we need to differentiate between them, and assessing their ability to debug in real time along with their ability to explain concepts and their general helping manner is a much better way to differentiate than just looking at grades. [Currently,] we split the interviews between me and 4 other interviewers, two for 126 and two for 226/217,\nFirst, applicants apply on TigerUHR. Then, I reach out to all the applicants who meet the grades criteria (I don’t know what grade it corresponds to, but a 3/5 or higher on TigerUHR) to schedule interviews on a Calendly like. We split the interviews evenly between the interviewers and conduct them remotely, screensharing a code file with 3 bugs and having the candidate walk us through the code as if they were a TA. We use a predetermined rubric to assign a score to each candidate, and we also record comments about their approach and general helping manner. Then, we determine how many TAs we need to hire, and we hire the TAs with the highest scores.\nTAs can be hired for 226/217 or 126, either as full time (2 shifts/week), part time (1 shift/week), or subs. [\u0026hellip;]\nAs the Head TA, I am in charge of conducting interviews and hiring TAs, coordinating training for new TAs, creating the schedule, overseeing TA shadowing, and being the general point person for anything that comes up throughout the semester.\n"},{"id":13,"href":"/docs/general/contribute/","title":"How to Contribute to this Site","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":" How to Contribute to this Site # This site is hosted in a public GitHub repository. It uses the Hugo static site generator and the actual pages are written in Markdown (see cheat sheet here). It is published using GitHub Pages.\nAnybody with a GitHub account, can suggest changes to an existing page with only two or three clicks, like for Wikipedia. (Anybody can also propose new pages, but that requires a few more clicks.)\nIf you have made several contributions, you may be made a collaborator and you will be able to directly modify the site without requiring approval. (Since GitHub is a version control system, all changes are tracked and it is easy to undo specific changes, if they are later identified as malicious).\nBelow we outline how to suggest a change for any existing page on the website to get you started. This is a good opportunity to get to know GitHub and version control systems, which are really important tools.\nFirst Step: Click \u0026ldquo;Edit this page\u0026rdquo; # On any page of this site, including this one, you can find a link at the bottom, or bottom-right of the site, that is captioned Edit this page. The next step depends on whether you are a collaborator or not.\nHow to suggest a change if you are not a collaborator # If you are not a collaborator, you cannot push changes to the repository directly: You must first make fork to your repository. Fortunately GitHub both clearly indicates when this must happen, and transparently creates the fork for you such that this step of the process is completely transparent to you.\nYou can click \u0026ldquo;Fork this repository\u0026rdquo; and then follow the steps outlined starting in Step 2 of GitHub\u0026rsquo;s guide on Editing Files in Another User\u0026rsquo;s Repository.\nThank you in advance for your contribution! Depending on whether the semester is busy, your contribution will be reviewed soon. Once several of your contributions have been accepted, we will likely consider making you a collaborator!\nHow to suggest a change if you are a collaborator # If you are a collaborator, there is no need for a fork: You can edit files directly as though were the owner of the files. After clicking on Edit this page, you can follow the steps outlined starting in Step 2 of GitHub\u0026rsquo;s guide on Editing Files in Your Repository.\n"},{"id":14,"href":"/docs/employees/slack/","title":"The UCA Slack","section":"For Current Employees","content":"The Slack is where certain jobs coordinate.\nIt is available at https://princetoncosutas.slack.com/, with Princeton CAS login.\nThe rosters for this Slack are automatically synchronized based on TigerUHR\u0026rsquo;s rosters. You will automatically be placed in the appropriate channels.\n"}] \ No newline at end of file diff --git a/en.search-data.min.a16927a6613e3dfd0e9ef6da299e1cae1dee166a1347131bbfeb3165d28f4dd4.json b/en.search-data.min.a16927a6613e3dfd0e9ef6da299e1cae1dee166a1347131bbfeb3165d28f4dd4.json deleted file mode 100644 index 1ef7481..0000000 --- a/en.search-data.min.a16927a6613e3dfd0e9ef6da299e1cae1dee166a1347131bbfeb3165d28f4dd4.json +++ /dev/null @@ -1 +0,0 @@ -[{"id":0,"href":"/docs/general/contact/","title":"Contact Us / Report a Problem","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":"The Department of Computer Science runs a very large Undergraduate Course Assistant (UCA) program.\nUCAs provide support in a couple dozen of courses of the Department of Computer Science, they are one of the most prized resources of Princeton.\nBecause our program is so large, because we have such a diverse array of courses staffed with UCAs, the experience of being a UCA can have some variability.\nWe strive to meticulously follow the official guidance policy set forth by the Office of the Dean of the College, in consultation with the McGraw Center for Teaching and Learning.\n➡️ Please read this guidance to understand what are the expectations that the University places on the department and the faculty in the department, in terms of providing UCAs with proper oversight, management and support.\nIf you have any question, concern, feedback about any part of the process, please email the COS UCA hiring coordinators (Xiaoyan Li: xiaoyan@cs.princeton.edu, and Christopher Moretti: cmoretti@cs.princeton.edu).\n"},{"id":1,"href":"/docs/applicants/jobs/","title":"COS UCA Job Catalog","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"This page provides a general description of the responsibilities of all the jobs that are available to UCAs in Princeton University\u0026rsquo;s Department of Computer Science. It also provides a description of the different job categories.\nGeneral Job Categories # The department employs undergraduates to assist with many COS courses. The jobs are divided into three categories (most paid $18/hr):\nLab TAs who help students in undergraduate-staffed office hours Graders who grade assignments and (in some courses) exams In-class TAs who help students in the classroom (these positions are called facilitators or precept assistants) Some Independent Work (IW) seminars also hires 1-2 UCAs to do a combination of all three jobs (assisting in class to provide feedback to student presenting their projects, grading projects, and providing office hours for students to get help with their projects).\nFinally, some courses also hire a higher-level position (paid $21/hr):\nManagers who coordinate and supervise the work of other UCAs (typically managers have already worked in the course in a previous semester) Specific Job Categories # In addition to the general jobs, there are some specific jobs.\nFor instance, the Intro COS Lab (which centralizes the undergraduate-staffed office hours for COS 109, 126, 217, and 226) hires a Head Intro Lab TA or Team. The Intro COS Lab also hires a team of Interviewers, who interview prospective Intro Lab TAs.\nSeveral courses may hire UCAs on an ad-hoc basis to help with course development or tool building.\nJobs # Below is a description of all the jobs that are available, with a description of their responsibilities.\nThese jobs are not always hiring every semester, so please check TigerUHR directly for the list of jobs currently hiring.\nIntro COS Lab TA Program # Supervised by UCA hiring coordinators and the Head Lab TA Team.\nTeam communication: Slack ( central COS UCA Slack: #lab-announcements, #126-lab, #2xx-lab)\nThe Intro COS Lab, currently in Lewis 121 and 122, is a place where students taking introductory courses can go for help in debugging their programs. The Intro Lab TAs are those glorious individuals working on the front lines, providing that help. The lab is available to students taking COS 109, COS 126, 217, and 226. The Intro Lab TAs are coordinated by the Head Intro Lab TA (possibly with an Assistant), who is an undergraduate. Most of the shifts are on evenings or weekends, and they last 2 hours. Typically, a TA either has two shifts per week, or is a substitute TA.\nFor more information about the job, the conditions for applying, and the pay rate, please see this page about becoming an Intro Lab TA job.\nThe Intro COS Lab uses the LabQueue to manage the queue of students waiting for help.\nRead specific information about the job responsibilities for:\nthe Intro Lab TA job (which requires an interview if you are a first-time Intro Lab TA) the Interviewers job (apply directly by contacting the Head Intro Lab TA) the Head Intro Lab TA job COS 109: Computers in Our World # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Brian Kernighan (Fall 2023)\nTeam communication: Email\nDescription:\nAssist students in understanding problem sets and completing labs\nResponsibilities (6-8 hours/week):\nAssist in the scoring of 5 assignments spread out over the term\nAssist in the scoring of lecture or guest speaker reflections or book reports\nRequirements:\nMust have taken the class and gotten B+ (by default), Must have prior experience as a UCA (in this course), Must be COS majors, Must be specific applicant(s) that have contacted Prof. Brian Kernighan COS 126: Computer Science: An Interdisciplinary Approach # For description and past ratings, see course page on Princeton Courses\nGrader position # Supervised by Prof. Sebastian Caldas (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #126-grading)\nDescription:\nThis position grades the programming assignments and programming exams, in Java.\nGraders work through codePost to provide high-quality and supportive feedback to introductory CS students. A detailed rubric is included. The work consists of reading and understanding the student\u0026rsquo;s code, and providing feedback on the code\u0026rsquo;s correctness, efficiency and clarity.\nResponsibilities (~4-5 hrs/week):\nAttend weekly grader meeting (2-3h/week) to review the rubric and start grading synchronously. Grade late and remaining assignments asynchronously (~1h/week).\nRequirements:\nHaving taken COS 126 (B+ or better typically) Strong empathetic skills\nGood written communication skills\nPrecept Assistant position # Supervised by Prof. Sebastian Caldas (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #126-precept-assistants)\nDescription:\nPrecept assistants are responsible for helping students understand the solutions to a set of active learning exercises during precept (e.g., Java programming exercises, worksheets). You will work alongside a graduate student or faculty preceptor to help students work on these exercises and will answer questions regarding the course material.\nA great precept assistant is enthusiastic and patient. They can connect with a wide variety of students, encouraging them to ask questions while explaining the course material in a variety of ways.\nA precept assistant may also be hired as a grader or as a COS Lab TA.\nResponsibilities (~2-4 hrs/week) :\nPrepare by reviewing upcoming precept exercises before class (1h/week)\nAttend two precepts per week and answer students’ questions (2-3h/week)\nWork under the direction of a preceptor\nRequirements:\nHaving taken COS 126\nBeing able to communicate effectively with a diverse group of students\nSchedules (updated for Spring 2023):\nBefore applying to this position, please confirm you are available for one of the scheduled precepts for COS 126, which you can find here.\nCOS 217: Introduction to Programming Systems # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Christopher Moretti (Fall 2024)\nTeam communication: Slack ( central COS UCA Slack: #217-grading)\nDescription:\nThe COS 217 grader evaluates COS 217 assignment transcripts and code to grade and provide high-quality, supportive feedback on students\u0026rsquo; submissions. Grading is done via codePost using primarily pre-defined rubric notes and deductions.\nResponsibilities (~6-10 hours/week):\nAttend weekly grader meeting ~1 hour per week (Spring 2024: likely to be Thursdays 5:00-~6:00pm). During weeks an assignment is due, this meeting will refresh your memory of that assignment, describe common errors, and review the rubric and codePost items to prepare for grading. During weeks between assignment due dates, this meeting will serve as a grading session to do some synchronous grading and get questions answered.\nGrade 8-15 submissions asynchronously. Typically this accounts for 4-8 hours per week, though some assignments may grade faster or slower than others.\nRequirements:\nHaving taken COS 217 and earned an A- or better. (Lower grades will be considered on a case-by-case basis.) COS 226: Algorithms and Data Structures # For description and past ratings, see course page on Princeton Courses\nGrader position # Supervised by Prof. Pedro Paredes (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #226-grading)\nThis position grades the programming assignments in Java, which happen about once every two weeks. It involves reading complex code, with the need to understand errors in the running time or memory efficiency of the code.\nResponsibilities (~4-6 hrs/assignment) :\nAttend weekly grader meeting (2-3h/assignment) to review the rubric and start grading synchronously.\nGrade late and remaining assignments asynchronously (~2-3h/assignment).\nRequirements:\nFor Freshman/Sophomores: Having taken COS 226 (B+ or better typically)\nFor Juniors: Grading experience in any course (or being a lab TA)\nFor Seniors: Grading experience in COS 226\nGrading Manager position # Supervised by Prof. Pedro Paredes (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #226-grading)\nDescription:\nThis position is for students that are interested in contributing to improve the class and can involve multiple things depending on your interests (see responsibilities below for examples), some of which don\u0026rsquo;t necessarily involve grading (despite the title name).\nGrading managers will work closely with Prof. Paredes\nResponsibilities (time commitment variable):\nFor students interested in grading it can be any of the following:\nSupervising the COS 226 graders (e.g. answering their questions, grading tougher submissions). Creating new materials to support the grading mission (such as the style guide, automation scripts, preparing grading briefs). Audit a subset of submissions to ensure quality of grading. For students interested in interacting with other students, responsibilities might include holding office hours, assisting in precepts and attending staff meetings with the course instructors and graduate preceptors.\nFor students interested in creating new material for the course, responsibilities might include revising assignment statements, revising precept handouts, beta testing new assignments, creating supplemental material.\nRequirements:\nHaving been a COS 226 grader for at least one semester\nA vision on what can be done to do to improve COS 226\nCandidates will be asked a few questions about what they are interested in doing for the course as well as their past experience with the course\nCOS 240: Reasoning About Computation # For description and past ratings, see course page on Princeton Courses\nGrader position # Supervised by Prof. Iasonas Petras (Spring 2024)\nTeam communication: Email\nDescription:\nThe COS 240 grader grades COS 240 students\u0026rsquo; work and provides feedback.\nResponsibilities:\nGrade (asynchronously) students\u0026rsquo; work and provide feedback for ~5-7 hours a week (on weeks when grading takes place, which is more or less every 2 weeks).\nAttend (and participate in) grading consistency meetings (most likely online) taking place on Thursdays 4:30PM-5:30PM\nAttend (and participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM\nMeet grading deadlines consistently\nRequirements:\nHaving taken COS 240 and performed well\nMust have satisfactorily answered the supplemental survey\nLab TA position # Supervised by Prof. Iasonas Petras (Spring 2024)\nDescription:\nThe COS 240 Lab TA holds office hours where COS 240 students can ask questions on and discuss the course material and the course\u0026rsquo;s assignments. \u0026quot;\nResponsibilities (~6 hrs/week):\nHold 4 hours of office hours per week.\nAttend (and participate in) weekly status meetings (most likely online) taking place on Fridays 3:30PM-5:00PM\nRequirements:\nHaving taken COS 240 and performed well\nMust have satisfactorily answered the supplemental survey\nCOS 302: Mathematics for Numerical Computing and Machine Learning # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Ryan Adams (Fall 2023)\nTeam communication: a course staff Slack channel\nDescription: This position grades assignments and exams. In both cases, submissions will be done through Gradescope. Generally there are two kinds of problems on the assignments: conceptual math problems, and practical work in Python. The Python is submitted as a colab notebook. Graders are expected to provide helpful and fair feedback that encourages understanding.\nResponsibilities (~5 hrs/week:)\nGraders are expected to be reasonably responsive after assignment submission in order to determine who will grade what problems and to ask for help as necessary. My goal is to provide grades and feedback within a week. Requirements:\nFamiliarity with the material COS 324: Introduction to Machine Learning # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Sanjeev Arora and Prof. Elad Hazan (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #324-uca)\nDescription:\nThis position is a joint grader and office hour position.\nFor grading, you will be part of the team that grades our weekly assignments, which typically alternate between a written homework (i.e. pen-and-paper pset) and a programming assignment (i.e. IPython notebook). Typically, you will grade one problem or sub-problem most weeks according to a rubric as well as handle regrade requests for your problem. Depending on the number of UCAs on the course, you may not be assigned grading every week (though you should be prepared to grade each week).\nFor office hours, you will host a weekly 2-hour office hours (either in-person or virtual, we try to offer roughly 50%-50% options) primarily for helping students get unstuck on our weekly assignments. Office hours will also provide prep support before our midterm and final.\nResponsibilities (~5-10 hrs/week, depending on whether you\u0026rsquo;re assigned grading in a given week):\nAttend and actively participate in 1-hour staff meeting each week (Mon 4:30-5:30pm for Fall 2023, most weeks on Zoom, ~1/month in-person)\nPrep for hosting office hours each week (i.e. do assignment yourself, ~2 hours/week)\nHost 2-hour office hour block each week\nGrade asynchronously one problem or sub-problem (~3-5 hours/most weeks) for the entire class (weekly grading period starts Saturday and is due Tuesdays EOD for Fall 2023)\nRequirements:\nHaving taken COS 324 and received a B+ or better\nStrong written communication skills (for grading)\nStrong oral communication and relational skills (for facilitating office hours)\nPreferred:\nPrior experience as a UCA (in any course) COS 326: Functional Programming # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Andrew Appel (Fall 2023)\nTeam communication: a course Slack\nDescription: The \u0026ldquo;COS 326 UCA\u0026rdquo; position includes grading homeworks, holding in-person office hours (typically focused on homeworks), and answering questions on Ed.\nResponsibilities (~6 hrs/week:)\nYou should regularly monitor the COS326 slack where the course staff (including UCAs) will communicate.\nGrading is asynchronous and on-line; there are 7 homeworks and for each one theres a 2-3 day window in which it ought to be graded. Since you\u0026rsquo;ve taken the course, you have a pretty clear idea what those homeworks are.\nIf you are assigned certain days/times to cover Ed, you should monitor Ed from time do time during those hours.\nIf you are assigned in-person office hours, you should be there and be helpful.\nRequirements:\nMust have taken the class and gotten B+ (by default), Must pass an interview COS 333: Advanced Programming Techniques # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Bob Dondero (Spring 2023)\nTeam communication: Email, and staff mailing list cos333instructors@lists.cs.princeton.edu\nDescription:\nA COS 333 UCA works with a graduate student TA to grade some semester-long projects.\nResponsibilities:\nThese responsibilities refer to \u0026ldquo;Reading Period\u0026rdquo; and \u0026ldquo;Dean\u0026rsquo;s Date\u0026rdquo; as defined in the Registrar\u0026rsquo;s Office\u0026rsquo;s academic calendar.\nEach UCA will participate in a ~2 hour Zoom pre-grading meeting with the lead instructor and graduate student TAs. During that meeting they will discuss the project grading rubrics. That meeting will occur sometime during Reading Period.\nAfter Dean\u0026rsquo;s Date each UCA will grade 4-to-6 projects, approximately one per day. Some slippage of that schedule will be fine. The grading will be mostly asynchronous, but could involve some synchronous interaction with the members of the teams whose projects are being graded. An UCA will devote ~5 hours to grading each project.\nFinally, each UCA will participate in a final ~4 hour Zoom meeting with the lead instructor and graduate student TAs. During that meeting they will finalize the project grades. That meeting will occur shortly before the day when course letter grades are due at the Registrar\u0026rsquo;s Office.\nRequirements:\nHaving taken COS 333 and gotten an A- or better COS 343: Algorithms for Computational Biology # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Ben Raphael (Spring 2023)\nTeam communication: Slack ( central COS UCA Slack: #343-grading)\nDescription:\nThe primary responsibility of this position is to grade 5 homework assignments, midterm, and final exam. HW assignments consist of written exercises and short programming exercises. The written exercises are graded for correctness and clarity using a detailed rubric that will be provided. Programming exercises are graded for correctness, but not for quality of code.\nUCAs who are interested in other tasks such as helping answer questions on Ed, holding office hours to answer student questions, or contributing to the development/debugging of new assignments are welcome to do so, and will be paid for time spent on these activities.\nResponsibilities (~ 5-8 hrs/week):\nAttend bi-weekly in-person staff meeting (\u0026lt;1hr)\nConsistently meet grading deadlines\nRequirements:\nMust be COS or ORFE/MAT majors (other majors acceptable with relevant experience)\nMust have taken COS 226 with a grade of B+ or better\nMust be interested in course topics (computational biology)\nPSY/COS 360: Computational Models of Cognition # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Tom Griffiths (Fall 2023)\nTeam communication: a course Slack\nDescription: This position is for a grader who will help with grading of problem sets involving programming problems and written answers. The programming problems are in Python. An auto-grader will be used, and you will interpret ambiguous cases flagged by the auto-grader and provide feedback on the code. You will also help to test problem sets and develop questions.\nResponsibilities (~10 hrs/week:)\nAttend weekly meeting (1 h/week) to coordinate on grading and course goals for the week Read rubric for grading assigned problems Test solve assigned homework problems Grade asynchronously for about 6-8h/week, flexible timing Requirements:\nMust pass an interview, Prefer students with experience in ML, e.g. COS 324 COS 375: Computer Architecture and Organization # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. David August (Fall 2023)\nTeam communication: a course Slack\nDescription: This position involves helping students with the course and grading the programming assignments.\nResponsibilities (Flexible 4~10 hrs/week:)\nOnce a week office hours or on request, and grade a few times over the semester. Requirements:\nMust have taken the class and gotten B+ (by default), Strong performance having taken COS/ECE375. Must pass an interview COS 418 Distributed Systems # For description and past ratings, see course page on Princeton Courses.\nSupervised by Supervised by Prof. Michael J. Freedman and Wyatt Lloyd (Spring 2024)\nTeam communication: a course Slack\nDescription: As a LabTA for COS 418 you will provide students with support working on our challenging programming assignments.\nResponsibilities (~5.25 hrs/week:)\n4 hours of office hours per week, typically in 2 separate 2-hour chunks 1 hour of answering questions on EdStem per week (in a defined 1-hour window) course staff meeting to initially discuss responsibilities and later to discuss office hours for 1 hour roughly once a month Requirements:\nMust have taken the class and gotten B+ (by default) COS 423 Theory of Algorithms # For description and past ratings, see course page on Princeton Courses.\nSupervised by Supervised by Prof. Robert Tarjan (Spring 2024)\nTeam communication: TBA\nDescription: In this course, UTAs help students complete their coursework. They hold office hours, help in precept, answer questions on Ed, and participate in the grading team. .\nResponsibilities (10 hrs/week:)\nAttend a weekly staff meeting to plan the week. Solve this year\u0026rsquo;s version of the assignments, which will differ a bit from those of previous years. Hold office hours. Help answer questions on Ed. Help the grading team. Requirements:\nMust have taken the class and gotten B+ (by default), Must pass an interview COS 426 Computer Graphics # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Adam Finkelstein (Fall 2023)\nTeam communication: centralized Slack if available\nDescription: In this course, UTAs help students complete their coursework. They hold office hours, help in precept, answer questions on Ed, and participate in the grading team. .\nResponsibilities (10 hrs/week:)\nAttend a weekly staff meeting to plan the week. Solve this year\u0026rsquo;s version of the assignments, which will differ a bit from those of previous years. Hold office hours. Help answer questions on Ed. Help the grading team. Requirements:\nMust have taken the class and gotten B+ (by default), Must pass an interview COS 429: Computer Vision # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Felix Heide and Prof. Vikram Ramaswamy (Spring 2024)\nTeam communication: a course Slack\nDescription:\nWe are looking for students with strong background in computer vision to help in this next iteration of the course.\nAll UCAs will be expected to assist with grading of assignments and exams.\nBeyond that, we would welcome help with:\nUCA-run office hours\nUCA support to help guide the final projects\nUCA support with debugging any new assignments\nUCA support with grading the poster session and/or the final project reports\nUCA support with the two exam review sessions\nResponsibilities (~5-10 hrs/week, depending on whether there is grading in a given week):\nThere are 4 assignments and 2 exams. These will be due approximately every 2 weeks and need to be graded within a week. UCAs will be expected to be available to turn the grading around within about 5 days, and to work closely with the grad TA responsible for each assignment.\nRequirements:\nHaving taken COS 429 and gotten an A- or better COS 433: Cryptography # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Zeev Dvir (Spring 2023)\nTeam communication: Email\nDescription:\nThe position is for helping grade problem sets (about one Pset every other week). In addition, if the applicant is interested, they can also hold weekly office hours for additional pay.\nResponsibilities (~6-10 hrs/week):\nAttend grading meetings (about once in two weeks) to agree on grading rubrics.\nGrade about one problem in each Pset (for all ~60-70 students of the course in Spring 2023) on Gradescope. There will be about 4-5 Psets in the semester.\nRequirements:\nHaving a strong mathematical background. COS 435: Introduction to Reinforcement Learning # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Benjamin Eyesenbach and Prof. Mengdi Wang (Spring 2024)\nTeam communication: A course Slack\nDescription:\nThis position grades written and coding assignments. The coding assignments will be written in Python + PyTorch. You will work together with the graduate TAs to come up with a rubric for grading each problem. If time permits and if interested, you\u0026rsquo;re welcome to also help out in writing and testing assignments\nResponsibilities (10 hrs/week):\nWe aim to have all assignments graded within 24 hrs of submission. This means that you\u0026rsquo;ll have to block out some hours in the day after the submission for grading. Clear communication (i.e., staying on top of Slack messages from the rest of the course staff, letting us know if you\u0026rsquo;re unable to grade for some week) You won\u0026rsquo;t be expected to join the weekly staff meetings (though are welcome to if interested). Requirements:\nAn \u0026ldquo;A\u0026rdquo; in COS 324 (or equivalent). Some experience with RL. COS 445: Economics and Computation # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Matt Weinberg and Dr. Marcel Dall\u0026rsquo;Agnol (Spring 2024)\nTeam communication: Email + a course Slack\nDescription:\nUCAs for COS 445 are primarily responsible for grading (PSets, midterm, and final). That is, every UCA must grade assignments, and it is common for most UCAs to only grade assignments.\nUCAs who are interested in other tasks (such as helping answer questions on Ed, providing advice on course policy, etc.) are definitely welcome to do so (and be paid to do so, and appreciated for doing so), but the primary need is grading.\nAdditionally 1-3 UCAs can instead volunteer to be the \u0026ldquo;Strategy Design Czar(s)\u0026rdquo;. The Strategy Design Czars do not grade assignments, but are responsible for maintaining the codebase for strategy design assignments. This role requires significant independence in comparison to grading, but would be fun for students who enjoyed the strategy designs more than the PSets. If you are interested in this, you should email Matt ( smweinberg@princeton.edu) and Marcel ( dallagnol@cs.princeton.edu) to discuss.\nResponsibilities (~3-4 hrs/week):\nAttend weekly in-person meeting Thursdays 4:30PM-5:30PM. These meetings will tee up grading for the most recently submitted assignment, and we will ask you to stay for the entire hour to grade assignments with other course staff in the room.\nNote:\nWe will always be as efficient as possible with these meetings (e.g. we won\u0026rsquo;t force you to show up if you\u0026rsquo;ve already finished grading). However, we do ask that you think of in-person attendance every week as the default, and block this time off on your calendar.\nMany weeks, Matt and/or Marcel will take a subset of interested staff out for bubble tea at 5:30PM.\nGrade asynchronously ~6 hours every 2 weeks. PSets are due every other Monday. Grading tees off on Thursday, and is due 10 days later on Monday. Because the next cycle starts soon after, we do need to be sticklers about deadlines.\nBe available for ~6-8 hours (total) of grading the final on May 16/17 (the two days right after the university take-home final deadline). If you\u0026rsquo;re on-campus, we\u0026rsquo;ll ask that you grade in-person (and provide food/bubble tea). If you\u0026rsquo;re off-campus (which is completely fine), we\u0026rsquo;ll ask that you grade remotely. If your travel plans prevent you from grading (even remotely) during this period, please let Matt/Marcel know this in advance (but you do not need to change your travel plans to be available).\nThere will be no staff meeting during Spring Break, and it is entirely feasible to complete your responsibilities without working at all over Spring Break. However, some UCAs prefer to grade the midterm over Spring Break, and we will have an optional remote tee-off meeting for those who want to do so.\nBe prepared to give actual feedback on written PSet submissions to help students improve. We will try our best to make this as efficient as possible, but you should be prepared that any assignment that doesn\u0026rsquo;t receive full credit does typically require you to write something specific to that submission (copy/pasting comments across solutions historically leads to confusion by the students and results in appeals that we have to resolve anyway).\n[For Strategy Design Czars only] There is a codebase for strategy designs on github that, afaik, is complete, bug-free, etc. However, every SD still requires an initialization (TigerFile submission needs to be set up for every SD, sample files need to be uploaded for students, files need to be downloaded from TigerFile), and a run (some submissions have bugs and will crash the execution, you\u0026rsquo;ll need to figure out which ones and edit/remove them, etc.). You will also be responsible for answering any questions about the coding portion of the SDs (because Matt/Marcel may not know the answer). This requires more independence than a typical UCA role, because this has always been designed/maintained by UCAs (there is a detailed SD czar onboarding document, and previous years\u0026rsquo; czars are often happy to answer quick questions).\n[For Strategy Design Czars only] You are free to do more interesting things with the SD codebase, if that interests you. For example, you are free to add more \u0026lsquo;check submitted files\u0026rsquo; test cases so that there\u0026rsquo;s fewer buggy submissions, write more efficient code, write new \u0026lsquo;staff solutions\u0026rsquo;, or develop any new infrastructure that you think would be beneficial. But this is entirely optional\u0026ndash;your \u0026lsquo;responsibility\u0026rsquo; is just to make sure that SD files are uploaded in a timely fashion, and grades are computed in a timely fashion as well.\nRequirements:\nMust have taken COS 445 and gotten an A- or better. (If you have taken COS 445 and are interested in being a UCA, but did not earn an A- or better, feel free to reach out to Matt and/or Marcel to discuss).\nMust be available for a weekly 4:30PM-5:30PM staff meeting on Thursdays, in-person.\nIf you apply for this position, we will assume that you\u0026rsquo;ll block off every Thursday 4:30PM-5:30PM for an in-person meeting. Exceptions are possible (and we understand there will be sporadic absences), but you should email Matt ( smweinberg@princeton.edu) and Marcel ( dallagnol@cs.princeton.edu) with your situation before applying for this position.\nCOS 448: Innovating Across Technology, Business, and Marketplaces # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Robert Fish (Fall 2023)\nTeam communication: centralized Slack (TBD)\nDescription: Students will assist the class AI’s in scoring assignments and speaker reflections based on a rubric. They will also be able to attend class and listen to the lectures and guest speakers in this new and highly sought-after class. .\nResponsibilities (6~10 hrs/week:)\nAssist in the scoring of 5 assignments spread out over the term\nAssist in the scoring of lecture or guest speaker reflections or book reports\nRequirements:\nMust be interested in the course subject matter\nGood written communication analysis skills, must be better than ChatGPT.\nAny applicant will be interviewed by the course staff prior to hire and we would like to see a writing sample.\nCOS 461: Computer Networks # For description and past ratings, see course page on Princeton Courses\nSupervised by Prof. Kyle Jamieson (Spring 2023)\nTeam communication: Course Slack\nDescription:\nThis position supports and grades the programming assignments for COS 461 (see https://github.com/kyleatprinceton/COS461-Public), supports precept content development, and other miscellaneous course duties.\nResponsibilities (~2-10 hrs/week):\nAttend weekly grading meetings\nHold supplemental office hours before programming assignment deadlines\nHold supplemental office hours before exams\nRequirements:\nHaving taken COS 461 and gotten an B+ or better COS 471: Blockchains, Decentralized Trust, and Their Applications # Supervised by Prof. Rob Fish and Prof. J. P. Singh (Spring 2024)\nTeam communication: Slack ( central COS UCA Slack: #471-uca)\nDescription:\nStudents will assist the class AI\u0026rsquo;s in scoring programming assignments and speaker assignments based on a rubric. They will also be able to attend class and listen to the lectures and distinguished guest speakers in this class.\nResponsibilities (~6-10 hrs/week):\nAssist in the scoring of 2-3 programming assignments\nAssist in the scoring of lecture or guest speaker-based assignments\nAssist in the scoring of projects\nRequirements:\nMust be interested in the course subject matter\nGood written communication analysis skills, must be better than ChatGPT.\nAny applicant will be interviewed by the course staff prior to hire\nCOS 484: Natural Language Processing # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Karthik Narasimhan (Spring 2024)\nTeam communication: Course Slack\nDescription:\nThis position is a joint grader and office hour position.\nFor grading, you will be part of the team that grades our assignments: there are 4 + 1 assignments throughout the semester (including one warm-up), and each assignment has a written component, and a programming component based on Colab. Typically, you will grade one problem (or part of a problem) a week according to a rubric.\nFor office hours, you will host a weekly 1-hour office hours primarily for helping studying get unstuck on our assignments, or provide prep support before midterm, or provide guidance on their final project.\nResponsibilities (~4-8 hrs/week, depending on whether there is grading in a given week):\nAttend and actively participate in 30-min staff meeting each week (Thursday 4:30-5pm in COS 401)\nPrep for hosting office hours each week (0.5~2 hours; this really depends on your familiarity of the course materials. For the weeks that have an assignment due, you are expected to do the assignment yourself and it will take longer)\nHost 1-hour office hour block each week\nGrade asynchronously one problem/sub-problem (~4-6 hours for each assignment; there are 4+1 assignments in total throughout the semester) for the entire class.\nResponsible for regrade requests after the grades are released (0-3 hours for each assignment; really depends on how many issues we may have).\nHelp with answer questions on Ed together with graduate TAs\nRequirements:\nHaving taken COS 484 and gotten an A- or better\nIdeally have prior experience as a UCA (in any course)\nStrong written communication skills (for grading)\nStrong oral communication and relational skills (for facilitating office hours)\nExternal Courses Jobs # Occasionally, the Department of Computer Science will hire UCAs for courses outside of the COS department. These positions are listed below, and may not recruit every semester. Please check the TigerUHR application for confirmation.\nEGR 154: Foundations of Engineering: Linear Systems # For description and past ratings, see course page on Princeton Courses.\nSupervised by Prof. Bernard Chazelle and Kritkorn Karntikoon (Spring 2024)\nTeam communication: Email\nDescription:\nUCAs, working under the direction of the instructor and head TA will do one of the following three tasks (based on their preference): helping craft homework problems, grading, and facilitating help sessions.\nResponsibilities (~3-5 hrs/week):\nUCAs work from the second week of classes to the last day of classes. UCAs will not have to work during midterm week, spring break, or after Dean\u0026rsquo;s Date.\nUCAs can work in person or entirely remotely depending on their preference.\nUCAs will work about 3 hours per week and not more than 5 hours.\nThere is a weekly 30-minute meeting via Zoom (based on everyone\u0026rsquo;s availability)\nUCAs can pick from among three different tasks depending on their preference:\nGrading, which happens remotely every Friday via Gradescope with a rubric provided by the head TA. Assignments are submitted on Thursday and we always return grades within 24 hours. UCAs will not be responsible for grading the midterm exam or final exam. Facilitating help sessions, which are on Monday and Wednesday from 4:30PM-7:30PM in COS 301. UCAs can help with all or part of one or both of these help sessions. Working with the head TA to create the homework, which must be done by each Wednesday, so we can post the assignment on Thursdays. Requirements:\nMust have taken EGR 154 and gotten an A, or have taken MAT 202/217 and having gotten a B+ or higher\nMust be reliable and consistent\nMust be communicative via email, and respond to emails within a few hours\nIW Seminar Jobs # The Department of Computer Science offers \u0026ldquo;IW seminars\u0026rdquo; for its majors, in which a faculty advises a group of 8-10 students each on their own project around a theme of the faculty\u0026rsquo;s choosing.\nGenerally, the faculty member is responsible for the overall theme of the seminar, and the UCA(s) is/are responsible for the logistics of the seminar. The UCA(s) is/are expected to be available to answer questions from students, to help students with their projects, and often to provide feedback during the group meeting time.\nThe meeting times as well as the specific themes of each seminars are updated every term on the IW seminar page of the Department of Computer Science.\n➡️ Please note that a UCA for a seminar is expected to be able to make the class meeting time for the seminar. It is your responsibility to check that you are available for the IW seminar for which you apply to be a UCA.\nProf. Ryan Adams # See academic website.\nTeam communication: Course Slack\nDescription:\nThis position is to provide support for students taking the IW seminar. UCAs will be expected to attend some of the weekly class meetings, hold office hours, and provide support for students on, e.g., Slack. The primary aim will be to offer guidance, conceptual help, and troubleshooting.\nResponsibilities (~5-6 hrs/week):\nAttend the weekly class meeting at a frequency jointly determined with the instructor.\nHold 2 hours of office hours a week, with extra before significant deadlines.\nBe responsive on Slack to issues raised by students in the class.\nRequirements:\nMust pass an interview, Must have previously completed an IW. Prof. Suma Bhat # See academic website.\nTeam communication: Course Slack\nDescription:\nThis position primarily assists students in the seminar course.\nA UCA attends (most of) the weekly seminars, listens to the students\u0026rsquo; project updates and holds office hours.\nResponsibilities (~3 hrs/week):\nAttend the weekly seminar (Spring 2023: Fridays 11AM-12:20PM) and listens to the students\u0026rsquo; project updates and action items\nHold office hours for ~3 hours/week for students to stop by around key deadlines (beginning of semester, midpoint checkpoint) and clarify conceptual questions and troubleshooting implementations\nRequirements:\nMust have been an UCA for an IW seminar or COS 333 Prof. Chistiane Fellbaum # See academic website.\nTeam communication: Email\nDescription: This position requires assisting seminar participants in conjunction with the instructor. The UCA should attend some of the weekly seminars, specific dates to be agreed upon with the instructor. The UCA is expected to familiarize themselves with the students’ projects and to hold office hours addressing the students’ questions.\nResponsibilities (Approximately 5-6 hours/week):\nAttend approximately half of the weekly seminar meeting (Fridays 11AM-12:20PM) , give feedback in class, and review the students’ project updates and action items presented there. Hold office hours for ~3 hours/week for students to stop by esp. around key deadlines (beginning and end of semester, midpoint checkpoint) and clarify conceptual questions, troubleshoot technical problems. Approximately 5-6 hours/week. There\u0026rsquo;ll be less in the middle of the semester and more at the beginning and the very end. Requirements:\nSome familiarity with NLP and ML. Prof. Felix Heide # See academic website.\nTeam communication: A course Slack\nDescription: This position supports training job running and bringup of the base IW codebase on research clusters.\nResponsibilities (Approximately 5 hours/week):\nAttend weekly sync up meetings.\nSupport in environment bringup and testing of base code structure for IW projects.\nAid in IW code architecture bringup.\nRequirements:\nMust have prior experience as a UCA (in any course), Must be COS majors, Strong communication skills. Prof. Robert Fish # See [academic website]( https://www.cs.princeton.edu/courses/archive/fall23/cosIW04/ https://www.cs.princeton.edu/courses/archive/spring24/cosIW03).\nTeam communication: Email\nDescription: This position provides near-peer support for students in IW seminar, particularly those who have never done an IW before. UCA should be available to come to the seminar and find out what projects the students are doing. They should also have some office hours at convenient times to work with students to overcome barriers to success, particularly programming issues.\nResponsibilities (Approximately 6-10 hours/week):\nCome to seminar Have office hours at convenient times and be flexible about meeting students Able to check a GitHub or similar repo Willing to help with programming issues Requirements:\nMust pass an interview, Should have completed an IW project before Prof. Xiaoyan Li # See academic website.\nTeam communication: Email\nDescription:\nThis position holds office hours to help answer students\u0026rsquo; questions on using ML packages or coding with Python. The UCAs are also expected to help organize students\u0026rsquo; project presentation in class and check their weekly progress.\nResponsibilities (~7 hrs/week):\nAttend weekly class meeting ~1.5h/week or 3h/week (Fall 2024: Wednesdays 11AM-12:20PM or 3:00PM-4:20PM)\nHold office hours 1h or 2h/week\nRead students\u0026rsquo; weekly progress report 2h or 3h/week\nRequirements:\nPassing an interview with Prof. Xiaoyan Li\nHaving completed an IW in machine learning or data science\nGood programming skills with Python\nGood verbal and written communication skills\nProf. Mae Milano # See academic website.\nTeam communication: Slack\nDescription:\nThis position supports the course infrastructure and assists students in using it.\nThe course infrastructure consists of virtual machines and services hosted by Amazon, Microsoft, and Google. The purpose of this course is to gain experience using and configuring distributed systems. Experience with kubernetes, S3, EC2, Azure, or any other cloud-hosted services and cloud providers will be helpful. TAs will ensure virtual services remain available, help configure them correctly for the course, and help students effectively use these resources.\nResponsibilities (~8 hrs/week):\nAttend weekly 30min/week sync-up meeting to check on status of course infrastructure and assign action items\nTake direct responsibility for a particular cloud service or vendor\nConfigure networking and services on virtual machines\nhold 2-4 hours / week of office hours for students attempting to use these services\ncommunicate availability and summarize expected progress with cloud-specific tasks\nmonitor course email and slack\nmonitor assigned cloud services\nRequirements:\nexperience using linux-based systems\ncomfort on the command line\nfamiliarity with at least one cloud service\nProf. Huacheng Yu # See academic website.\nTeam communication: Email\nDescription:\nUCAs participate in in-class discussions, give quick feedbacks to the student presentations in class and project proposal and mid-term reports, and hold office hours.\nResponsibilities (~3 hrs/week):\nAttend weekly class meetings (80 minutes)\nHold a 1-hr office hour every week\nAttend TA meetings before \u0026ldquo;grading\u0026rdquo; the proposal and mid-term report\nRequirements:\nMust be COS or ORFE/MAT majors\nMust have taken a COS 4xx (and gotten an A- or better) or a 5xx-level theory course\n"},{"id":2,"href":"/docs/applicants/choice/","title":"Rules for Choosing a Job","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"Every semester, the Department of Computer Science processes about over 500 applications, for more than 250 positions (some UCAs work in several positions). We are very grateful for the interest in our courses, and we are committed to providing a fair and transparent process for all applicants.\nOur promise to you is to ensure that our process is free from bias and provides every student an opportunity to work in an interesting, résumé-building job, as expected of us by the official guidance set forth by the Office of the Dean of the College.\nLifecycle of a UCA Application # How to decide which jobs to apply to # Every job listed on TigerUHR should have a corresponding sub-section in our UCA job catalog.\nFor every job, the catalog provides you with:\nA link to the course, in which you will be able to see the course description.\nThe description of the job, which will provide you an overview of how the job fits into the course.\nThe responsibilities of the job, are an itemized list of the specific tasks you will be asked to do, helping set your expectations.\nThe requirements of the job, are an itemized list of how likely you are to be hired, if you apply for this job.\nThis information is provided to help you make an informed decision about which jobs you would like to apply for.\nHow to express your preferences # When the applications open, you may go to TigerUHR\u0026rsquo;s registration page.\nFor each UCA job, you can indicate that STRONG, WEAK or NO interest.\nThere are a few rules to consider:\nStaffing the Intro COS Lab program is the highest priority, as it serves a very large population of non-major students, and support the introductory curriculum of the department (COS 126, 217, 226 and occasionally COS 109). For this reason, if you apply, are interviewed and offered a job of Intro Lab TA, it will override your preferences, you will be assigned to it and cannot turn it down; on the flip side, this means if you are unsure whether you might get a UCA job, applying to the Intro COS Lab increases your chances significantly.\nYou may be found suitable for multiple jobs, and you will be hired first in the highest priority jobs for which you have expressed a STRONG preference. If you turn down an offer for your highest priority job AND you had expressed a STRONG preference for this job, we will not offer you a position in another course and you will not be offered an UCA job for this campaign.\nYou may accept positions for multiple courses, up to your discretion. However it is very important that you do not turn down a job you have already accepted; failure to abide by these terms may result in a mark in your record.\nThese rules are intended to provide stability for the faculty and to ensure that our most important courses are properly staffed.\nWhen you are hired # Once you have been hired for a position, you will receive an email from the faculty supervisor for that position around the beginnin of the second week of the semester. (You can also log into TigerUHR to check the status of your application.)\nAfter that point, the responsibility will be to the faculty supervisor to follow up with you and get you on-boarded.\nIf you have been hired for a job, but have not been onboarded, please contact us.\nWhen you are not hired # If all positions have been filled, we will send out an email to all applicants who are not hired for any position for this term.\n"},{"id":3,"href":"/docs/timeline/","title":"TIMELINE FOR HIRING","section":"Docs","content":"This page contain details about the timeline. (Subject to change)\nFall 2024 campaign # August 19: TigerUHR open for UCA applications September 2: Deadline to apply for a COS UCA job September 9-14: Decisions for UCA hiring "},{"id":4,"href":"/posts/2022-12-02-recruiting-ucas-for-spring-2023/","title":"Recruiting UCAs for Fall 2024","section":"Announcements\u003cbr/\u003e\u003cbr/\u003e","content":"We are testing the new TigerUHR system which will be used to accept UCA applications for Fall 2024. All undergraduate students will receive an email from the department with the link and instructions for applicaition about two weeks before the start of the semester.\n"},{"id":5,"href":"/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/","title":"COS Lab Recruiting for Fall 2021","section":"Announcements\u003cbr/\u003e\u003cbr/\u003e","content":"Today we sent the following announcement to all COS undergraduate students, with broader diffusion of this message to follow:\nHello, and I hope your summer is going well!\nThe Department of Computer Science is hiring enrolled undergraduates (that\u0026rsquo;s you!) to assist in many of our COS courses as Undergraduate Course Assistants (UCAs). This is an opportunity to gain teaching experience, work with and get to know faculty, and contribute back to our undergraduate curriculum.\nEvery term, we hire undergraduates in two steps:\n— We first recruit applicants for the COS Lab TAs positions. These are the undergraduate-staffed office hours for the COS 126 and COS 226/217 courses where you will help current students with the programming assignments, and teach them how to debug. We are collecting applications starting now and until August 20th, 2021. This is to allow for the longer interviewing process involved with that position. If you are interested in a Lab TA position, please apply as soon as possible.\n— We will then hire applicants for general positions (grader, facilitator, office hours in other courses) starting August 20th, 2021, and until the term begins. Some positions are already open and you are free to start applying to them, others will be opened up at the end of next week.\nThe web form below will allow you to apply for these positions. You do NOT need to be a COS concentrator, but you must be a current Princeton undergraduate, and must have taken the classes corresponding to the position you are applying for.\nThe pay rate for all positions is $15.50/hour. More details are provided on the form. To apply, please fill out the form:\nhttps://www.tigeruhr.io/register/\nYou can apply to additional jobs after your first application. Note, you will need to submit a .PDF copy of your Degree Progress Report (available on TigerHub) in order to finalize the form.\nThe general deadline is August 20th at midnight. Julia Ruskin ‘22 will make lab TA hiring decisions in consultation with the department. Applications submitted after the deadline may not be considered.\nIf you have technical difficulties when filling out the form or have any other questions about the program, please contact the head lab TA, Julia Ruskin ‘22, at jruskin@princeton.edu.\nBest wishes,\nThe COS UCA Program Coordinators.\n"},{"id":6,"href":"/posts/2021-07-29-launch-of-site/","title":"Launching the New Site","section":"Announcements\u003cbr/\u003e\u003cbr/\u003e","content":"This is a website to document the valuable contribution that undergraduate students provide the teaching mission of Princeton University\u0026rsquo;s Deparment of Computer Science, and to provide information on this program.\nThe goal of the website will be, among other things, to help provide information to both prospective applicants and current students about the different roles and jobs fulfilled by Undergraduate Course Assistants.\nThe website is built using the Hugo static site generator, the Hugo Book theme, and is hosted on GitHub Pages.\n"},{"id":7,"href":"/docs/employees/payroll/","title":"Before Getting Paid\u0026hellip;","section":"For Current Employees","content":" Summary # Before being added to department payroll, you need to complete your tax paperwork (I-9 and W-2 forms) either at the Office of Student Employment, or online on JobX. This paperwork will only need to be filed once during your time at Princeton; for legal reasons, it can only be filed when you have a job offer.\nOnce your tax paperwork is filed, you can be added to the Department of Computer Science\u0026rsquo;s payroll, and start declaring hours using the TimesheetX platform.\nThe most common issue that new hires face is that they do not complete their tax paperwork, and they cannot be added to TimesheetX. The best person to contact for any issues having to do with payroll is Louis Riehl.\nOverview # Before getting paid by the Department of Computer Science, you need to be registered in two different places:\nYou need to be registered with the Student Employment Office to be added to University payroll: They will check your eligibility to work, and collect the necessary tax forms. This is a necessary step for any job on campus, but must only be done once during your time at Princeton.\nOnly once you are registered with the Student Employment Office, can you be added to the department\u0026rsquo;s time collection payroll. This is a step we will do for you, once you have filed your paperwork with the University and been hired in one of our jobs. Only when this step is complete are you allowed to begin work and declare your hours. If you have not completed the first step, our financial administrator will not be able to select you to be added to our payroll.\nOnce these steps have been completed, you will be ready to find out How to Declare Your Hours to get paid.\nYou will typically do Step 1 as soon as possible; if the current procedure outlined by the Student Employment Office, you should aim to take care of the paperwork in your first week on campus. Step 2 can be accomplished as needed as you are hired. Submitting the Student Employment Office Paperwork # Students who are not already on the payroll, can find instructions on the necessary forms to complete at this section of the Student Employment Office website. Since March 2020, the Student Employment Office has allowed these documents to be verified remotely, using video conference; it is unclear how long this practice will continue to be used. Previously, documents needed to be manually brought to the office for verification.\nAs part of your hiring, you will need to fill to U.S. federal tax forms:\nan I-9 form, the purpose of which is to verify that you are eligible to work under U.S. employment law. This will require you to show some documents to prove your identity and your authorization to work in the U.S.;\na W-4 form, the purpose of which is to determine how much the University must withhold from your paycheck to prepay federal taxes. This amount is an approximation of the taxes you might owe, usually an over-approximation which explains why consistently over 80% of U.S. tax-payers get a federal tax refund.\nGetting Added to the Department\u0026rsquo;s Payroll # You need to complete your Student Employment Office Paperwork as soon as possible ideally, before being hired by the department.\nYou have or will apply for a job with the department on TigerUHR. Once you have been hired into a job, you will be added to queue that will notify our financial assistant, Elizabeth Wang, to add you to the department payroll for the corresponding job.\nIf you have not filed the necessary paperwork, you will not be available to be added to the department\u0026rsquo;s payroll, and an email will be sent to you to let you know that you need to file paperwork before we can take further action.\nSample Hiring Confirmation Message # Once you have been hired, you will be typically receive an email from Louis Riehl outlining the most important aspects of declaring hours.\nThis is a sample message from February 2021:\nThis is to inform you that you have been added to the Payroll System as a XXXXXXXX in Computer Science.\nPlease go to https://princeton.studentemployment.ngwebsolutions.com/Cmx_Content.aspx?cpId=6 (“Student Employees” -\u0026gt; ”My Timesheets”) for instruction on how to enter your hours. If you have multiple roles at Princeton for which you are paid, please be sure to enter your hours associated with the correct role. For example, this includes if you are both a grader and a TA for Computer Science (we pay out these roles on different chart strings, and need an accurate accounting of each).\nPlease also note, if you do not enter your hours by the end of a pay period, you will not get paid on time! (Current period ends 2/21/2021.) Hours need to be entered by the Monday after every 2-week pay period in order to be logged in time for Payroll to process with regular paydays. Hours entered retroactively get paid as backpay, and are delayed. Please enter your hours by the end of every 2-week pay period!\nLet me know if you have any trouble entering your hours.\n"},{"id":8,"href":"/docs/general/staff/","title":"Current Staff","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":" TBD # "},{"id":9,"href":"/docs/employees/time-collection/","title":"How to Declare Your Hours","section":"For Current Employees","content":" Summary # Once you have been added to the department\u0026rsquo;s payroll, you can declare the hours that you work in the TimesheetX platform and get paid every few weeks. Overview: What are JobX and TimesheetX? # Princeton University uses JobX to advertise and solicit applications for most student employment jobs on campus (recruiting both undergraduate and graduate students). These jobs are typically hourly jobs, and student employees declare their hours on TimesheetX. Below is information on how to use the latter to declare your hours for COS jobs.\nFor most UCA jobs, the Department of Computer Science does its hiring through TigerUHR. However some jobs, in particular summer research internships, are advertised through JobX.\nYou cannot be added to the payroll for an hourly job until you have completed your official employment paperwork. Please make sure you follow all steps outlined in the Before Getting Paid page. How to Get Help # If you have any questions about getting added to payroll or declaring hours, you may contact Elizabeth Wang, who oversees the department\u0026rsquo;s payroll for Undergraduate Course Assistants.\nIf you belong to the UCA Slack, you can also ask her questions in the #payroll channel.\nOfficial Instructions # The Student Employees portal contains several useful resources, including:\nTutorial on JobX and TimesheetX: JobX is the platform on which you can search for a large number of student employment jobs on campus; TimesheetX is the platform on which you will declare your hours once hired.\nQuick Tips for Time Sheet Entry\nStep-by-Step Guide # Go to TigerHub.\nHours must be reported separately for each category of job (grader, facilitator, etc.) that you may be hired in. Begin by selecting a category in which to declare hours. This will process have to be repeated for other jobs.\nClick on \u0026ldquo;Start time sheet\u0026rdquo; on the most recent pay period.\nEnter every shift you worked. For each shift, click \u0026ldquo;Add a new entry.\u0026rdquo;\nEnter the details of the entry.\nOnce done entering all your hours for a given pay period, click \u0026ldquo;Submit Time Sheet.\u0026rdquo; Note: Only one time sheet can be submitted per period; and time sheets cannot be edited once submitted. For this reason, it is important to only submit at the end of pay period, once all entries have been submitted.\nReview the accuracy of your submission, before it is sent to our administrative coordinator and financial assistant.\nAnd confirm a second time.\nOnce your submission has been made, review the details of when we will have reviewed it, and when it will be transferred to Princeton\u0026rsquo;s financial department for disbursement to you.\n"},{"id":10,"href":"/docs/applicants/apply/","title":"How/When to Apply","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"The deparement will send all COS undergraduate students an email with instructions for UCA application about 2 weeks before the start of the semester.\nApplications are submitted on the TigerUHR registration page.\nTranscript Information # As part of the application process, TigerUHR will ask that you submit an up-to-date transcript. These documents can be obtained from TigerHub.\nInternal Transcript # Also acceptable: Degree Progress Report # "},{"id":11,"href":"/docs/general/past-ucas/","title":"Past Helpers","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":"This page lists past employees.\nPast Head Lab TAs # In chronological order, since 2013:\nAlex Daifotis Erica Portnoy and Utsarga Sikder Curtis Belmont Diana Liao Sally Jiao Benjamin G. Schiffer Justin Chang and Lily Zhang Julia Ruskin Diana Espindola and Austin Li Past Tool Builders # Vinay Ayyala \u0026lsquo;16 (codePost) Alex Daifotis \u0026lsquo;14 (LabQueueV1) James Evans \u0026lsquo;16 (codePost) Richard Freling \u0026lsquo;16 (codePost) Lance Goodridge ’17 *19 (TigerUHR and LabQueueV3) Aaron Lichtblau \u0026lsquo;22 (LabScheduler) Moin Mir \u0026lsquo;23 (subswap) Jeremy Dapaah \u0026lsquo;24 (QTrack) "},{"id":12,"href":"/docs/applicants/interview/","title":"Jobs that Require An Interview","section":"\u003cstrong\u003eFor Prospective Applicants\u003c/strong\u003e","content":"Some jobs require an interview, currently this includes the following jobs:\nCOS 126 Lab TA COS 2xx Lab TA Because scheduling and giving interviews takes time, these jobs usually have an earlier deadline than most jobs.\nInformation about the COS Lab Interview Process # Julia Ruskin BSE \u0026lsquo;22, Head Lab TA in 2021, describes the interview process for the Intro COS Lab in the following way:\nWe interview to get a sense for how the candidates would act when interacting with students. Since we get so many more applicants than we can realistically hire, we need to differentiate between them, and assessing their ability to debug in real time along with their ability to explain concepts and their general helping manner is a much better way to differentiate than just looking at grades. [Currently,] we split the interviews between me and 4 other interviewers, two for 126 and two for 226/217,\nFirst, applicants apply on TigerUHR. Then, I reach out to all the applicants who meet the grades criteria (I don’t know what grade it corresponds to, but a 3/5 or higher on TigerUHR) to schedule interviews on a Calendly like. We split the interviews evenly between the interviewers and conduct them remotely, screensharing a code file with 3 bugs and having the candidate walk us through the code as if they were a TA. We use a predetermined rubric to assign a score to each candidate, and we also record comments about their approach and general helping manner. Then, we determine how many TAs we need to hire, and we hire the TAs with the highest scores.\nTAs can be hired for 226/217 or 126, either as full time (2 shifts/week), part time (1 shift/week), or subs. [\u0026hellip;]\nAs the Head TA, I am in charge of conducting interviews and hiring TAs, coordinating training for new TAs, creating the schedule, overseeing TA shadowing, and being the general point person for anything that comes up throughout the semester.\n"},{"id":13,"href":"/docs/general/contribute/","title":"How to Contribute to this Site","section":"\u003cbr/\u003e\u003cstrong\u003eGeneral Information\u003c/strong\u003e","content":" How to Contribute to this Site # This site is hosted in a public GitHub repository. It uses the Hugo static site generator and the actual pages are written in Markdown (see cheat sheet here). It is published using GitHub Pages.\nAnybody with a GitHub account, can suggest changes to an existing page with only two or three clicks, like for Wikipedia. (Anybody can also propose new pages, but that requires a few more clicks.)\nIf you have made several contributions, you may be made a collaborator and you will be able to directly modify the site without requiring approval. (Since GitHub is a version control system, all changes are tracked and it is easy to undo specific changes, if they are later identified as malicious).\nBelow we outline how to suggest a change for any existing page on the website to get you started. This is a good opportunity to get to know GitHub and version control systems, which are really important tools.\nFirst Step: Click \u0026ldquo;Edit this page\u0026rdquo; # On any page of this site, including this one, you can find a link at the bottom, or bottom-right of the site, that is captioned Edit this page. The next step depends on whether you are a collaborator or not.\nHow to suggest a change if you are not a collaborator # If you are not a collaborator, you cannot push changes to the repository directly: You must first make fork to your repository. Fortunately GitHub both clearly indicates when this must happen, and transparently creates the fork for you such that this step of the process is completely transparent to you.\nYou can click \u0026ldquo;Fork this repository\u0026rdquo; and then follow the steps outlined starting in Step 2 of GitHub\u0026rsquo;s guide on Editing Files in Another User\u0026rsquo;s Repository.\nThank you in advance for your contribution! Depending on whether the semester is busy, your contribution will be reviewed soon. Once several of your contributions have been accepted, we will likely consider making you a collaborator!\nHow to suggest a change if you are a collaborator # If you are a collaborator, there is no need for a fork: You can edit files directly as though were the owner of the files. After clicking on Edit this page, you can follow the steps outlined starting in Step 2 of GitHub\u0026rsquo;s guide on Editing Files in Your Repository.\n"},{"id":14,"href":"/docs/employees/slack/","title":"The UCA Slack","section":"For Current Employees","content":"The Slack is where certain jobs coordinate.\nIt is available at https://princetoncosutas.slack.com/, with Princeton CAS login.\nThe rosters for this Slack are automatically synchronized based on TigerUHR\u0026rsquo;s rosters. You will automatically be placed in the appropriate channels.\n"}] \ No newline at end of file diff --git a/en.search.min.820ce8b4697813b452dcd95b4040574634746e15d8ab5b70e5069fb6c7d70e0d.js b/en.search.min.8d19db39ef7e52f386bdfe9a850243fd31200c446b0bab136d6421f0879351a4.js similarity index 90% rename from en.search.min.820ce8b4697813b452dcd95b4040574634746e15d8ab5b70e5069fb6c7d70e0d.js rename to en.search.min.8d19db39ef7e52f386bdfe9a850243fd31200c446b0bab136d6421f0879351a4.js index 7695081..02482a6 100644 --- a/en.search.min.820ce8b4697813b452dcd95b4040574634746e15d8ab5b70e5069fb6c7d70e0d.js +++ b/en.search.min.8d19db39ef7e52f386bdfe9a850243fd31200c446b0bab136d6421f0879351a4.js @@ -1 +1 @@ -"use strict";(function(){const o="/en.search-data.min.a16927a6613e3dfd0e9ef6da299e1cae1dee166a1347131bbfeb3165d28f4dd4.json",i=Object.assign({cache:!0},{doc:{id:"id",field:["title","content"],store:["title","href","section"]}}),e=document.querySelector("#book-search-input"),t=document.querySelector("#book-search-results");if(!e)return;e.addEventListener("focus",n),e.addEventListener("keyup",s),document.addEventListener("keypress",a);function a(t){if(e===document.activeElement)return;const n=String.fromCharCode(t.charCode);if(!r(n))return;e.focus(),t.preventDefault()}function r(t){const n=e.getAttribute("data-hotkeys")||"";return n.indexOf(t)>=0}function n(){e.removeEventListener("focus",n),e.required=!0,fetch(o).then(e=>e.json()).then(e=>{window.bookSearchIndex=FlexSearch.create("balance",i),window.bookSearchIndex.add(e)}).then(()=>e.required=!1).then(s)}function s(){for(;t.firstChild;)t.removeChild(t.firstChild);if(!e.value)return;const n=window.bookSearchIndex.search(e.value,10);n.forEach(function(e){const n=c("
    • "),s=n.querySelector("a"),o=n.querySelector("small");s.href=e.href,s.textContent=e.title,o.textContent=e.section,t.appendChild(n)})}function c(e){const t=document.createElement("div");return t.innerHTML=e,t.firstChild}})() \ No newline at end of file +"use strict";(function(){const o="/en.search-data.min.4ba023eccb056c518af111f9343b02c4ed9289ee7688d8f83e117ebd476177c3.json",i=Object.assign({cache:!0},{doc:{id:"id",field:["title","content"],store:["title","href","section"]}}),e=document.querySelector("#book-search-input"),t=document.querySelector("#book-search-results");if(!e)return;e.addEventListener("focus",n),e.addEventListener("keyup",s),document.addEventListener("keypress",a);function a(t){if(e===document.activeElement)return;const n=String.fromCharCode(t.charCode);if(!r(n))return;e.focus(),t.preventDefault()}function r(t){const n=e.getAttribute("data-hotkeys")||"";return n.indexOf(t)>=0}function n(){e.removeEventListener("focus",n),e.required=!0,fetch(o).then(e=>e.json()).then(e=>{window.bookSearchIndex=FlexSearch.create("balance",i),window.bookSearchIndex.add(e)}).then(()=>e.required=!1).then(s)}function s(){for(;t.firstChild;)t.removeChild(t.firstChild);if(!e.value)return;const n=window.bookSearchIndex.search(e.value,10);n.forEach(function(e){const n=c("
    • "),s=n.querySelector("a"),o=n.querySelector("small");s.href=e.href,s.textContent=e.title,o.textContent=e.section,t.appendChild(n)})}function c(e){const t=document.createElement("div");return t.innerHTML=e,t.firstChild}})() \ No newline at end of file diff --git a/index.html b/index.html index 990de16..a86cc48 100644 --- a/index.html +++ b/index.html @@ -1,5 +1,5 @@ Landing Page | Princeton COS Undergraduate Course Assistants Program - +
    diff --git a/posts/2021-07-29-launch-of-site/index.html b/posts/2021-07-29-launch-of-site/index.html index 765ed73..b720e23 100644 --- a/posts/2021-07-29-launch-of-site/index.html +++ b/posts/2021-07-29-launch-of-site/index.html @@ -3,7 +3,7 @@ The website is built using the Hugo static site generator, the Hugo Book theme, and is hosted on GitHub Pages.">Launching the New Site | Princeton COS Undergraduate Course Assistants Program - +
    diff --git a/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/index.html b/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/index.html index 6dd7dcf..46262e1 100644 --- a/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/index.html +++ b/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/index.html @@ -3,7 +3,7 @@ The Department of Computer Science is hiring enrolled undergraduates (that’s you!) to assist in many of our COS courses as Undergraduate Course Assistants (UCAs). This is an opportunity to gain teaching experience, work with and get to know faculty, and contribute back to our undergraduate curriculum.">COS Lab Recruiting for Fall 2021 | Princeton COS Undergraduate Course Assistants Program - +
    diff --git a/posts/2022-12-02-recruiting-ucas-for-spring-2023/index.html b/posts/2022-12-02-recruiting-ucas-for-spring-2023/index.html index cbdffa7..344ccba 100644 --- a/posts/2022-12-02-recruiting-ucas-for-spring-2023/index.html +++ b/posts/2022-12-02-recruiting-ucas-for-spring-2023/index.html @@ -1,5 +1,5 @@ Recruiting UCAs for Fall 2024 | Princeton COS Undergraduate Course Assistants Program - +
    diff --git a/posts/index.html b/posts/index.html index 4f95a9e..0bb1f7e 100644 --- a/posts/index.html +++ b/posts/index.html @@ -1,5 +1,5 @@ Announcements<br/><br/> | Princeton COS Undergraduate Course Assistants Program - +
    diff --git a/sitemap.xml b/sitemap.xml index 8562d65..3b1dd44 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1 +1 @@ -https://ugradjobs.cs.princeton.edu/docs/general/contact/2024-07-31T11:22:05-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/jobs/2024-08-14T10:12:42-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/choice/2024-07-31T12:08:26-04:00https://ugradjobs.cs.princeton.edu/docs/timeline/2024-07-31T12:20:40-04:00https://ugradjobs.cs.princeton.edu/posts/2022-12-02-recruiting-ucas-for-spring-2023/2024-07-31T11:36:37-04:00https://ugradjobs.cs.princeton.edu/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/2021-08-14T01:00:41-04:00https://ugradjobs.cs.princeton.edu/posts/2021-07-29-launch-of-site/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/docs/employees/payroll/2024-08-13T16:09:39-04:00https://ugradjobs.cs.princeton.edu/docs/general/staff/2023-08-07T09:46:57-04:00https://ugradjobs.cs.princeton.edu/docs/students/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/2021-07-29T01:27:37-04:00https://ugradjobs.cs.princeton.edu/docs/employees/time-collection/2024-07-31T11:51:40-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/apply/2024-07-31T11:44:53-04:00https://ugradjobs.cs.princeton.edu/docs/general/past-ucas/2023-01-19T01:11:52-05:00https://ugradjobs.cs.princeton.edu/docs/applicants/interview/2021-08-14T00:55:05-04:00https://ugradjobs.cs.princeton.edu/docs/employees/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/docs/general/contribute/2023-01-19T01:07:08-05:00https://ugradjobs.cs.princeton.edu/docs/employees/slack/2023-01-19T12:22:49-05:00https://ugradjobs.cs.princeton.edu/docs/general/2021-07-29T01:38:29-04:00https://ugradjobs.cs.princeton.edu/posts/2021-07-29T02:43:11-04:00https://ugradjobs.cs.princeton.edu/categories/https://ugradjobs.cs.princeton.edu/docs/2024-08-14T10:12:42-04:00https://ugradjobs.cs.princeton.edu/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/tags/ \ No newline at end of file +https://ugradjobs.cs.princeton.edu/docs/general/contact/2024-07-31T11:22:05-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/jobs/2024-08-14T10:47:33-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/choice/2024-07-31T12:08:26-04:00https://ugradjobs.cs.princeton.edu/docs/timeline/2024-07-31T12:20:40-04:00https://ugradjobs.cs.princeton.edu/posts/2022-12-02-recruiting-ucas-for-spring-2023/2024-07-31T11:36:37-04:00https://ugradjobs.cs.princeton.edu/posts/2021-08-13-cos-lab-recruiting-for-fall-2021/2021-08-14T01:00:41-04:00https://ugradjobs.cs.princeton.edu/posts/2021-07-29-launch-of-site/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/docs/employees/payroll/2024-08-13T16:09:39-04:00https://ugradjobs.cs.princeton.edu/docs/general/staff/2023-08-07T09:46:57-04:00https://ugradjobs.cs.princeton.edu/docs/students/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/2021-07-29T01:27:37-04:00https://ugradjobs.cs.princeton.edu/docs/employees/time-collection/2024-07-31T11:51:40-04:00https://ugradjobs.cs.princeton.edu/docs/applicants/apply/2024-07-31T11:44:53-04:00https://ugradjobs.cs.princeton.edu/docs/general/past-ucas/2023-01-19T01:11:52-05:00https://ugradjobs.cs.princeton.edu/docs/applicants/interview/2021-08-14T00:55:05-04:00https://ugradjobs.cs.princeton.edu/docs/employees/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/docs/general/contribute/2023-01-19T01:07:08-05:00https://ugradjobs.cs.princeton.edu/docs/employees/slack/2023-01-19T12:22:49-05:00https://ugradjobs.cs.princeton.edu/docs/general/2021-07-29T01:38:29-04:00https://ugradjobs.cs.princeton.edu/posts/2021-07-29T02:43:11-04:00https://ugradjobs.cs.princeton.edu/categories/https://ugradjobs.cs.princeton.edu/docs/2024-08-14T10:47:33-04:00https://ugradjobs.cs.princeton.edu/2021-07-29T00:58:05-04:00https://ugradjobs.cs.princeton.edu/tags/ \ No newline at end of file diff --git a/tags/index.html b/tags/index.html index 905d5b1..1fcc2bd 100644 --- a/tags/index.html +++ b/tags/index.html @@ -1,5 +1,5 @@ Tags | Princeton COS Undergraduate Course Assistants Program - +