First Week Retro + Finalize Recruiting Meeting

Misc Stuff

After-Hours

• First week of month Thursday 7PM work?

• Members speak?

Membership

• Can all project leads help us make a membership list?

First Week Retro

How did it go?

Trends

• First meeting was ight….lot of members were at career fair

• 15 new people

• Looking forward to next week’s meeting

• Goal is to get things going next week

API/Platform

• 40 people at API/Platform meeting

• 25 RSVPs

• Introduced people to team processes

• Meeting w/ David on Tuesday

Planner

• 50 ish people

• Did walkthrough of product

• Handful of super enthusiastic people

• Most people were there for meeting

Jupiter

• 30 people

• Talked about what Jupiter has now

• Not a lot of returning members

• Somewhat equal distribution of engineering, design, and product

• 2 people ask “how can I get started”

Design

• 18 people showed up

• Got a lot of newbies

• Worried about hand-holding new designers

• Won’t know until applications

Engineering

• 60 people

• Didn’t get a super good feel of the room on experienced / inexperienced

Product

• 20 people

• Good for Friday evening

• Mix of returning + newbies

• Lot of graduate students

• Good enthusiasm

Team Capacity

How many people can each team support?

• Eng

• Product

• Design

What type of people can each division support?

• How many new

• How many cracked

How many people can each division head support?

Officers help newbies idea?

Goal is to have a “max capacity” number for people in the org

API/Platform

• As many as possible

• Level-based structure

• 3 returning + Ahad

Trends

• Want 5-6 people in each division

  • Most team members are coming and going

  • Sees 2-3 people at any given time

• Product

  • 4 returning people

  • Sharon was thinking 4 people

• Design

  • 2 returning people

    • People seem enthusiastic but not the most responsive

    • Recurring meeting time might solve the problem

• Engineering

  • 1 returning person

Jupiter

• 1 returning engineer & 1 returning designer

• Have product meeting Friday

• Can take 5 more engineers

  • 2 engineers currently doing stuff | experienced?

• Goal is to get inexperienced people working on Jupiter to learn NextJS + up to speed

  • 3 experienced 2 new

Planner

• 6 returning engineers

  • 3 committed

  • 3 iffy

• Looking for 3 committed engineers

• May have space for 1-2 inexperienced people

• Want 3 total PMs

  • Have 1 PM

  • Want at least 1 experienced PM

• Want 2 designers

  • 1 experienced

  • 1 not experienced

  • Most work is for improving existing designs

Idea: officers help new engineers

Kevin: will this create a bad experience for new engineers?

David: we can give them a basic ticket & help them out

Josh: not super sure if this will be useful for me?

• Level system will address

Jason: working in small groups w/ new people

• Help them w/ whatever they need

David: hold workshops based on what we see from helping new people

William: would be down to have new people

Jason: after we hit cap, tell people they can contribute but can’t support you as much as we’d want

Ruben: don’t mind but was planning on doing it anyway

Kevin: have some people interested in pair programming

• Be down

Josh: level system

• Put people into levels

• Let them slowly move up the levels

Jake: how to poll people’s experience?

• Josh: tell people to sort themselves into levels

Jason: maybe apply this to the organization?

Consensus

• Put what people are comfortable doing

  • No idea how to start

  • Small feature

  • Large feature

  • Can do anything given to them

Do we do this for all divisions?

• Hilary: not bad but for design I want to know more

Do we allow people to do multiple roles & multiple divisions

• Do 1 for now, let people to do multiple on a per-individual basis

Recruiting Strategy

Questions to answer

• What type of people are we looking for?

• How are we going to structure the interest form?

• Are we rejecting people?

• How are we matching people onto teams?

How do we filter?

• Caleb: First come first serve?

  • Group: okay nope xD

• Filter based on experience

Jupiter

• Few people interested in design

API

• 1 or 2 people interested

Prefer design over engineering

How do people get put on projects?

Jason

• Eng

  • Skills