> For the complete documentation index, see [llms.txt](https://help.prentus.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.prentus.co/common-use-cases/evaluate-job-search-materials.md).

# Evaluate Job Search Materials

Use Case: 

* Evaluate the Overall Effectiveness of My Approach, Materials, etc. Using Prentus' Data

Need: 

* To Understand and Evaluate how effective the job seeker's current methodologies and materials are - particularly for specific time periods.
* More specifically, to evaluate the rate of conversion from initial application to early interviews, offers, etc. (or, conversely, how ineffective one's current approach is). 

Execution:

1. Advance any job you've applied to from "Applied" to "Interviewing"
   1. Job Search > Job Tracker > "List"/"Board" view
   2. Select "View" and then select "Applied" button at the top of the job card; select "interviewing", etc
2. Return to Job Tracker and select "Trends" tab to compare the number of jobs you've applied to with the number that have chosen to move forward (and to what stage)
3. Make adjustments to your cover letter, follow-up messaging, interview techniques etc and assess their positive or negative impact over time (bearing in mind changes in the general job market, economy, etc. as well).


---

# 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://help.prentus.co/common-use-cases/evaluate-job-search-materials.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.