# Make Team Contributor - Career Pathway > **[[03 - Contributors]]** → WordPress Community > Related: [[Meetup Organizers]], [[WordCamp Organizers]], [[Open Source Contributors]] > Prerequisites: WordPress knowledge in specialized area ## Role Overview Make Team Contributors improve WordPress through community teams: Core, Design, Mobile, Accessibility, Polyglots, Support, Documentation, Themes, Plugins, Meta, CLI, TV, Community, Training, Test, Tide, Openverse, Photos, Hosting, Marketing. **Compensation**: Volunteer (career advancement benefit) | **Time**: 2-10 hours/week | **Impact**: Shape WordPress future --- ## ENTRY LEVEL (0-6 months) ### Getting Started 1. **Choose a Team**: Match skills to team needs - **Core**: Code contributions to WordPress itself - **Design**: UI/UX for WordPress - **Training**: Educational content - **Support**: Help users in forums - **Polyglots**: Translate WordPress 2. **First Contributions**: Small, guided tasks 3. **Learn Processes**: Each team has workflows 4. **Build Relationships**: Get to know team members ### Skills Demonstrated ✅ Follow team processes ✅ Complete assigned tasks ✅ Communicate effectively ✅ Accept feedback gracefully ✅ Collaborate asynchronously ### Contribution Examples - Answer 10 support forum questions - Submit 5 documentation improvements - Translate 500 strings - Fix 3 minor bugs - Design 1 UI component ### Ready for Regular Contributor? - [ ] Understand team workflows - [ ] Complete contributions independently - [ ] Attend team meetings regularly - [ ] Build trust with team members - [ ] Self-assign appropriate tasks **Time Investment**: 2-5 hours/week --- ## MID LEVEL (6 months - 2 years) ### Regular Contributor - Attend weekly meetings consistently - Take on larger tasks - Review others' contributions - Help onboard new contributors - Propose improvements ### Skills Demonstrated ✅ Lead initiatives ✅ Mentor new contributors ✅ Make architectural suggestions ✅ Resolve disagreements constructively ✅ Represent team in discussions ### Contribution Examples - Lead documentation project - Triage 50+ support tickets - Review 20+ code patches - Organize team sprint - Coordinate translation effort ### Ready for Team Leadership? - [ ] Consistent contributor for 1+ years - [ ] Trusted by team members - [ ] Demonstrate leadership - [ ] Manage projects effectively - [ ] Handle conflicts maturely - [ ] Nominated by current leaders **Time Investment**: 5-10 hours/week --- ## SENIOR LEVEL (2-5 years) ### Team Rep / Component Maintainer - Represent team in cross-team discussions - Make decisions on behalf of team - Maintain specific WordPress components - Set team direction and priorities - Recruit and mentor contributors ### Skills Demonstrated ✅ Strategic thinking ✅ Build consensus ✅ Represent community values ✅ Balance competing priorities ✅ Grow team health and culture ### Ready for Team Leadership? - [ ] Consistent senior contributor 2+ years - [ ] Demonstrated leadership - [ ] Community respect - [ ] Available commitment (10-15 hours/week) - [ ] Nominated and approved by team **Time Investment**: 10-15 hours/week --- ## LEADERSHIP (5+ years) ### Make Team Lead - Set team vision and strategy - Lead weekly meetings - Final decision authority - Represent team to WordPress leadership - Grow and sustain team ### Other Leadership Paths - **Release Lead**: Lead WordPress releases - **Component Maintainer**: Own WordPress subsystem - **Working Group Lead**: Cross-team initiatives - **Core Committer**: Commit authority to WordPress Core **Time Investment**: 15-20 hours/week --- ## Career Benefits ### Professional Development - Deep WordPress knowledge - Leadership experience - Public portfolio of contributions - Network with WordPress leaders - Speaking opportunities ### Career Advancement - **Hiring Advantage**: Contributions prove skills - **Network Effects**: Jobs through community connections - **Reputation**: Known in WordPress ecosystem - **Skills**: Project management, collaboration, technical depth - **Visibility**: Conference invitations, job offers ### Documented Impact - WordPress.org profile shows contributions - GitHub profile (for code contributions) - Make blog posts under your name - Conference presentations - Project leadership --- ## Getting Started ### Choose Your Team **Match Skills to Teams:** | Your Background | Recommended Teams | |----------------|-------------------| | Developer | Core, CLI, Themes, Plugins | | Designer | Design, Training (visual content) | | Writer | Documentation, Training, Support | | Multilingual | Polyglots | | Community Builder | Community, WordCamps, Meetups | | Marketer | Marketing | | DevOps | Hosting, Meta | | QA/Testing | Test, Tide | ### First Steps 1. **Read Team Handbook**: make.wordpress.org/[team] 2. **Join Slack**: WordPress.org Slack, find team channel 3. **Attend Meeting**: Introduction, listen first 4. **Claim Small Task**: Look for "good first issue" 5. **Ask Questions**: Team members are friendly 6. **Complete Task**: Follow guidelines 7. **Iterate**: Based on feedback ### Time Commitment - **Minimum**: 2 hours/week to maintain involvement - **Active**: 5-10 hours/week for regular contributions - **Leadership**: 15-20 hours/week for team lead roles --- ## Balancing Contribution with Career ### While Employed - **Employer Support**: Some companies give contribution time - **Personal Time**: Nights/weekends common - **Boundaries**: Don't burn out - **Strategic**: Align contributions with skill development ### As Freelancer - **Marketing**: Contributions build reputation - **Network**: Leads to clients - **Skills**: Stay technically sharp - **Downtime**: Contribute between projects ### Career Transitions - **Automattic**: Hiring preference for contributors - **WordPress Companies**: WP Engine, Yoast, etc. value contributors - **Speaking Circuit**: Conference invitations - **Consulting**: Authority from contributions --- ## Success Stories **Example Paths:** - Support forum contributor → Automattic Happiness Engineer - Core contributor → Senior WordPress Engineer at agency - Training team member → Developer Advocate - Polyglots coordinator → International team lead - Design contributor → Product Designer at WordPress company --- ## Ongoing Engagement ### Staying Active - Attend WordCamp Contributor Day - Participate in team sprints - Join async discussions on Slack/GitHub - Attend annual community summit - Speak about your contributions ### Growing Impact - Mentor new contributors - Lead initiatives - Cross-team collaboration - Innovation and experimentation --- ## Success Metrics **Entry**: First contribution within 1 month, 5+ contributions in 3 months **Mid**: Regular contributor, attend meetings, 50+ contributions/year **Senior**: Team rep role, lead projects, mentor others **Leadership**: Team lead, shape WordPress direction, 15+ hours/week --- ## Next Steps **Starting?** → [[Choose Your Make Team]] → [[First Contribution Guide]] **Active?** → [[Lead a Project]] → [[Mentor New Contributors]] **Leading?** → [[Team Lead Handbook]] → [[WordPress Leadership]] *Updated: 2025*