Data Ontology Engineer

{
  "content_hash": "e3d0ba8d2c5a9205cf11cb6d0dd535c1de53dca7ff3a8495df8f6fb89fcd1711",
  "source_hash": "869e70c6f458566f0df08c78418110488c83092dd3c3dc7580510a106fb43c1b",
  "last_changed_at": "2026-06-13T08:21:59.303Z",
  "active_status": "active"
}

{
  "dedupe": null,
  "language": "en",
  "location": {
    "raw": "UNAVAILABLE, UNAVAILABLE, US",
    "city": "UNAVAILABLE",
    "region": "UNAVAILABLE",
    "country": "United States",
    "is_remote": false,
    "confidence": 0.8
  },
  "salary_max": 158303,
  "salary_min": 142696,
  "inferred_at": "2026-06-20T08:26:58.137Z",
  "launch_scope": {
    "reason": "english_us_canada",
    "included": true,
    "language": "en",
    "location": {
      "raw": "UNAVAILABLE, UNAVAILABLE, US",
      "city": "UNAVAILABLE",
      "region": "UNAVAILABLE",
      "country": "United States",
      "is_remote": false,
      "confidence": 0.8
    },
    "countries": [
      "United States"
    ]
  },
  "remote_policy": "remote",
  "salary_period": "hour",
  "workplace_type": "remote",
  "salary_currency": "USD"
}

{}

