Senior Data Platform Engineer (Graph Serving)

We're looking for a senior platform engineer to build and own the graph serving layer that sits on top of our data platform. Our main source of truth lives in the data lake. The graph database is built from it and can be rebuilt from scratch at any time. You'll build the pipeline that produces the graph and keep it current as new findings land. You'll also choose the graph store it runs on and build the query layer that analysts and downstream products read it through. You'll own the EKS infrastructure the team runs on as well.

This is a hands-on engineering role. You'll spend at least as much time writing pipelines and the query service as running infrastructure.

What you'll own

The graph build pipeline. Write the Spark pipelines that build the graph from lake tables and keep it current as new findings land. Make sure evidence that ages out is actually removed from the store. The graph must always be fully rebuildable from the lake. Once the data model shows its access patterns, you'll test candidate stores against them:

• traversals across several hops, with filters at each step
• queries against nodes with very high edge counts
• how fast a full bulk rebuild runs
• how efficiently data can be deleted as it ages out You'll run the evaluation, make the recommendation, and then operate the store. The query and access layer. Design and build the service and APIs that analysts and downstream products use to read the graph. This includes API contracts, versioning, authentication and authorization, and performance. Query performance. Read query plans, design indexes and fix slow queries. EKS infrastructure. Crossplane compositions, Argo CD applications, deployment pipelines and monitoring. Design leadership. Write down the reasons behind architecture decisions, including the graph store evaluation, and take part in design reviews.

What we need

You have run a stateful data store in production, not just used one. That means sizing, upgrades, and a restore you performed yourself.
Kubernetes in production, and infrastructure as code.
Backend service and API development in Python, Go, Java or a similar language.
Enough Spark and lake table experience (for example Iceberg, Delta Lake or Hudi) to write the pipelines that build the serving layer.
Query performance work: reading query plans, designing indexes and fixing slow queries.
Strong debugging skills in distributed systems.
Must be a US citizen.

Nice to have

Graph database experience (for example Neo4j, Amazon Neptune, JanusGraph or TigerGraph). This is a plus, not a requirement. Distributed systems and operations experience is what matters most.
Hands-on experience with EKS, Crossplane or Argo CD specifically.
Running databases on Kubernetes (StatefulSets, Operators, persistent volumes).
Building data retention and deletion processes, or working in security-sensitive or regulated environments.

What this role is not

This is not a pure site reliability role. You'll spend at least as much time writing the pipelines and the query service as running infrastructure.

What success looks like

A graph store chosen based on test results, with the reasoning written down.
A graph that rebuilds reliably from the lake and stays current as new findings land.
Evidence that ages out is removed from the store on schedule.
A fast, well-documented query layer that analysts and products rely on.
EKS infrastructure that is defined in code, observable and resilient.

Why join us

Own a core platform component from the ground up, including the choice of its main technology.
Work on real production systems at meaningful scale.
Work closely with senior engineers, researchers and product leaders.
Build systems that value correctness, performance and maintainability.