Back to jobs

Senior Data Platform Engineer

Remote - New Jersey, US

Live, first seen by us 40 days ago
Pay
Pay not listedSimilar roles state $127K–$190K
Work setting
Remote — work setting source
Listed location: Remote - New Jersey, US
Read the full posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting

What you’ll work on

Full posting

We are seeking a Senior Data Platform Engineer to help build, scale, and operate our bespoke enterprise data platform, the foundational infrastructure layer that ingestion, ontology, and business application teams build on top of.

You will not own the business logic of individual data pipelines; those are owned by application and business teams.

  • Build reusable batch and streaming frameworks on Airflow, Spark, and Flink for other teams to use

  • Own the Iceberg/Nessie/Trino/StarRocks lakehouse layer, including performance and storage lifecycle

  • Build and run Kafka streaming infrastructure for topics, schemas, and connectors

  • Design APIs and MCP servers that expose platform data and capabilities to people and AI agents

  • Build observability, resilience, and on-call practices for the platform stack

From the employer’s posting
We are seeking a Senior Data Platform Engineer to help build, scale, and operate our bespoke enterprise data platform, the foundational infrastructure layer that ingestion, ontology, and business application teams build on top of. This is a hands-on, individual-contributor role for someone who wants deep technical ownership of platform internals rather than owning specific business data pipelines: our platform stack spans Airflow, Iceberg, Spark, Flink, Kafka, Nessie, Trino, and StarRocks, along with supporting UI components for platform users.
You will not own the business logic of individual data pipelines; those are owned by application and business teams. Instead, you will build and harden the core platform capabilities that make those pipelines possible: ingestion frameworks, data cleansing/harmonization utilities, storage and compute infrastructure, and the APIs and agentic (MCP) interfaces that let both humans and AI agents access and operate on platform data and capabilities. You'll also be expected to bring an agentic software development approach to your own work, using AI coding agents and tooling to meaningfully multiply your engineering throughput, not just as an experiment on the side.
providing reusable frameworks that application/business teams use to build their own pipelines
Own the data lakehouse layer built on Iceberg, Nessie (catalog/versioning), Trino, and StarRocks
Build and maintain Kafka-based streaming infrastructure (topics, schema management, connectors)
Design and build APIs that expose platform data and capabilities
Build and maintain observability (metrics, logging, tracing, alerting) across the platform stack

What you’ll bring

All qualifications

Core experience

  • 8-12 years of software/data engineering experience, with significant hands-on experience building or operating large-scale data platform infrastructure (not primarily building individual application-level data pipelines).
  • Strong understanding of lakehouse architecture: table formats, catalog management, query engines, and the trade-offs between batch and streaming processing.
  • Experience designing and building APIs for platform capabilities, with an understanding of API governance, versioning, and security for multi-tenant platform consumers.
  • Experience building and maintaining production observability (metrics, logging, tracing) for complex, multi-service data infrastructure.

Preferred experience

  • Experience building internal developer platforms or "paved road" tooling that other engineering teams adopt as self-service infrastructure.
  • Experience building agent-facing tooling or infrastructure beyond MCP (e.g., tool-use frameworks, agent orchestration, guardrails for autonomous agent actions).
  • Familiarity with UI/front-end development sufficient to build or contribute to platform-facing dashboards and tooling (not a primary requirement, but a plus).
  • Experience in financial services or another regulated, data-intensive industry, given the auditability and data-quality expectations typical of the domain.
Qualification wording
8-12 years of software/data engineering experience, with significant hands-on experience building or operating large-scale data platform infrastructure (not primarily building individual application-level data pipelines).
Strong understanding of lakehouse architecture: table formats, catalog management, query engines, and the trade-offs between batch and streaming processing.
Experience designing and building APIs for platform capabilities, with an understanding of API governance, versioning, and security for multi-tenant platform consumers.
Experience building and maintaining production observability (metrics, logging, tracing) for complex, multi-service data infrastructure.
Experience building internal developer platforms or "paved road" tooling that other engineering teams adopt as self-service infrastructure.
Experience building agent-facing tooling or infrastructure beyond MCP (e.g., tool-use frameworks, agent orchestration, guardrails for autonomous agent actions).
Familiarity with UI/front-end development sufficient to build or contribute to platform-facing dashboards and tooling (not a primary requirement, but a plus).
Experience in financial services or another regulated, data-intensive industry, given the auditability and data-quality expectations typical of the domain.
Apply at Ssctech

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 9, 202640 days ago
Recorded sightings
85
Last seen by us
Nov 16, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$127K–$190K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,396 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 40

Similar jobs usually come down between day 6 and day 56.

At Ssctech, jobs usually come down by about day 44.

From 14,186 similar postings that came down, and 40 of Ssctech’s. Coming down is not always a hire.

Ssctech is hiring

7 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring has slowed
  • Takes jobs down at a usual pace
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Iceberg
  • Kafka
  • Spark
  • Trino
  • Airflow
