> Markdown version of [/jobs/ext/3049870-sr-engineer-ontology-platform](https://www.wearedevelopers.com/jobs/ext/3049870-sr-engineer-ontology-platform). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Sr Engineer Ontology Platform - **Company:** SS&C Technologies, Inc. - **Location:** United States (Remote available) - **Experience:** Expert - **Salary:** $165,000.0 - $175,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Airflow, Information Engineering, Data Infrastructure, Extract Transform Load (ETL), Data Transformation, Data Systems, Graph Database, Systems Development Life Cycle, Semantic Web, Software Deployment, SPARQL, SQL Databases, Curam Configuration Tools, GitHub Copilot, Apache Spark, Build Management, Apache Flink, Apache Kafka, Data Pipelines - **Published:** September 24, 2026 - **Apply:** https://wd1.myworkdaysite.com/recruiting/ssctech/SSCTechnologies/job/Remote---New-Jersey-US/Sr-Engineer-Ontology-Platform_R46425 ## About the Role * 5-9 years of software/data engineering experience, including exposure to data modeling, data pipelines, and production support for a data platform or similar system. * Comfortable working across the full lifecycle of a feature or capability: design conversations with business stakeholders, implementation, deployment, and ongoing operational support, rather than specializing in one slice. * Solid data engineering fundamentals: SQL, ETL/ELT patterns, data modeling (relational and/or graph), and experience building or maintaining data pipelines at scale. * Experience building integrations or connectors to external/source systems, including handling schema variation and data quality issues at the source. * Ability to translate ambiguous business requirements or definitions into concrete technical structures, and to communicate clearly with both business stakeholders and engineers. * Experience with production operations: monitoring, incident response, and troubleshooting for data systems. * Comfortable working on top of a shared foundational data platform (rather than owning core infrastructure), navigating platform dependencies and escalating capability gaps rather than building around them. * Practical, hands-on experience using AI coding agents (e.g., Claude Code, GitHub Copilot, or similar) as a core part of your development workflow, with a track record of using them to meaningfully increase delivery speed and quality, not just occasional use. * Experience in or working with financial services data environments is a plus, given the regulatory and data-quality expectations typical of the domain., * Prior exposure to ontology, knowledge graph, or master data management (MDM) concepts. * Experience with rules engines or validation/reconciliation frameworks. * Familiarity with graph databases or semantic web standards (RDF, OWL, SPARQL). * Experience onboarding new data sources or users onto a platform as a repeatable, documented process. * Familiarity with the underlying foundational data platform's technologies (Airflow, Spark, Kafka, Iceberg, Trino, or similar), even if you are not building that infrastructure directly. * Experience mentoring others on effective use of AI coding agents or agentic development workflows. ## Description We are seeking a Senior Engineer to join the Ontology Platform team, reporting to the Ontology Platform Lead, and covering the full engineering lifecycle of the ontology platform: from stewarding the ontology model and building reconciliation/rules logic, through connector and platform engineering, data and warehouse work, and production operations. This is a hands-on, individual-contributor role for someone who wants broad ownership across the platform rather than a narrowly scoped specialization: unlike a large infrastructure team where roles split cleanly into specialization tracks, this team is small (5-6 engineers), so each engineer is expected to flex across ontology stewardship, rules engineering, connector/platform work, data engineering, and operations as priorities shift. The ontology platform is built on top of the enterprise's foundational data platform (Airflow, Iceberg, Spark, Flink, Kafka, Nessie, Trino, StarRocks), so you will leverage that infrastructure rather than rebuilding it. Your focus is the layer above it: translating business ontology definitions into concrete structures, building the connectors and mapping/rules logic that bring source systems onto the platform, maintaining the ontology-specific data model and pipelines, and operating the platform in production, including onboarding new sources and supporting business users day to day. Day to Day: Ontology Stewardship & Rules Engineering * Partner with business stakeholders to translate their ontology definitions (entities, relationships, attributes) into concrete, implementable structures within the platform, without redefining what the business itself owns. * Act as a steward of ontology consistency: identify overlapping or conflicting definitions across business teams and help drive toward a shared, canonical view. * Design and build the rules and validation logic that detects breaks (discrepancies between source data and ontology expectations), and continuously improve rule coverage and precision as new sources and use cases are onboarded. * Build and maintain reconciliation logic that compares source system data against the canonical ontology and surfaces exceptions in a way business users can triage. * Maintain clear documentation of ontology structures, mapping conventions, and rule logic so the model stays understandable as it grows. Connector & Platform Engineering * Build and maintain ingestion connectors that bring new source systems onto the ontology platform, working within the frameworks and patterns established by the Engineering Lead. * Contribute to core platform services and APIs that support mapping, configuration, and rules management, so business users can define and adjust behavior without engineering intervention per source. * Leverage the foundational data platform's ingestion, storage, and compute capabilities rather than duplicating them; escalate capability gaps to the Engineering Lead rather than building bespoke infrastructure workarounds. * Adopt and champion an agentic SDLC approach, using AI coding agents and related tooling as a core part of your own development workflow to substantially multiply engineering throughput across connector development, rules/reconciliation logic, and pipeline maintenance, targeting materially higher output than traditional development approaches, not incremental gains. Data & Warehouse Engineering * Design and maintain the data models, schemas, and pipelines that store and serve ontology-mapped data for downstream consumption. * Build and optimize data transformation logic (ETL/ELT) that moves data from source systems through cleansing, harmonization, and mapping into its canonical ontology form. * Ensure data quality, lineage, and performance across the pipeline, from ingestion through to consumption, on top of the foundational platform's storage and compute layers. Operations & Onboarding * Own the end-to-end onboarding process for new data sources and business use cases, from initial mapping through to production deployment. * Support production operations for the platform: monitoring, incident response, troubleshooting, and resolving data or pipeline issues. * Build and maintain runbooks, dashboards, and documentation that make the platform easier to operate and support over time. * Work directly with business users during onboarding to help them understand mapping results, breaks, and how to use the platform's configuration tools. ## Related Videos - [From Messy Queries to Scalable Systems - How Data Engineering actually works](https://www.wearedevelopers.com/videos/100203-from-messy-queries-to-scalable-systems-how-data-engineering-actually-works) - [How to Benchmark Your Apache Kafka](https://www.wearedevelopers.com/videos/76-how-to-benchmark-your-apache-kafka) - [Building a Multi-Agent Orchestration Engine That Actually Follows the Rules](https://www.wearedevelopers.com/videos/100159-building-a-multi-agent-orchestration-engine-that-actually-follows-the-rules) - [AI Model Management Life Circles: ML Ops For Generative AI Models From Research to Deployment](https://www.wearedevelopers.com/videos/1152-ai-model-management-life-circles-ml-ops-for-generative-ai-models-from-research-to-deployment) - [Let's Get Started With Apache Kafka® for Python Developers](https://www.wearedevelopers.com/videos/565-let-s-get-started-with-apache-kafka-for-python-developers) - [Enjoying SQL data pipelines with dbt](https://www.wearedevelopers.com/videos/823-enjoying-sql-data-pipelines-with-dbt) ## Related Articles - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs)