Note: you are viewing the development version of schema.org. See How we work for more details.

Occupation

Thing > Intangible > Occupation

A profession, may involve prolonged training and/or a formal qualification.
PropertyExpected TypeDescription
Properties from Occupation
educationRequirements EducationalOccupationalCredential  or
Text 		Educational background needed for the position or Occupation.
estimatedSalary MonetaryAmount  or
MonetaryAmountDistribution  or
Number 		An estimated salary for a job posting or occupation, based on a variety of variables including, but not limited to industry, job title, and location. Estimated salaries are often computed by outside organizations rather than the hiring organization, who may not have committed to the estimated value.
experienceRequirements Text Description of skills and experience needed for the position or Occupation.
occupationLocation AdministrativeArea The region/country for which this occupational description is appropriate. Note that educational requirements and qualifications can vary between jurisdictions.
occupationalCategory CategoryCode  or
Text 		A category describing the job, preferably using a term from a taxonomy such as BLS O*NET-SOC, ISCO-08 or similar, with the property repeated for each applicable value. Ideally the taxonomy should be identified, and both the textual label and formal code for the category should be provided.

Note: for historical reasons, any textual label and formal code provided as a literal may be assumed to be from O*NET-SOC.
qualifications EducationalOccupationalCredential  or
Text 		Specific qualifications required for this role or Occupation.
responsibilities Text Responsibilities associated with this role or Occupation.
skills DefinedTerm  or
Text 		A statement of knowledge, skill, ability, task or any other assertion expressing a competency that is desired or required to fulfill this role or to work in this occupation.
Properties from Thing
additionalType URL An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.
alternateName Text An alias for the item.
description Text A description of the item.
disambiguatingDescription Text A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.
identifier PropertyValue  or
Text  or
URL 		The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.
image ImageObject  or
URL 		An image of the item. This can be a URL or a fully described ImageObject.
mainEntityOfPage CreativeWork  or
URL 		Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details.
Inverse property: mainEntity.
name Text The name of the item.
potentialAction Action Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
sameAs URL URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.
subjectOf CreativeWork  or
Event 		A CreativeWork or Event about this Thing.
Inverse property: about.
url URL URL of the item.


Instances of Occupation may appear as values for the following properties

PropertyOn TypesDescription
hasOccupation Person The Person's occupation. For past professions, use Role for expressing dates.
relevantOccupation JobPosting The Occupation for the JobPosting.

Source

https://github.com/schemaorg/schemaorg/issues/1698

Examples

Example 1
Without Markup Microdata RDFa JSON-LD 
<h1>Occupation: Research Scientist</h1>
<h2>educationRequirements"</h2>
<p>PhD or equivalent<p>

<div itemscope itemtype="http://schema.org/Occupation">
 <h1>Occupation: <span itemprop="name"> Research Scientist</span></h1>
 <h2>qualifications</h2>
 <p itemprop="educationRequirements" itemscope
    itemtype="http://schema.org/EducationalOccupationalCredential">
  <span itemprop="educationalLevel">PhD or equivalent</span>
 </p>
</div>

<div vocab="http://schema.org/" typeof="http://schema.org/Occupation">
 <h1>Occupation: <span property="name"> Research Scientist</span></h1>
 <h2>qualifications</h2>
 <p property="educationRequirements"
    typeof="http://schema.org/EducationalOccupationalCredential">
  <span property="educationalLevel">PhD or equivalent</span>
 </p>
</div>

<script type="application/ld+json">
{
  "@context": "http://schema.org/",
  "@type": "Occupation",
  "name": "Research Scientist",
  "qualifications": {
    "@type": "EducationalOccupationalCredential",
    "educationalLevel": "PhD or equivalent"
  }
}
</script>
Example 2
Without Markup Microdata RDFa JSON-LD 
See JSON example.

TODO

TODO

<script type="application/ld+json">
{
  "@context": "http://schema.org/",
  "@type": "JobPosting",
  "name": "Mobile App Developer",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "ACME Software"
  },
  "relevantOccupation": {
    "@type": "Occupation",
    "name": "Software Developers, Applications",
    "occupationalCategory": {
             "@type": "CategoryCode",
             "inCodeSet": {
                  "@type": "CategoryCodeSet",
                  "name": "O*Net-SOC",
                  "dateModified": "2019",
                  "url": "https://www.onetonline.org/"
               },
             "codeValue": "15-1132.00",
             "name": "Software Developers, Applications",
             "url": "https://www.onetonline.org/link/summary/15-1132.00"
         }
  }
}
</script>
Example 3
Without Markup Microdata RDFa JSON-LD 
See JSON example.

TODO

TODO

<script type="application/ld+json">
{
  "@context": "http://schema.org/",
  "@type": "Occupation",
  "name": "Nurse Practioner",
  "educationRequirements": "Graduate degree in nursing",
  "occupationalCategory": "29-1171.00",
  "occupationLocation": {
    "@type": "Country",
    "name": "USA",
    "sameAs": "https://www.wikidata.org/wiki/Q30"
  },
  "qualifications": "Registered nurse licensure in state where practicing",
  "responsibilities": "Diagnose and treat acute, episodic, or chronic illness, independently or as part of a healthcare team.",
  "skills": ["Active listening", "Critical thinking", "Social awareness"],
  "estimatedSalary": {
    "@type": "MonetaryAmountDistribution",
    "duration": "1Y",
    "currency": "USD",
    "percentile10": 72000,
    "percentile25": 86000,
    "median": 109000,
    "percentile75": 120000,
    "percentile90": 140000
  }
}
</script>
Example 4
Without Markup Microdata RDFa JSON-LD 
<!-- occupationalCategory utilising CategoryCode -->
<!-- JSONLD only example -->

<!-- JSONLD only example -->

<!-- JSONLD only example -->

<!-- occupationalCategory utilising CategoryCode -->
<script type="application/ld+json">
    {
      "@context": "http://schema.org/",
      "@type": "Occupation",
      "occupationalCategory": {
         "@type": "CategoryCode",
         "inCodeSet": {
              "@type": "CategoryCodeSet",
              "name": "O*Net-SOC",
              "dateModified": "2019",
              "url": "https://www.onetonline.org/"
           },
         "codeValue": "15-1211.00",
         "name": "Computer Systems Analysts",
         "url": "https://www.onetonline.org/link/summary/15-1121.00"
     }
    }
    </script>
Example 5
Without Markup Microdata RDFa JSON-LD 
See JSON example.

TODO

TODO

<script type="application/ld+json">
{
  "@context": "http://schema.org/",
  "@type": "Person",
  "name": "Peter Venkman",
  "hasOccupation": {
    "@type": "Occupation",
    "name": "Parapsychologist",
    "educationRequirements": "PhD in parapsychology"
  }
}
</script>
Example 6
Without Markup Microdata RDFa JSON-LD 
See JSON example.

TODO

TODO

<script type="application/ld+json">
{
  "@context": "http://schema.org/",
  "@type": "Person",
  "name": "Albert Einstein",
  "hasOccupation": [
    {
      "@type": "Role",
      "hasOccupation": {
      "@type": "Occupation",
      "name": "Patent examiner",
        "occupationalCategory": "23-2099.00"
      },
      "startDate": "1901",
      "endDate": "1906"
    },
    {
      "@type": "Occupation",
      "name": "Professor of Physics",
      "educationRequirements": "PhD in Physics"
    }
  ]
}
</script>