# Getting hired

- [Preparing to find a job](https://howtocode.trek.io/topics/getting-hired/preparing-to-find-a-job.md): Learn everything you need to know about preparing to find a job.
- [Plan a strategy](https://howtocode.trek.io/topics/getting-hired/preparing-to-find-a-job/plan-a-strategy.md): You've got to have a plan or you'll find yourself spamming your resume out to every job post on every job board and wondering why you haven't had any success.
- [What companies want](https://howtocode.trek.io/topics/getting-hired/preparing-to-find-a-job/what-companies-want.md): Companies are looking for someone who can add value as soon as possible and who will be able to grow with the organization.
- [Get yourself together](https://howtocode.trek.io/topics/getting-hired/preparing-to-find-a-job/get-yourself-together.md): You should have at least an informal list of the things that matter to you. Now ruthlessly rank them. What are your non-negotiables and what are your nice-to-haves?
- [How to prepare](https://howtocode.trek.io/topics/getting-hired/preparing-to-find-a-job/how-to-prepare.md): You may be uncomfortable "selling yourself" but that's exactly what you'll have to do.
- [Project: Make your website](https://howtocode.trek.io/topics/getting-hired/preparing-to-find-a-job/project-build-a-personal-website.md): In general, it's best to keep your site simple and clean. Let your portfolio of work speak for itself.
- [Applying and interviewing](https://howtocode.trek.io/topics/getting-hired/applying-and-interviewing-for-a-job.md): Learn everything you need to know about applying and interviewing for a job.
- [Qualifying leads](https://howtocode.trek.io/topics/getting-hired/applying-and-interviewing-for-a-job/qualifying-leads.md): Part of the reason for qualifying the leads is to make sure you don't get sucked into a process and waste a bunch of time applying to jobs that you wouldn't actually take anyway.
- [Project: Make your resume](https://howtocode.trek.io/topics/getting-hired/applying-and-interviewing-for-a-job/project-make-a-developer-resume.md): A developer's resume is an interesting thing because so much of your value is demonstrated from your projects, which live in your GitHub (and are hopefully also deployed somewhere online).
- [Applying for jobs](https://howtocode.trek.io/topics/getting-hired/applying-and-interviewing-for-a-job/applying-for-jobs.md): Start with companies that you're on the fence about. Once you feel comfortable with your application-sending and hopefully interviewing abilities, start tackling your top choices.
- [Preparing for an interview](https://howtocode.trek.io/topics/getting-hired/applying-and-interviewing-for-a-job/preparing-for-an-interview.md): You'll want to figure out the questions you might expect to be asked (and the general responses you'll have for each which demonstrate your brilliance) and you'll want to research the company too.
- [Handling an offer](https://howtocode.trek.io/topics/getting-hired/applying-and-interviewing-for-a-job/handling-an-offer.md): Do not accept right away. This is doubly true if you don't think it's a good offer.
- [Final words](https://howtocode.trek.io/topics/getting-hired/applying-and-interviewing-for-a-job/final-words.md): Build some awesome software, learn as much as you can, and pay it forward when you're able to.


---

# 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://howtocode.trek.io/topics/getting-hired.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.