Screener questions

Screener Questions are a way to learn more about your job seekers during the application process. These questions should be formatted in JSON and posted to a URL so Indeed Apply can retrieve them.

Before you begin


  • You can provide a maximum of 500 questions. However, our data indicates that a sharp drop-off in conversion occurs when more than 20 questions are asked.
  • Questions files should be no larger than 1 MB.
  • Questions files are cached server-side by unique question URLs and refreshed hourly.
  • Use the en_US locale to format limit, min, or max. Use a period for the decimal point. Do not use thousands separators.
  • The format of type=date impacts how the application is passed to the third party as well as the parsing of min and max. The job seeker still enters the date based on their locale, not the specified format, and validation error messages are in their locale’s format.
  • For type=date, use yyyy instead of yy in the format to prevent confusion.

Note: Verify the syntax of your JSON file and preview the look of your screener questions using the Indeed Apply Questions tool.

Best practices

  • Only include questions that are relevant to the job.
  • Include as few screener questions as possible. Remember that job seekers will answer these questions on mobile devices.
  • Use the “pagebreak” question type to split your application into logical sections. Indeed inserts pagebreaks by default if none are included in your JSON, but this can split your application up in unintended ways.
  • Do not repeat questions that can be answered from a job seeker’s resume, or have already been collected during the Indeed Apply application process (e.g. basic contact details).
  • Follow local laws when determining which questions to ask. Consult your legal department about questions your local laws may prohibit.
  • Provide guidance to job seekers when answers require a specific format.

JSON for screener questions

This section lists the parameters used in building all question types. For examples of specific question types, refer to Screener question types.

JSON post example

The JSON post contains:

  • questions: the full questions list as described in the previous section
  • answers: the full answers list
  • url: the URL from which the questions were retrieved
  • retrievedOnMillis: the datetime in milliseconds at which the questions were retrieved

Click here to view or download a full example JSON post file.

Screener question types


A question that displays a multi-line text entry field. Used for questions with long-form answers.


A question that displays a single-line text entry field. Used for questions with shorter answers.

Note: Please see the examples below for more information on the different formats available for text questions: integer, decimal, numeric_text.


A question that displays a drop-down menu that allows the applicant to select a single answer. Used for questions with multiple choice answers.

Note: If you include 5 or fewer answer options, they will display as radio buttons. If you include more than 5 options, they will display in a drop-down menu.


A question that is or is not displayed based on responses to previous questions. For example, you might ask an applicant if they are at least 18 years of age. If they answer yes, you ask if they can provide required work documentation.


A question that displays additional questions and responses based on previously selected answers. For example, you might ask an applicant to choose a state. Then, depending on what they select, you could offer them a dropdown list of cities within that state. Each hierarchical question is limited to 3 levels, for example: state/city/county.

Note: Hierarchical questions are similar to conditional questions. However, hierarchical questions may be better suited to certain question types where an initial selection defines potential answers for subsequent questions. Using the hierarchical functionality reduces the total number of questions needed to obtain related information.


A question that displays a list of checkboxes that allows the applicant to select multiple answers. Used for questions with multiple answers.


A question that displays a text field that only accepts date entry. Used for questions that must be answered with a date.

Note: format is required when using this screener question type. The format must be dd/MM/yyyy or another locale specific format that meets Unicode CLDR formatting. Indeed uses the SimpleDateFormat, so month must be formatted as MM. Using mm will result in misconfiguration.


A question that displays a file upload interface. Used for questions that require a file upload as an answer, such as certifications, portfolios, or example work. As detailed in the Application data delivery options section, the answer data returned in the JSON POST request will contain 3 fields: contentType, data, and fileName.

Accepted file types: doc, docx, gif, jfif, jif, jpe, jpeg, jpg, pdf, png, rtf, tif, tiff, txt
File size limit: 5 MB (maximum combined limit per application is 15MB, including resume file.)

Note: Do not use this question type to acquire resumes. Instead, use the native “Resume” Indeed Apply configuration parameter.


A text display that does not require a response. Used to include explanatory text or provide section headings. You can include the following HTML elements in the text: <b>, <p>, <br>, <li>, <ul>, <ol>, <a href=" ">. (Only http and https protocols are allowed in URLs. Links open in a new tab.)

Note: Do not force line breaks. Indeed automatically inserts line breaks between paragraphs.


Used to group questions on a page. All questions included between two pagebreak types appear on the same page. You can group up to 20 questions on the same page.

Next steps