Develop and Post Leads open roles

mxajPrice commented 1 year ago

Overview

HfLA volunteers typically stay for 6-12 months, so we need a plan in place to regularly recruit new leads and mentors to keep this community going.

Action Items

[x] Update the open roles card
[x] Update the leads description
[x] Create a card for mentor recruitment

Resources/Instructions

PM CoP Lead role description

mxajPrice commented 1 year ago

DRAFT CARD

**Software Engineer Mentors Wanted!**

The Engineering Community of Practice is looking for mentors to help answer community questions about
- Software Engineering
- Career Development
- their Hack for LA projects

**Volunteer Opportunity**: Mentors for the Engineering Community of Practice. Get leadership experience at low stake environment. 

**Responsibilities include**: 
* Answering junior dev questions on Slack
* Attending one Mentor Night session a month to answer community questions
* Working with CoP leads to continue developing the Mentor program and the CoP

**Duration**:  Open-ended

**Who to communicate your interest to**
- Slack channel link: [#engineering](https://hackforla.slack.com/archives/C01CU709SER)
- Slack name of person to contact in the channel: ajPrice, Micah Elm, Alejandro Gomez, Harrison Katz

FIND OUT MORE INFORMATION HERE (link to wiki post below)

DRAFT WIKI POSTING

### Software Engineer Mentors Wanted!
_Posted on Developer Open Roles board [here](https://github.com/hackforla/engineering/projects/2)._

**Who we are**
The Engineering Community of Practice is a group of software engineers and technologists who are trying to make a positive impact on local communities and hone their professional skills. As a subset of [Hack for LA](https://www.hackforla.org/) (HfLA), we exchange information on Slack and [meet once a week](https://github.com/hackforla/engineering/wiki/CoP-Meetings) to network, discuss career goals, exchange knowledge, and have industry professionals share their experience with us.

**About the Mentor Role**
Most Hack for LA engineering volunteers are junior level and need help and guidance on their projects, best practices, and career development.  The role of our mentors is to engage with other engineers on Slack and at our monthly Mentor Night meeting to answer questions and empower those looking to start a new career, switch careers, or who just want deeper knowledge.

If you have joined Hack for LA to teach and lead, mentoring is right for you!

**Duties include...**
- Working with the [Engineering CoP leads](https://github.com/hackforla/engineering/wiki/Community#engineering-cop-leads) to nurture the community and mentorship program
- Interacting with the engineering community on [Slack](https://hackforla.slack.com/archives/C01CU709SER)
- Answering questions at [Mentor Nights](https://github.com/hackforla/engineering/wiki/CoP-Meetings#mentor-nights)

**Requirements for mentors**
- 3+ years professional (paid) software experience
- Specialist expertise (i.e. Front end, back end, data, security, testing, etc.)
- Availability on Slack and 1 CoP "Mentor Night" meeting a month

**Nice-to-haves, if you can say 'yes' to 2-3 of these that's great**
- A degree in the field
- Maintainer on a Github repo with >20 stars
- More that 3 published open source projects (e.g. you're the owner on Rubygems or NPM)
- Participated in the release of software you were paid to write
- Participated in the design of software you were paid to write
- A senior+ level title at an enterprise-level company
- Have managed other engineers
- Have participated in the hiring of other engineers
- Worked for more than 6 months at a significant tech company (e.g. but not limited to FAANG)

**Time commitment**
   - 2-3 hours a month
      - 1 50-minute Engineering CoP meeting a month
      - 1 or 2 15-minute meetings with leads to give feedback on CoP meetings a month
      - other time spent answering questions on Slack or working with leads on development as needed

**Who to communicate your interest to**
- Slack channel link: [#engineering](https://hackforla.slack.com/archives/C01CU709SER)
- Slack name of person to contact in the channel: ajPrice, Micah Elm, Alejandro Gomez, Harrison Katz

mxajPrice commented 1 year ago

Notes from mentors on Slack:

Judson 12:16 PM My suggestion would be to have a list of indicators - qualities that suggest someone as a mentor, with more being better. Maybe that could go in Nice to Haves, but on the one hand I'm loathe to say "every Hack for LA Eng Mentor will be X" and on the other I think "every mentor will have some of A-Z" and "Nice to Have" sounds like something you could do without.

Judson 12:26 PM Every one of the numbers below is plucked from the air. I think there's some lower limit to qualify, but I'm not sure what it should be. 3 Years of professional (i.e. paid) software experience. A degree in the field Maintainer on a Github repo with >20 stars (again, not sure about the number here) More that 3 published open source projects (e.g. you're the owner on Rubygems or NPM) Participated in the release of software you were paid to write Participated in the design of software you were paid to write A senior+ level title at a legitimate company (so much handwaving here...) Have managed other engineers Have participated in the hiring of other engineers Worked for more than 6 months at a significant tech company (e.g. but not limited to FAANG) Specialist expertise - e.g. Security testing, accessibility design, kernel programming, documentation - beyond "I read a blog post and played with it for a weekend" Try as I might, I don't think I can put together an exhaustive list. Longer term, I'd want people who felt like they could be mentors but can't provide credentials from a list to be able to propose equivalent experience or expertise for addition.

mxajPrice commented 1 year ago

DRAFT LEADS CARD

### Engineering CoP Community Lead - Mentor Coordinator

**Volunteer Opportunity:** The Hack for LA Engineering Community of Practice is in need of a Community Lead to help organize Mentor Nights. A community lead is someone who can roll up their sleeves and create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success.

**Duration:** At least 6 months

**Time commitments:** 5-6 hours a week
- 1 50-minute Engineering CoP meeting a _week_ - Thursdays
- 1 25-minute Engineering CoP leads meeting a _week_ - Thursdays
- 1 50-minute HfLA CoP leads meeting a _month_ - First Wednesdays
- 3-4 hours of task work a _week_

**Who to communicate your interest to**
- Slack channel link: [#engineering](https://hackforla.slack.com/archives/C01CU709SER)
- Slack name of person to contact in the channel: ajPrice, Micah Elm, Alejandro Gomez, Harrison Katz

[GO HERE FOR MORE INFORMATION.](link to wiki post below)

DRAFT WIKI POSTING

### Engineering CoP Community Lead - Mentor Coordinator
The Hack for LA Engineering Community of Practice is in need of a Community Lead to help organize Mentor Nights. A community lead is someone who can roll up their sleeves and create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success.

About Mentor Nights
There are four kinds of meetings we host for the weekly CoP meetings: the Speaker Series, Lightning Talks, Open Networking, and Mentor Nights.  Mentor Nights happen once a month and are scheduled at the Engineering CoP Leads meetings which happen after every Engineering CoP meeting on Thursdays.  At the Mentor Nights meetings we have our [mentors](https://github.com/hackforla/engineering/wiki/Community#engineering-cop-mentors) on-call to answer questions from the community.

General duties of community leads (these responsibilities are shared with the other leads):
* Keeping [wiki](https://github.com/hackforla/engineering/wiki) documentation up-to-date
* Maintaining the [CoP Project Board](https://github.com/hackforla/engineering/projects/1)
* Welcoming new Engineers on Slack after every onboarding
* Analyzing and improving programming for community
* Creating agendas for the weekly [CoP](https://github.com/hackforla/engineering/issues/58) and [CoP Leads](https://github.com/hackforla/engineering/issues/42) meetings
* Participating in monthly planning meetings with the other CoP leads (UX/UI, Ops, Engineering, Data Science)
* Onboarding/Offboarding other Engineering CoP leads

Mentors Coordinator duties:
* Planning and leading Mentor Nights
* Coordinating mentor team
* Recruiting mentors
* On-boarding and off-boarding mentors

Skills needed or willing to be learned:
* Creating GitHub issues
* Kanban management
* Agenda creation
* Creating and managing Zoom rooms
* Editing GitHub wikis
* Team communication

Time commitments: 5-6 hours a week
* 1 50-minute Engineering CoP meeting a _week_ - Thursdays
* 1 25-minute Engineering CoP leads meeting a _week_ - Thursdays
* 1 50-minute HfLA CoP leads meeting a _month_ - First Wednesdays
* 3-4 hours of task work a _week_

Who to communicate your interest to
- Slack channel link: [#engineering](https://hackforla.slack.com/archives/C01CU709SER)
- Slack name of person to contact in the channel: ajPrice, Micah Elm, Alejandro Gomez, Harrison Katz

hackforla / engineering