> 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/interview-technical-requirements/technical-requirements-for-interviews.md).

# Technical requirements for interview studies

Your computer must have a few things for desktop interviews to work properly. This includes:

1. **Working speakers (or headphones you can use), camera, and microphone.** If you don’t have a built-in camera or microphone, external ones will work just fine.
2. **Google Chrome or Microsoft Edge web browser.** You'll need to install and use Chrome or Edge as your browser during your [Interview pre-test](/interview-studies/interview-technical-requirements/interview-pre-test-scout-overview-troubleshooting.md) and session.
3. **A strong internet connection.** During your interview pre-test, you'll be asked to test your internet connection. If the indicator turns yellow or red, consider moving closer to your WiFi router or connecting to your internet via ethernet cable.

For mobile interview requirements, check out [this article](/interview-studies/participate-in-interview-studies/mobile-interview-participation-guidelines-walkthrough.md).

If you run into any issues with these steps, reach out to our Support team [here](https://help.dscout.com/hc/en-us/requests/new) for assistance.


---

# 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/interview-technical-requirements/technical-requirements-for-interviews.md?ask=<question>&goal=<user_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.