> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/initiatives/launchpad.md).

# Launchpad

Launchpad is μLearn's skills-first hiring platform where students showcase Proof-of-Work and companies hire based on verified skills not academic marks. No CGPA filters. No backlog barriers. Skills over scores.

### <mark style="color:$primary;">What It Is</mark>

Launchpad is μLearn's integrated skills-first hiring platform where students showcase Proof-of-Work (PoW) and companies hire based on verified skills not academic marks.

*Skills > scores. Geography doesn't limit opportunity.*

### <mark style="color:$primary;">How It Works</mark>

Launchpad operates through two hiring modes:

<mark style="color:$primary;">**General Mode**</mark>\
Companies access the pre-vetted talent pool filtered by domain, skill tags, and Karma bands. Students who have toggled "Open to Work" on their μID appear in the pool. Fast. Browse and shortlist instantly.

<mark style="color:$primary;">**Challenge Mode**</mark>\
Companies define a custom task. Only students who complete that specific task become eligible for that role. Focused. Best for niche or specialized roles.

<table><thead><tr><th width="130">Feature</th><th>General Mode</th><th>Challenge Mode</th></tr></thead><tbody><tr><td><strong>Eligibility</strong></td><td>Open to Work + domain match + Karma band</td><td>Complete company's custom challenge</td></tr><tr><td><strong>Speed</strong></td><td>Fast  browse pool instantly</td><td>Focused review challenge submissions</td></tr><tr><td><strong>Best for</strong></td><td>Internships, entry-level, continuous hiring</td><td>Niche, specialized, senior roles</td></tr></tbody></table>

{% stepper %}
{% step %}

### <mark style="color:$primary;">Student Journey</mark>

1. Join μLearn and select Interest Groups
2. Complete structured tasks and levels
3. Build PoW projects and earn Karma
4. Build μID profile, link GitHub, Behance, portfolio
5. Toggle **"Open to Work"**
6. Apply for General roles or complete Company Challenges
7. Shortlist → Interview → Offer

**Pre "Open to Work" checklist:**

* 3+ PoW tasks/projects with clear READMEs
* GitHub/Behance/portfolio links added
* Mentor/peer validation done Karma updated
* Professional summary added on μID
  {% endstep %}

{% step %}

### <mark style="color:$primary;">Company Journey</mark>

* Create company account on mulearn.org
* Add recruiter profiles
* Post role via General Mode or Challenge Mode
* Shortlist → unlock candidate contact → schedule interview → offer
* Close cycle and share outcomes
  {% endstep %}

{% step %}

### <mark style="color:$primary;">Core Philosophy</mark>

* No marks, no certificate screens only PoW
* μID - digital skill portfolio
* Karma - skill currency earned only via validated PoW
* Contact info stays private until shortlist
* Equal opportunity backlogs and CGPA don't block eligibility
  {% endstep %}
  {% endstepper %}

> **Manual Intervention:** Company onboarding and partnership agreements are managed by the μLearn core team. Contact \[partner inquiry form].

[**Access Launchpad →**](https://mulearn.org/careers)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mulearn.org/initiatives/launchpad.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.