watonomous.github.io

1. Knowledge Base
2. Knowledge Base Home
3. Management Tools & Training

[ Knowledge Base : Job Title Definitions ]

Created by [ Rowan Dempster] on Dec 24, 2019

The following are the job descriptions for all roles in WATO, along with the associated job descriptions

Team Captain

• Leads the Team
• Ensure the success of SAE competition
• Responsible for
  • Coordinating the work done by the Software, Electrical, Business and Mechanical organizations and incorporating it together for the final product, arranging
  • Biweekly test track visits to test the entire product
  • Reading all discord messages
  • All external relations
• Conducts
  • Weekly director meetings
  • Biweekly one-on-ones with all directors
  • Biweekly All Hands meeting, reporting on the overall status of the product
  • Monthly WATO-wide social
  • Termly WATO-wide offsite

Director

• Leads a Division (Software, Electrical, Mechanical, and Business)
• Responsible for
  • Coordinating and incorporating the work done by all reporting Group for each test track visit
  • Creation, Management, and Tracking of Objectives & Key Results
    • Directors will be prioritizing the OKRs
  • Forwarding financial requests
  • Assisting business for recruitment for their organization
  • Ensuring the health of the organization’s work and acting as a Technical Lead for any immediately urgent problems affecting the entire organization (eg. Software pipeline is broken)
  • Acting as a Technical Lead for newly formed Teams where there is no pre-existing work
• Conducts
  • Weekly Organization meetings with all Managers and Technical Leads in the Organization
  • Bi-weekly one-on-ones with all Managers and Technical Leads in the Division
  • Monthly socials for Managers and Technical Leads within the organization
  • Completing admin/managment tasks assigned in Directors' meeting

Manager

• Leads a Group
• A Group should consist of between 5 to 20 active members
• Responsible for
  • Ensuring that the work being done by the team fits in with the “bigger picture” and is compatible with work done by other teams. Cross-team integration
    • Software: Specifically, they would be responsible for integrating their team’s work to the software production pipeline in the test track. This means they should all know how to deploy, run, and test the software pipeline in the car
  • Assignment of Technical Leads to Objectives & Key Results if Technical Leads exists.
  • For smaller groups, Managers will be directly assigning OKRs to core members.
  • Assignment and prioritization of tasks
  • Conducting interviews for potential new members
  • Ensuring the health of the Team’s work and acting as a Technical Lead for any immediately urgent problems affecting the entire Team (eg. Processing nodes are broken during the competition)
  • Acts as a Core Member
• Conducts
  • Weekly Group-wide work sessions
  • Weekly one-on-ones with all Technical Leads and Core Members in the Group during work sessions
  • Monthly group socials

Technical Lead

• Leads one or more Key Result of an Objective
• There should be between 1 and 3 technical leads per Group
• Responsible for
  • Research
  • Architecture
  • Maintaining technical documentation (Code documentation, Phabricator, etc)
  • Creation of tasks / tickets for their responsible OKRs
  • Reviewing pull requests related to an Objective & Key Result
  • Training and onboarding core members

Core Member

• Assigned to work on one or more Key Results of an Objective
• Core Members can reject work if no tickets are created for them
• if you are interested to do something, all you need to do is ask
• core member can participate in all of the above
• core members can attend any meeting in WATonomous

Document generated by Confluence on Nov 19, 2021 12:21

Atlassian