Sessional Lecturer - CSC367H1S - Parallel Programming

We need to output HTML fragment only, with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key content: - Course number and title: CSC367H1S - Parallel Programming - Position 1: CSC367H1S, LEC0101 - Position 2: CSC367H1S, LEC0201 - Please note, this position is a 0.5 FCE appointment. - Course description: Introduction to aspects of parallel programming. Topics include computer instruction execution, instruction-level parallelism, memory system performance, task and data parallelism, parallel models (shared memory, message passing), synchronization, scalability and Amdahl's law, Flynn taxonomy, vector processing and parallel computing architectures. - Reference: https://artsci.calendar.utoronto.ca/course/csc367h1 - Estimated course enrolment: 125 students per section - Estimated TA support: one 60-hour TA position for every 30 students - Class Schedule Position 1: Mondays, Wednesdays, and Fridays 10:00-11:00 - Position 2: Mondays, Wednesdays, and Fridays 10:00-11:00 - Please note, the delivery method for this course is currently in-person. - Please note that, in keeping with current circumstances, the section delivery method may change as determined by the Faculty or the Department. - Sessional dates of appointment: January 1, 2027 – April 30, 2027 - Salary Sessional Lecturer I = $9,997.48 - Sessional Lecturer I - Long Term = $10,699.22 - Sessional Lecturer II = $10,699.22 - Sessional Lecturer II - Long Term = $10,953.96 - Sessional Lecturer III = $10,953.96 - Sessional Lecturer III - Long Term = $11,228.90 - Please note that should rates stipulated in the collective agreement vary from rates stated in this posting, the rates stated in the collective agreement shall prevail. - Minimum Qualifications: Graduate degree in Computer Science or closely related field required. Demonstrated expertise in topic area of the course required. Strong organizational, interpersonal, and communication skills required. Teaching experience at the university level or equivalent industry level required. - Preferred Qualifications: Previous experience teaching undergraduate courses in the field of Computer Science preferred. Demonstrated evidence of excellence in teaching preferred. - Description Of Duties: Preparing and delivering the lectures in-person on campus as scheduled. Handling course administration including: maintaining the course website on Quercus; developing marking schemes/syllabus; planning tutorial content (when applicable); developing course assessments including assignments, projects, quizzes, tests, and final assessments. Providing appropriate contact time outside of class to students, through office hours, email, the course website and/or the course bulletin board. Preparing the breakdown of hours for TA duties in the course and supervising the TAs. Ensuring that tutorials and/or labs are delivered appropriately by the TAs as applicable. Managing the grading for the course, which is largely done by the TAs, and carrying out any grading not handled by the TAs. Invigilating term tests and the final exam when applicable. Managing the grades, including the timely completion and release of grades and feedback to students throughout the term; submitting final course grades (due May 7, 2027). While there is a lot of room for creativity in course delivery, instructors will be expected to follow the basic content and style used by the faculty members who normally teach the course, and must get approval from these faculty members or from the Associate Chair for any substantial changes to the course content or assessment methods. Instructors will also be expected to consult with the department’s Teaching Support group when creating the course syllabus and course assessments (tests, assignments, projects, and final exam) - Application instructions: ... (we must remove application instructions) - Closing Date: 10/20/2026, 11:59PM EDT - Diversity Statement, Accessibility Statement, etc. (these are boilerplate; we should remove them) - Job Segment: Computer Science, Cloud, Information Technology, Programmer, Technology (maybe not needed) - Find Similar Jobs etc. We need to keep substantive info: description, duties, qualifications, schedule, pay, dates, etc. We need to decide sections: About the role (maybe course description), Responsibilities (duties), Requirements (minimum qualifications), Qualifications (preferred qualifications?), Skills (maybe not explicit), Benefits (none explicit), Pay (salary), Schedule (class schedule and appointment dates). Also maybe "Appointment Details" but we stick to allowed headings. We must not create sections with placeholder/filler. So we need to ensure each section has real content. We have: - About the role: could include course description, FCE, positions, enrolment, TA support, delivery method, appointment dates. That's substantive. - Responsibilities: description of duties (list). Use

  • . - Requirements: minimum qualifications (list). Use
    • . - Qualifications: preferred qualifications (list). Use
      • . - Skills: maybe not explicit; we could omit if no specific skills listed besides those in qualifications. Better to omit. - Benefits: none explicit; omit. - Pay: salary rates (list). Use
        • . - Schedule: class schedule (days/times) and appointment dates (sessional dates). Could also include delivery method note. Use

          or

          . We must not repeat job title as heading. So no

          Sessional Lecturer... etc. We must not put Job ID/Req ID as heading; we can include them in a short

          maybe but not required. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it." We can drop them. We must remove application instructions, closing date? Closing date is substantive? It's part of posting but maybe considered metadata; but we could keep as part of About the role? Might be considered minor metadata. The instruction says preserve ALL substantive information; closing date is substantive for applicants. However, we might include it in a short

          under About the role or separate? The instruction says we can fold minor metadata into a short

          . Closing date maybe minor but still substantive. I'd include it in a

          maybe under About the role. We must remove boilerplate like Diversity Statement, Accessibility Statement, Job Segment, etc. We must not include duplicated lines. Now produce HTML fragment. Structure:

          About the role

          ... course description, FCE, positions, enrolment, TA support, delivery method, appointment dates, closing date maybe.

          Responsibilities

          • ...
          ...

          Requirements

          • Graduate degree in Computer Science or closely related field required.
          • Demonstrated expertise in topic area of the course required.
          • Strong organizational, interpersonal, and communication skills required.
          • Teaching experience at the university level or equivalent industry level required.

          Qualifications

          • Previous experience teaching undergraduate courses in the field of Computer Science preferred.
          • Demonstrated evidence of excellence in teaching preferred.

          Pay

          • Sessional Lecturer I = $9,997.48
          • Sessional Lecturer I - Long Term = $10,699.22
          • Sessional Lecturer II = $10,699.22
          • Sessional Lecturer II - Long Term = $10,953.96
          • Sessional Lecturer III = $10,953.96
          • Sessional Lecturer III - Long Term = $11,228.90

          Schedule

          Class sessions: Mondays, Wednesdays, and Fridays 10:00‑11:00 (both sections LEC0101 and LEC0201). Delivery method: in‑person (subject to change per Faculty/Department). Appointment period: January 1, 2027 – April 30, 2027. Estimated enrolment: 125 students per section. Estimated TA support: one 60‑hour TA position for every 30 students. Position is a 0.5 FCE appointment.

          We need to ensure we didn't miss any substantive info: reference link? Could be included in About the role as a link. The instruction: preserve ALL substantive information; we should include the reference link. Also maybe include the course number and title. Already in About the role. We should also include that the position is 0.5 FCE appointment (we have). Also include that the position is a Sessional Lecturer (but we shouldn't repeat job title as heading; but we can mention in prose). Also include that there are two positions (LEC0101 and LEC0201). Already. We should also include note about rates stipulated in collective agreement may vary; we can include a note in Pay section: "Note: Should rates stipulated in the collective agreement vary from rates stated in this posting, the rates stated in the collective agreement shall prevail." That's substantive. Also include note about closing date: we can add in About the role: "Applications close October 20, 2026, 11:59 PM EDT." We must not include application instructions (the link, email, etc). So we drop that. We must not include the diversity statement, accessibility statement, etc. Now produce HTML. Check for any duplicated lines: we have not repeated. Make sure to use proper HTML tags:

          ,

          ,

          • . No extra tags. Let's craft the About the role paragraph: "Course: CSC367H1S – Parallel Programming. Introduction to aspects of parallel programming. Topics include computer instruction execution, instruction-level parallelism, memory system performance, task and data parallelism, parallel models (shared memory, message passing), synchronization, scalability and Amdahl's law, Flynn taxonomy, vector processing and parallel computing architectures. Reference: https://artsci.calendar.utoronto.ca/course/csc367h1. Estimated enrolment: 125 students per section. Estimated TA support: one 60‑hour TA position for every 30 students. Two sections offered