> 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-tips.md).

# Application Tips

1. **Be Vigilant** - Look out for information on upcoming Tech Fleet projects by checking the [#project-openings](/resources/the-great-tech-fleet-discord-migration-video-tutorials/common-channels-in-tech-fleet-discord.md) channel and the [Tech Fleet Newsletter](/resources/quick-links/join-our-mailing-list.md).
2. **Follow & Contribute** - At Tech Fleet we believe that contribution = growth. Those who contribute should be awarded more opportunities to contribute further. Being a project observer is a great way of understanding the working dynamics of a Tech Fleet team and making a contribution to the community.
3. **Prepare for Agile and Service Leadership** - All Agile team mates are expert collaborators before anything else. People on Tech Fleet projects often must build a mindset of Agile and of Servant Leadership before they can fully succeed in teams and contribute their best work. Take the [Servant Leadership Masterclass](/training-openings/current-and-upcoming-program-openings/masterclass-openings.md) and read the [Agile handbook](/agile-training-portal/agile-handbook.md) before applying to maximize your success.
4. **Shadow shadow shadow!** - [Observers](broken://pages/Blh9wc6LQu7pcHQug9kK) gain advantage in Tech Fleet programs because they've seen the work happen on teams. We recommend you shadow for one full week, watching as many team meetings on one project that you can, so you get a full sense of the work ahead. Show in your application responses that you've shadowed, and your leads will be able to tell you've prepared for the apprenticeship program. 
5. **Apply apply apply!** - When project applications [open up](/training-openings/current-and-upcoming-program-openings/project-training-openings.md), they are for anyone wanting to apply. We don’t ask for a resumé or a portfolio. What we are most interested in is your willingness to learn and help others do the same. This sentiment should be reflected in your application. 
6. **Write with quality over quantity** -  [Check out the application questions to see how to prepare.](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training/application-questions.md) When you write your application responses, be sure to write detailed and concise answers with as much context as you can build. When leads look at your responses they only have these to go off, and your history in Tech Fleet, to decide whether you're a good fit to interview. So don't be afraid to show your passion, show your chops, show your gumption in these responses.

## 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-tips.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.