Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Assign meaningful projects with clear tasks

  • Give rapid critical useful feedback

  • Quickly understand and root cause any issues the co-op student may encounter

  • Teach useful technical concepts and skills

    • Hands on learning for the co-op student

  • Commit at least 7 hours per week to supporting the co-op student, which includes daily syncs scheduled for at least 30 minutes

    • The remaining time is spent on support (e.g. planning, research and experimentation, reviews)

    • This is in addition to the time you already spend on WARG (e.g. subteam meetings, flight tests)

    • If there are periods of time where you are not able to fulfill this (e.g. exams), you must find another member to temporarily take these responsibilitiesThis is in addition to the time you already spend on WARG (e.g. subteam meetings, flight tests)

SDC criteria

TODO

To be a co-op supervisor we strongly prefer some managerial experience. This can include being a project manager or subteam lead at WARG. management is hard and we don’t want our managers to be learning for the first time on co-op students. in the past this has usually been subteam leads, but this really isn’t a requirement. Note that for F24 we are expanding into general members and advisors as possible co-op supervisors, but this needs to be backed up with clear signs of readiness.

...