{
  "json_ld": {
    "url": "https://careers-gdms.icims.com/jobs/72874/data-ontology-engineer/job",
    "@type": "JobPosting",
    "title": "Data Ontology Engineer",
    "@context": "http://schema.org",
    "datePosted": "2026-06-02T04:00:00.000Z",
    "description": "<h2>Basic Qualifications </h2>\n<p>Bachelor's degree in Systems Engineering, or a related Science, Engineering or Mathematics field, plus a minimum of 8 years of relevant experience; or Master's degree, plus a minimum of 6 years of relevant experience.<strong>CLEARANCE REQUIREMENTS:</strong>: Department of Defense Secret security clearance is required at time of hire. Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information. Due to the nature of work performed within our facilities, U.S. citizenship is required.</p>\n<h2>Responsibilities for this Position</h2>\n<h2>What You'll Own</h2>\n<ul>\n <li>Domain ontologies. Design and maintain semantic schemas that describe key engineering and manufacturing entities — products, BOMs, plants, equipment, processes, work orders — and their relationships across systems.</li>\n <li>Knowledge graphs. Implement ontologies using semantic web or graph technologies (RDF/OWL/SHACL/SPARQL or property-graph equivalents like Neo4j). Build, query, validate, and tune knowledge graphs in production.</li>\n <li>Data alignment. Integrate heterogeneous data sources — PLM, ERP, MES, CMMS, QMS, data lakes — into a common vocabulary. Align schemas, code sets, and master data to the ontology so AI services see one coherent picture.</li>\n <li>Semantic layer. Design the enterprise semantic layer that BI tools, analytics platforms, and AI/LLM applications query consistently. Define core business entities, metrics, and hierarchies and map them to existing data stores.</li>\n <li>Ontology governance. Manage versioning, documentation, reuse of industry standards, and enforcement of modeling best practices across pods. Your ontologies are shared assets — they must be maintainable by others.</li>\n</ul>\n<h2>What You Won't Own</h2>\n<ul>\n <li>AI model development or prompt engineering — you provide the data substrate, the AI engineers build on it</li>\n <li>Enterprise system administration — you integrate data from systems, you don't manage them</li>\n <li>Business process decisions — Domain SMEs and the Product Owner define what matters; you model it</li>\n</ul>\n<h2>What Makes This Role Different</h2>\n<ul>\n <li>Your ontologies directly feed AI systems that make real business decisions. A bad data model doesn't just slow a report — it makes an AI agent reason incorrectly.</li>\n <li>You will work across multiple enterprise domains — HR, manufacturing, CRM, supply chain — building a shared knowledge architecture, not siloed data models.</li>\n <li>You will collaborate with business SMEs who understand the domain and AI engineers who consume your models. You translate between both worlds.</li>\n</ul>\n<h2>Required Qualifications</h2>\n<ul>\n <li>Bachelor’s degree in Computer Science, Data Science, Information Science, or a related field, plus 5 years of experience; or Master’s degree plus 3 years of experience</li>\n <li>Hands-on experience with knowledge graph or ontology technologies — RDF/OWL/SHACL/SKOS, SPARQL, and/or graph databases (Neo4j, Stardog, Ontotext, AWS Neptune, or similar)</li>\n <li>Experience integrating disparate enterprise data sources into a shared vocabulary or knowledge graph — you have aligned data across systems that use different schemas, code sets, and terminology</li>\n <li>Strong data modeling skills — dimensional modeling, semantic modeling, or formal ontology design applied in production, not just academic settings</li>\n <li>Experience with enterprise data platforms — data warehouses, data lakes, Snowflake, Palantir Foundry, or similar</li>\n <li>U.S. citizenship required. Department of Defense Secret security clearance is required at time of hire.</li>\n</ul>\n<h2>Preferred Qualifications</h2>\n<ul>\n <li>Experience building semantic layers or metrics layers consumed by BI, analytics, or AI/LLM applications</li>\n <li>Experience with enterprise systems data (ERP, MES, PLM, CRM) — you understand the data structures these systems produce</li>\n <li>Familiarity with AI/ML data requirements — embeddings, vectorization, retrieval-augmented generation, and how knowledge graphs support LLM reasoning</li>\n <li>Comfortable leading workshops with non-technical business SMEs to capture requirements and iteratively refine data models</li>\n <li>Experience with ontology governance — versioning, documentation, standards reuse across teams or an enterprise</li>\n</ul>\n<h2>What Sets You Apart</h2>\n<ul>\n <li>You think in relationships, not rows. You see connections between data that others model as flat tables.</li>\n <li>You can explain a semantic model to a business SME and have them recognize their domain in it.</li>\n <li>You build ontologies that other people can use and extend — not elegant models that only you understand.</li>\n <li>You have integrated data from systems that were never designed to work together and made it coherent.</li>\n <li>You care about data meaning, not just data structure. You know that two systems calling something \"part number\" doesn't mean they mean the same thing.</li>\n</ul>\n<h2>Details</h2>\n<ul>\n <li>Remote — 100% telework</li>\n <li>9/80 schedule</li>\n <li>Defense industry experience is not required</li>\n</ul>\n<h2>Salary Note</h2>This estimate represents the typical salary range for this position based on experience and other factors (geographic location, etc.). Actual pay may vary. This job posting will remain open until the position is filled.\n<h2>Combined Salary Range</h2>USD $142,696.00 - USD $158,303.00 /Yr.\n<h2>Company Overview</h2>\n<p>General Dynamics Mission Systems (GDMS) engineers a diverse portfolio of high technology solutions, products and services that enable customers to successfully execute missions across all domains of operation. With a global team of 12,000+ top professionals, we partner with the best in industry to expand the bounds of innovation in the defense and scientific arenas. Given the nature of our work and who we are, we value trust, honesty, alignment and transparency. We offer highly competitive benefits and pride ourselves in being a great place to work with a shared sense of purpose. You will also enjoy a flexible work environment where contributions are recognized and rewarded. If who we are and what we do resonates with you, we invite you to join our high-performance team!</p>\n<p>Equal Opportunity Employer / Individuals with Disabilities / Protected Veterans</p>",
    "directApply": true,
    "jobLocation": [
      {
        "@type": "Place",
        "address": {
          "@type": "PostalAddress",
          "postalCode": "UNAVAILABLE",
          "addressRegion": "UNAVAILABLE",
          "streetAddress": "UNAVAILABLE",
          "addressCountry": "US",
          "addressLocality": "UNAVAILABLE",
          "postOfficeBoxNumber": "UNAVAILABLE"
        }
      }
    ],
    "validThrough": "2027-06-02T04:00:00.000Z",
    "employmentType": "OTHER",
    "jobLocationType": "TELECOMMUTE",
    "hiringOrganization": {
      "name": "General Dynamics Mission Systems, Inc",
      "@type": "Organization",
      "sameAs": "https://gdmissionsystems.com/"
    },
    "occupationalCategory": "Engineering-Systems"
  },
  "detail_meta": {
    "url": "https://careers-gdms.icims.com/jobs/72874/data-ontology-engineer/job?in_iframe=1",
    "http_status": 200,
    "content_type": "text/html;charset=UTF-8",
    "response_bytes": 45974,
    "compact_response_bytes": 7660,
    "original_response_bytes": 45974
  },
  "sitemap_job": {
    "id": "72874",
    "url": "https://careers-gdms.icims.com/jobs/72874/data-ontology-engineer/job",
    "slug": "data-ontology-engineer",
    "lastmod": "2026-06-12T12:58:18-04:00"
  },
  "detail_errors": []
}