# Core Team Selection

This document serves as a step-by-step guide for **Campus Leads** to build a strong, diverse, and mission-aligned core team for their TinkerHub campus chapter. It includes multiple strategies tailored for both existing and new communities and also covers the First-Year Coordinator onboarding.

### [Core Team Roles (as defined by TinkerHub)](/campus-community/campus-communities/campus-structure.md#campus-core-team)

### When to Begin

* Ideally, **within the first month, or deadline set by TinkerHub Foundation** 
* Plan completion: **within 2–3 weeks** after open call.

**One Major Note**

Before every nomination and voting, it is important that the campus lead presents the roles and responsibilities, mission, and vision of each role in the core team, so that either the voting community or the selection committee gets a clear picture, and makes an unbiased decision.

### Two Scenarios

### 1. New/Inactive Community

If you're starting from scratch or restarting an inactive chapter.

 **3-Stage Selection Process**

**1. Application Form (**[**Google Form Template**](https://docs.google.com/document/d/1GPrP3FsaoB42ddPeqUkKGyjtkCz8ealTWSaqV9mHjdk/edit?usp=sharing)**)**

* Collect basic info + motivation.
* Ask for specific inputs:
  * Past involvement in tech/leadership/volunteering
  * Interest in particular roles (Learning, Outreach, WIT, First Year)
  * Availability for 6–10 months

**2. Skill-Based Task Round**

* **Learning Coordinator**: Propose a sample Study Jam plan (topic, audience, timeline).
* **Outreach Lead**: Design a poster or social media campaign idea.
* **WIT Fellow**: Share ideas to promote inclusivity.
* **First Year Coordinator**: Suggest how they’d onboard 50+ new students in 30 days.

**3. Interview**

* Panel interview with a faculty mentor, alumni of campus or senior tech club member (if any).
* Focus on:
  * Team spirit
  * Problem-solving
  * Communication
  * Passion for community work

**Bonus Tip**: Invite external reviewers like Council or leads from other campus community or alumni.

#### 2. Active Community

If your campus already has an active TinkerHub presence.

**Community Nomination & Interview**

1. Open **peer nominations** with short pitches.
2. Community can vote for the candidates based on their pitch. 

***

### Selecting the First Year Coordinator (Special Case)

> **Note:** First-year students usually join later, so this role is selected separately **2–3 months** into the academic year.

#### Suggested Process:

1. **Host a Beginner-Friendly Program**
   * Example: Intro to TinkerHub, Tech 101, Icebreaker Jam.
2. **Observe Participants**
   * Look for curiosity, consistency, and engagement.
3. **Shortlist and Talk**
   * Have an informal chat with potential candidates.
4. **Trial Task**
   * Let them co-lead a follow-up activity (e.g., onboarding batchmates).
5. **Final Onboarding**
   * Add to core team officially after trial phase.

### For Arts and Science Colleges

Including members from multiple departments is mandatory in core team. This ensures that cross-departmental interests and concerns gets reflected within the core team, and is considered during program design and community engagement. 

***

### Best Practices for Core Team Formation

* **Diversity Matters**: Actively look for gender, stream, and year diversity.
* **Use Feedback**: Ask current/ex team or foundation mentors for input.
* **Document Everything**: Save forms, selections, and notes for transparency and continuity.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.tinkerhub.org/campus-community/campus-communities/campus-structure/core-team-selection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.