Job Metadata: What's Inside Every Job Posting

What Is Job Metadata?

Job metadata is the structured, machine-readable data extracted from a job posting - separate from the free-text job description itself. Whenever Techmap collects a posting from an ATS career page, job board, or employment office - or via our own job crawlers, it does not merely store the raw text: it identifies and normalises dozens of individual fields, such as the company name, publish date, location, employment type, salary, and required skills.

This matters because raw job posting text is, by its very nature, unstructured and inconsistent across sources: one site might write "Remote" in the title, another in a dedicated field, and a third not at all. Metadata normalises these signals into consistent fields (such as job.workPlace), so they can be filtered, counted, and compared across sources, countries, and companies without re-parsing the text for every single query.

Why Job Metadata Matters

• Filtering and search: query postings by countryCode, workPlace, careerLevel, or dateCreated, rather than scanning the description text.
• Deduplication: the isDuplicate and isDuplicateOf flags let you exclude re-published copies of the very same posting.
• Source quality: the isDirect flag distinguishes employer-direct postings (career pages) from job board republications. Do note, however, that the job board copy is very often the only copy available online at all - not every hiring company runs a website of its own, let alone a proper careers page.
• Sales and market intelligence: company, location, and industry metadata power sales lead generation and labour market analysis, without the need for any manual text mining.
• Structured data / SEO: the job.jsonLD object follows the schema.org JobPosting format and may be embedded directly on a job board page for Google Jobs eligibility.

Job Metadata Fields

The table below groups Techmap's actual API field names (from the result[] array of the Job API's Data Dictionary) according to the kind of metadata they capture. Every field name and example value shown here is taken directly from the live schema - please see the full field reference for types and population rates.

Job Metadata in a Full API Response

Below is a complete, genuine example from the Job Posting API's /search endpoint: one posting with all of its metadata fields populated, including the jsonLD object in schema.org format.

{
  "api": "Techmap.io Job Posting API",
  "apiVersion": "v2.6",
  "page": 1,
  "pageSize": 10,
  "totalCount": 1069346,
  "result": [
    {
      "occupation": "Functional Analyst",
      "dateActive": "2024-10-14T14:48:29.000Z",
      "city": "Cleveland",
      "timezone": "CST",
      "contractType": ["DirectEmployment"],
      "language": "en",
      "industry": "Transport",
      "isDuplicate": false,
      "isDuplicateOf": null,
      "isDirect": false,
      "isRecruiter": false,
      "hasSalary": false,
      "jsonLD": {
        "identifier": "66f4d794a315a1138e6bfac2",
        "validThrough": "2024-10-14T14:48:29.000Z",
        "employmentType": "Direct Employment",
        "@type": "JobPosting",
        "salaryCurrency": "USD",
        "description": "**Job Description:** ...",
        "industry": "Transport",
        "title": "SAP TM Functional Analyst",
        "@context": "https://schema.org",
        "url": "https://www.dice.com/job-detail/003170f7-bd59-45d5-a0cf-e4ef93c27419",
        "relevantOccupation": "Functional Analyst",
        "skills": ["Logistics", "SAP TM", "ABAP"],
        "hiringOrganization": {
          "@type": "Organization",
          "name": "Example Corp",
          "url": "https://example.com"
        },
        "jobLocation": {
          "address": {
            "addressCountry": "United States",
            "@type": "PostalAddress",
            "addressLocality": "Cleveland",
            "addressRegion": "TX"
          },
          "@type": "Place",
          "latitude": 30.33804,
          "longitude": -95.02362
        },
        "datePosted": "2024-09-15"
      },
      "source": "dice_us",
      "locale": "en_US",
      "geoPoint": { "lon": -95.02362, "lat": 30.33804 },
      "title": "SAP TM Functional Analyst",
      "skills": ["Logistics", "SAP TM", "ABAP"],
      "dateCreated": "2024-09-15T14:43:24.000Z",
      "timezoneOffset": -6,
      "countryCode": "us",
      "company": "Example Corp",
      "state": "TX",
      "portal": "dice",
      "workPlace": ["Onsite"],
      "careerLevel": ["N/A"],
      "workType": ["N/A"],
      "postCode": "77327"
    }
  ],
  "resultSizeInBytes": 59203
}

This is the very same example as used in the Job API Overview's Data Dictionary.

References

• Job API Overview - Data Dictionary - the complete, unabbreviated field reference with types and population rates
• Job Posting API - product overview and API access
• Job Data Overview - the equivalent field schema for bulk Data Feeds and Historical Datasets
• Developer Guide - query parameters, code examples, and pagination
• Job Data Glossary - definitions for ATS Career Page, isDirect, Data Schema, and 40+ related terms
• Portal Explorer - all 195+ sources these metadata fields are collected from