> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training/application-requirements.md).

# Application Requirements

## What you don't need: 

1. A degree
2. A resume 
3. A portfolio
4. Prior experience (even as a lead)

## What you should have:

### Completed Actions in Tech Fleet

1. Previously [observed project teams ](/observer-portal/observer-handbook.md)
2. Previously taken the [Servant Leadership Masterclass](/training-openings/current-and-upcoming-program-openings/masterclass-openings.md)
3. Read the [Apprentice Handbook](broken://pages/a2A9YzBut11QBik2J35T), [Co-Lead Handbook](broken://pages/qQQQDM2X1X3sFoxVeIQm), [Agile Handbook](/agile-training-portal/agile-handbook.md),  [Guidelines](/policies/community-collective-agreement.md), and info about [Life in Tech Fleet](broken://pages/X02zGIHf5xWPBi9b719d)
4. Understand what [questions ](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training/application-questions.md)we ask when applying
5. Complete both the [General and Project Phase Applications](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training/how-tech-fleet-project-applications-work.md)

### Built Experiences and Mindsets

1. A passion for philanthropy and peer-to-peer collaboration
2. A willingness to put in the time and energy in the program
3. Ability to commit an average of 15 to 20 hours to the project phase as part of a team
4. Prior education-building foundation (bootcamp, cert, school, self-training)
5. Knowledge about your role
6. Knowledge about Agile philosophies
7. Knowledge about Servant Leadership

## Head to the Next Lesson


---

# 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 dynamically by asking a question.

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

```
GET https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training/application-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.