Org Chart and Role Descriptions - cs428TAs/w2025 GitHub Wiki

<-- back to PriceMD

Organization Chart

PriceMD is split into three sub-teams: data, front end, and back end.

org_chart_2 drawio

Roles

Here are the role requirements for each team member, organized by sub-team:

Data

Caleb

  • Collecting data from diverse sources
  • Build, test, and maintain scalable data
  • Extract, transform, and load data from various sources into centralized system

Elaine

  • Coordinates with Sophie to implement data automation
  • Build, test, and maintain scalable data
  • Extract, transform, and load data from various sources into centralized system

Jaclyn

  • Data team lead - associated coordination/managerial tasks
  • Management/communication lines with other team members
  • Cleaning and analysing duplicated data
  • Building data pipeline
  • Build, test, and maintain scalable data
  • Extract, transform, and load data from various sources into centralized system

Sophie

  • Coordinates with Elaine to implement data automation
  • Build, test, and maintain scalable data
  • Extract, transform, and load data from various sources into centralized system

Front End

Clayton

  • Building and arranging UI components
  • Touch-up and polish existing UI for a cohesive look
  • Coordinates with Hayden to implement UI
  • Coordinates with Olivia to develop components

Hayden

  • UI/UX head designer
  • Customer interfacing/satisfaction, user requirements
  • Frontend Product Manager
  • Communicates with end user as well as other team members

Olivia

  • Building and arranging UI components
  • Touch-up and polish existing UI for a cohesive look
  • Coordinates with Hayden to implement UI
  • Coordinates with Clayton to develop components

Yirang

  • Front end team lead - associated coordination/managerial tasks
  • Primary front end architect
  • Developing and implementing UI
  • API integration with backend

Back End

Jonathan

  • Back end team lead
  • Make decisions with Architect on the stack and design of backend deliverables
  • Divvy up tasks for the backend team and pull in other developers as needed
  • Can report on progress in backend to Project Manager (who happens to also be on the backend team)

Matheus

  • Chief Architect/Backend developer
  • Make overall design for contracts between code from the three teams
  • Contact point for software design questions between teams
  • Communicates with project manager and other team leads as needed to make sure software design is on track

Rebekah

  • General Project Manager/Backend developer
  • Manages team meetings and follows up on deliverable progress, conducts status reports
  • Helps steer project progress to make sure it lines up with end-user requirements
  • Communicates with team leads for tracking progress