> For the complete documentation index, see [llms.txt](https://participanthelp.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://participanthelp.dscout.com/interview-studies/participate-in-interview-studies/what-is-an-interview-study.md). # What is an interview study An interview study is a research session that lets you engage in remote video with researchers. Instead of recording a selfie-style video of yourself on your mobile device, you’ll be face-to-face with your study leader(s) either on your phone or laptop (you'll be told ahead of time which device you should use!). As opposed to typing out a response in the mobile app, an interview study lets you answer questions, expand on your thoughts, and provide additional context in real time. Some interview sessions scouts have participated in the past include: * Giving Dscout employees feedback on how to make the Dscout app better * Showing researchers their new tattoos * Explaining what is frustrating and confusing about new products and software {% hint style="info" %} **Note:** Applying to interview sessions works the same way as applying to diary studies. When you browse open studies in the **Explore** tab, read the overview before you apply to see whether it's an interview study. Researchers may also ask whether you’re comfortable with a video call. {% endhint %} Check out these articles to learn more about interview studies and their technical requirements: * [Interview browser compatibility](/interview-studies/interview-technical-requirements/interview-browser-compatibility.md) * [Participating in interview studies](/interview-studies/participate-in-interview-studies/participating-in-interview-studies.md) * [Mobile interview: Walkthrough + Guidelines](/interview-studies/participate-in-interview-studies/mobile-interview-participation-guidelines-walkthrough.md) --- # 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://participanthelp.dscout.com/interview-studies/participate-in-interview-studies/what-is-an-interview-study.md?ask=&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.