Where the posting names them
Role Summary We are seeking a Senior Data Platform Engineer to help build, scale, and operate our bespoke enterprise data platform, the foundational infrastructure layer that ingestion, ontology, and business application teams build on top of. This is a hands-on, individual-contributor role for someone who wants deep technical ownership of platform internals rather than owning specific business data pipelines: our platform stack spans Airflow, Iceberg, Spark, Flink, Kafka, Nessie, Trino, and StarRocks, along with supporting UI components for platform users. You will not own the business logic of individual data pipelines; those are owned by application and business teams. Instead, you will build and harden the core platform capabilities that make those pipelines possible: ingestion frameworks, data cleansing/harmonization utilities, storage and compute infrastructure, and the APIs and agentic (MCP) interfaces that let both humans and AI agents access and operate on platform data and capabilities. You'll also be expected to bring an agentic software development approach to your own work, using AI coding agents and tooling to meaningfully multiply your engineering throughput, not just as an experiment on the side.
- Design, build, and operate core platform capabilities on top of Airflow, Spark, and Flink for batch and streaming data processing, providing reusable frameworks that application/business teams use to build their own pipelines rather than building pipelines on their behalf. - Own the data lakehouse layer built on Iceberg, Nessie (catalog/versioning), Trino, and StarRocks, including table format management, catalog governance, query performance, and storage lifecycle (compaction, partitioning, retention). - Build and maintain Kafka-based streaming infrastructure (topics, schema management, connectors) that supports both platform-internal needs and consumption by downstream teams.
- 8-12 years of software/data engineering experience, with significant hands-on experience building or operating large-scale data platform infrastructure (not primarily building individual application-level data pipelines). - Deep, hands-on experience with at least several of: Apache Airflow, Apache Iceberg, Apache Spark, Apache Flink, Apache Kafka, Nessie, Trino, StarRocks, with the ability to reason confidently about the rest and ramp up quickly where needed. - Strong understanding of lakehouse architecture: table formats, catalog management, query engines, and the trade-offs between batch and streaming processing.
- Own the data lakehouse layer built on Iceberg, Nessie (catalog/versioning), Trino, and StarRocks, including table format management, catalog governance, query performance, and storage lifecycle (compaction, partitioning, retention). - Build and maintain Kafka-based streaming infrastructure (topics, schema management, connectors) that supports both platform-internal needs and consumption by downstream teams. - Develop reusable ingestion, cleansing, and harmonization frameworks/libraries that application teams can adopt to bring data onto the platform in a consistent, quality-controlled way, without the platform team owning each pipeline's business logic.
- Experience in financial services or another regulated, data-intensive industry, given the auditability and data-quality expectations typical of the domain. - Contributions to open-source projects in the Airflow/Iceberg/Spark/Flink/Trino ecosystem. Unless explicitly requested or approached by SS&C Technologies, Inc. or any of its affiliated companies, the company will not accept unsolicited resumes from headhunters, recruitment agencies, or fee-based recruitment services.

Your next step

Complete your application on wd1.myworkdaysite.com. The employer’s form will show what is required.

Applying through Workday

  • You create an account with each employer before you can upload anything. Every Workday employer has its own account, so one sign-up doesn’t carry over.
  • “Autofill with Resume” comes right after sign-in, before the My Information and My Experience steps. Check every field it fills in those steps, since that’s what recruiters see.
  • Your application status lives in that employer’s Candidate Home, under the same sign-in.

Already applied? Track this application

Job description

View original posting ↗

SS&C is a leading provider of mission-critical, AI-powered technology and services empowering financial services and healthcare organizations to work smarter, faster, and securely. Founded in 1986, SS&C is headquartered in Windsor, Connecticut, and has offices worldwide. More than 23,000 financial services and healthcare organizations, from the world's largest companies to small and mid-market firms, rely on SS&C for expertise, scale, and technology.


Job Description


Senior Data Platform Engineer

Role Summary

We are seeking a Senior Data Platform Engineer to help build, scale, and operate our bespoke enterprise data platform, the foundational infrastructure layer that ingestion, ontology, and business application teams build on top of. This is a hands-on, individual-contributor role for someone who wants deep technical ownership of platform internals rather than owning specific business data pipelines: our platform stack spans Airflow, Iceberg, Spark, Flink, Kafka, Nessie, Trino, and StarRocks, along with supporting UI components for platform users.

You will not own the business logic of individual data pipelines; those are owned by application and business teams. Instead, you will build and harden the core platform capabilities that make those pipelines possible: ingestion frameworks, data cleansing/harmonization utilities, storage and compute infrastructure, and the APIs and agentic (MCP) interfaces that let both humans and AI agents access and operate on platform data and capabilities. You'll also be expected to bring an agentic software development approach to your own work, using AI coding agents and tooling to meaningfully multiply your engineering throughput, not just as an experiment on the side.

Key Responsibilities

