Overview

Fall 2026 Leads: Role Outline + Expectations

This is a list of all responsibilities T4SG Engineering team leads will be expected to fulfill throughout the Fall 2026 semester. Although the list is not all-inclusive, we have tried to make it as comprehensive as possible so you can plan ahead and know exactly what to expect!

Tl;dr: As a project lead, beyond running your project, you are the face of the T4SG community for your SWEs. We expect that you’ll be engaged with T4SG as a whole and contribute to the community!

Role Specific Details + Interview Notes

General Expectations

  • Responsiveness on Slack: We expect a minimum 24-hour response time on Slack, with more responsiveness (~12 hr) at the beginning of the semester when there’s a lot going on. Please make sure you have Slack notifications enabled for relevant Slack channels (#general, #f26-eng-leads, #f26-project-leads, and DMs) and are checking Slack daily!
  • Scheduling: We use iCal (Apple Calendar, Google Calendar, etc.) to schedule all events and will invite your school email (or another you prefer) to all relevant events.
  • Communication in advance: We totally understand life/classes/emergencies happen. If you need to miss any meetings or take any period of time away from T4SG-related work, let your co-lead and the DOEs know as soon as possible (preferably >24hr in advance)!
  • Social engagement: Community is the most important part of T4SG. Furthermore, you are the most important part of the T4SG community, because you spend the most time working and interacting with the SWEs day-to-day. Thus, we expect our leads to make time for T4SG’s social gatherings throughout the semester and encourage their team to attend. (You are often your SWEs’ only/biggest reason for coming to a social!) Lead Attendance at socials is required and is recognized and valued by your fellow T4SG’ers.

Beginning of semester

Onboarding + Project Setup

  • Leads onboarding meeting (3-4 hr): A meeting to go over semester logistics and prepare for the hectic member recruiting period. We will also include workshops for PMs and SSWEs to run through initiating a project and planning a week in the semester.
  • Project setup (variable time): You will be working with your co-lead to have your project infrastructure set up before SWEs onboard for the semester. This involves having an initial client meeting, completing the semester timeline, setting up the project codebase/repo and any foundational functionality (i.e. routing, user auth), and having starter projects/tasks ready for SWEs.
  • T4SG Orientation Day (3 hr): Beginning of semester to meet all of T4SG, introduce yourself to your new SWEs, and set up initial project logistics.

Member recruiting: Workshops/OH, interviews, and delibs

  • Workshops/application OH (2 hrs by signup), Dates TBD: The SWE R2 application process for Fall 2026 will last one week, with four 1.5-hour workshops spaced every other night, each co-hosted by two leads, and office hours held outside of workshops. We will ask leads to sign up for one of two options:
    • 45 min of application OH + co-hosting an internal workshop (1.5 hours)
    • Workshop content is already developed; you just need to familiarize yourself with the content and deliver it.
  • R2 interviews (2-3 hr): Every lead is expected to book 12 30-minute slots (variable amount depending on application volume) to interview R2 applicants. Because leads are paired for interviews and applicant sign-ups are variable, you will typically end up conducting 4-6 interviews. Interview obligations have been disproportionately imbalanced among leads in the past, so our goal is to spread out interviewing responsibilities as much as possible!
  • R2 delibs + project matching (3-4 hr): Meeting with all leads and DOEs to discuss applicants/interviews, make decisions, and select SWEs for your project team!

Throughout semester

Weekly meetings

  • Team meeting (45 min): To review the week’s progress, discuss/address challenges, and assign new deliverables.
    • Fill out team feedback form
  • Work sessions (both leads, 1-2 hr): For SWEs to meet with leads for help resolving bugs/technical challenges. SWEs can be excused if they submit a PR or show progress by date.
  • PM/SSWE sync (30 min-1hr): Meeting between PM and SSWE to discuss project progress, plan future directions, and write deliverables.
    • Deliverable: An outline of a task to be accomplished by a SWE over a week. Includes a general high-level overview of the task, a set of instructions for a suggested approach, and a list of helpful references/guides
    • Writing deliverables (especially detailed, well-crafted ones) may take longer than the PM/SSWE sync.
  • Client meeting (30 min - 1 hr): This will be held weekly to update your client on your progress, obtain feedback, request additional resources, etc.
  • Lead Sync - PM/SSWE/DOE sync (1 hr): Meeting between leads and DOE(s) to check in on project progress and discuss tips/guidance. You also will be meeting with other leads who are working on similar projects.

One-time commitments

  • Inter-Team Feedback Program (1 hr): You will need to attend a different team’s weekly meeting and complete a short feedback form reflecting on your insights from seeing how a different team operates.
  • DIET sessions (1 hr): In collaboration with our Directors of Ethical Tech (DIETs), you will help co-host a meeting with your team reflecting on your project’s implications for diversity, inclusion, and ethical technology (DIET). The exact format of these meetings is TBD!
  • Midpoint Presentation (1 hr): 1-hour presentation from you and your team to your client, DOEs, and any other guests to recap the project goals, summarize progress, and reflect on directions in the middle of the semester. This should include a slide deck and not simply be in the format of a weekly client meeting.
  • Check-ins with SWEs (1-1.5 hr): Short 15-20 min check-ins with each SWE, to be held at the beginning of semester and after the midpoint presentation. The beginning of semester check-in is for getting to know your SWEs, understanding their goals for the semester, and establishing feedback norms. The post-midpoint check-in is for making sure SWEs are being adequately fulfilled by their work and reflecting on any feedback from the first part of the semester.
    • You should be checking in with your SWEs on a weekly basis! Does not have to be an official meeting, just Slack mid-week (between team meetings) and ask how they are doing (within and outside of T4SG!)
  • Application and Internal Eng Workshop Series (1.5 hrs, by sign-up): We host workshops for our internal application process and for the basics of using Git in the beginning of the semester, each co-hosted by 2 leads. The first three will be hosted for the application process with the fourth workshop discussing the basics of Git.
    • Workshop content is already developed; you just need to familiarize yourself with the content and deliver it.

Socials/Initiatives

You’ll be hosting two socials for your team (free food on T4SG’s budget)! One should happen at the beginning of semester, and the other in the second half of the semester (post-midpoint to pre-final presentation).

T4SG will also be hosting several socials throughout the semester. Attendance at these socials is required. These include:

  • Midpoint celebration (git lit)
  • Final celebration
  • Two Eng leads socials (DOEs + all Eng leads): the first is the pitch party, and the second happens later in the semester. Highly suggested, borderline mandatory (because it’s fun!)
  • Discussion dinners (organized by DIETs)
  • Director Dialogues (aka Open DOE Meetings)

End of semester

  • Final Presentation (1 hr): 1-hour presentation from you and your team to your client, DOEs, and any other guests to recap the project goals, present the semester’s accomplishments, and reflect on future directions. This should include a slide deck and not simply be in the format of a weekly client meeting.
  • Code handoff (variable time): The handoff process typically occurs after final presentation (may stretch into the first 1-2 weeks of break) and involves writing necessary documentation and polishing code (your team can help with this). After that, you should share all code, accounts, API keys, etc. with your client!