Example of JobPosting qualifications as EducationalOccupationalCredential

From Talent Marketplace Signaling Community Group
Jump to: navigation, search
Talent Signal
Wiki Navigation
Main Page
Issues, use cases and requirements
Other useful links
Community group home page
email list for group
relevant work elsewhere
Issue Description: Provide examples of using the schema.org type EducationalOccupationalCredential as a value for the qualifications property of a JobPosting.

Discussion: see maillist for June 2019, thread on Example for JobPosting qualifications as EducationalOccupationalCredentials.

  • Definition of qualifications is: "Specific qualifications required for this role or Occupation." The expected type of the value is Text or EducationalOccupationalCredential
  • Definition of EducationalOccupationalCredential is "An educational or occupational credential. A diploma, academic degree, certification, qualification, badge, etc., that may be awarded to a person or other entity that meets the requirements defined by the credentialer."
  • Build on the example provided of an Occupation requiring a PhD level qualification.


Status: Done in schema.org release 3.9 Aug 2019 (see issue 2294 and PR 2295).

While the EducationalOccupationalCredential schema.org type is able to describe specific credentials/qualifications that are offered (e.g. a Bachelor degree in Software Engineering from a your favourite University) it can also be used to describe generic classes of credential. For example :

  • the name of the credential/qualification may be provided
  • the credentialCategory property (ie the category or type of credential being described, for example "degree", "certificate", "badge", or more specific term --schema.org/credentialCategory) may be used to specify that a "Bachelor of Science" is required,
  • the about property can be used to specify the subject matter of the content, in this case of the BS degree.
  • the recognizedBy property may be used to specify "An organization that acknowledges the validity, value or utility of a credential." --schema.org/recognizedBy. This is useful where the quality assurance or accreditation of a credential is important in distinguishing which credentials are acceptable.
  • other information such as educationalLevel and validIn may be provided where relevant.
  • much of this information may be provided as free text values, url links to concepts or schema.org DefinedTerms depending on the balance of specificity versus risk of a concept scheme not be recognised.

Example 1: Job requires a Bachelors degree in computer science

Based loosely on the Junior software developer example, but does not attempt to represent all the alternatives prescribed.

  "@context": "http://schema.org/",
  "@type": "JobPosting",
  "title": "Systems Research Engineer",
  "qualifications": {
    "@type": "EducationalOccupationalCredential",
    "credentialCategory": "Bachelor of Science",
    "about": "Computer Science",
    "recognizedBy": {
      "@type": "Organization",
      "name": "ABET",
      "url": "https://www.abet.org/"