Platform Capability Engineering

  • Design, build, and operate core platform capabilities on top of Airflow, Spark, and Flink for batch and streaming data processing, providing reusable frameworks that application/business teams use to build their own pipelines rather than building pipelines on their behalf.
  • Own the data lakehouse layer built on Iceberg, Nessie (catalog/versioning), Trino, and StarRocks, including table format management, catalog governance, query performance, and storage lifecycle (compaction, partitioning, retention).
  • Build and maintain Kafka-based streaming infrastructure (topics, schema management, connectors) that supports both platform-internal needs and consumption by downstream teams.
  • Develop reusable ingestion, cleansing, and harmonization frameworks/libraries that application teams can adopt to bring data onto the platform in a consistent, quality-controlled way, without the platform team owning each pipeline's business logic.
  • Build and maintain UI components that give platform users (engineers, analysts, business teams) visibility into platform state, data catalogs, job status, and data quality.

API & Agentic (MCP) Enablement

  • Design and build APIs that expose platform data and capabilities (ingestion, querying, catalog metadata, job orchestration) to downstream teams and services in a well-governed, secure, and performant way.
  • Build and maintain MCP (Model Context Protocol) servers/interfaces that expose platform data, catalogs, and lineage to AI agents and LLM-based tools, enabling agentic consumption of platform capabilities.
  • Extend agentic enablement beyond data access by building the tooling and guardrails that allow AI agents to safely operate parts of the platform itself (e.g., triggering pipeline runs, querying job status, remediation actions), with appropriate human-in-the-loop controls where needed.
  • Partner with platform consumers (including the Ontology Platform team) to understand their API/agentic access needs and translate them into platform capability requirements.

Scalability & Resilience

  • Ensure the platform scales reliably as data volume, source count, and consumer count grow, through capacity planning, performance tuning, and architectural evolution across the stack.
  • Design for resilience: fault tolerance, disaster recovery, data consistency guarantees, and graceful degradation across ingestion, storage, and compute layers.
  • Build and maintain observability (metrics, logging, tracing, alerting) across the platform stack to detect and diagnose issues before they impact downstream teams.
  • Drive on-call/production support practices for the platform, including runbooks and incident response processes.

Engineering Practice & Productivity

  • 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 (targeting materially higher output than traditional development approaches, not incremental gains).
  • Establish and evolve engineering best practices for the platform team: testing strategy, CI/CD, infrastructure-as-code, and code/architecture review standards suited to a bespoke, multi-technology data platform.
  • Mentor other engineers on platform internals and on effective use of agentic development tooling, even without formal management responsibility.
Required Qualifications
  • 8-12 years of software/data engineering experience, with significant hands-on experience building or operating large-scale data platform infrastructure (not primarily building individual application-level data pipelines).
  • Deep, hands-on experience with at least several of: Apache Airflow, Apache Iceberg, Apache Spark, Apache Flink, Apache Kafka, Nessie, Trino, StarRocks, with the ability to reason confidently about the rest and ramp up quickly where needed.
  • Strong understanding of lakehouse architecture: table formats, catalog management, query engines, and the trade-offs between batch and streaming processing.
  • Experience designing and building APIs for platform capabilities, with an understanding of API governance, versioning, and security for multi-tenant platform consumers.
  • Direct experience with, or strong interest and rapid aptitude for, building MCP servers or similar agent-facing interfaces that expose data/capabilities to AI agents and LLM-based tooling.
  • 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.
  • Strong systems engineering fundamentals: distributed systems, performance tuning, capacity planning, and building for fault tolerance and resilience at scale.
  • Experience building and maintaining production observability (metrics, logging, tracing) for complex, multi-service data infrastructure.
  • Comfortable operating as an individual contributor with deep technical ownership, while also being able to mentor others and influence engineering practice without formal authority.
Preferred Qualifications
  • Experience building internal developer platforms or "paved road" tooling that other engineering teams adopt as self-service infrastructure.
  • Experience building agent-facing tooling or infrastructure beyond MCP (e.g., tool-use frameworks, agent orchestration, guardrails for autonomous agent actions).
  • Familiarity with UI/front-end development sufficient to build or contribute to platform-facing dashboards and tooling (not a primary requirement, but a plus).
  • Experience in financial services or another regulated, data-intensive industry, given the auditability and data-quality expectations typical of the domain.
  • Contributions to open-source projects in the Airflow/Iceberg/Spark/Flink/Trino ecosystem.

 

 

Unless explicitly requested or approached by SS&C Technologies, Inc. or any of its affiliated companies, the company will not accept unsolicited resumes from headhunters, recruitment agencies, or fee-based recruitment services.

 

 

SS&C Technologies offers a comprehensive total rewards package designed to support your wellbeing, growth, and future. Our benefits include medical, dental, and vision coverage; a 401(k) plan with company match; paid time off, holidays, and parental leave; and professional development reimbursement opportunity.

 

 

 

 

 

 

 

 

Applications will be accepted on an ongoing basis until the position is filled.

 

 

SS&C Technologies is an Equal Employment Opportunity employer and does not discriminate against any applicant for employment or employee on the basis of race, color, religious creed, gender, age, marital status, sexual orientation, national origin, disability, veteran status or any other classification protected by applicable discrimination laws.

About Ssctech

People
About 28,800 in 2025, up 7% from the year before.Annual report (SEC Form 10-K)
Company
Listed as SSNC.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 860, the most 1,353, and the latest week had 1,020.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Remote - New Jersey, US

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.