Remote job
Data Engineer – Legal Entity Platform (AWS / Snowflake) (102)
Job details
About this role
Role overview Build the data foundation for a platform that brings ownership and control information about thousands of legal entities into a unified, AI-ready view. The work spans source ingestion, entity identity, ownership calculations, data governance, and data access, beginning with a pilot for one investment fund. The engagement is full-time contract work planned for a three-to-six-month period or longer.
Responsibilities - Build automated pipelines that load CSV and XML exports into cloud storage and a Snowflake warehouse, working around limited source APIs. - Design a cross-system entity model with a unique identifier and source-record mappings. - Develop an effective-dated ownership graph across 14 or more levels and calculate economic ownership deterministically. - Track lineage for each attribute, including source, date, owner, and AI confidence; send uncertain matches for steward review. - Add ingestion validation, source-priority rules, register reconciliation, and access controls by role, region, and attribute. - Manage infrastructure and delivery automation, and make data available to search, charts, and natural-language queries.
Requirements - At least five years building and operating production data pipelines. - Advanced SQL and Python skills, plus hands-on experience with AWS data services such as S3, Lambda, Glue, Step Functions, and EventBridge. - Experience with hierarchical or graph-shaped data, recursive queries, and point-in-time or bitemporal records. - Background in entity resolution or master data management. - Infrastructure-as-code experience with Terraform or CloudFormation and Git-based CI/CD. - Fluent written and spoken English.
Nice to have Snowflake features such as Snowpipe and Streams/Tasks; graph databases such as Neptune or Neo4j; Amazon Bedrock; fund structures or legal-entity ownership data; AWS or SnowPro certifications.
Benefits and work setup Hourly contract, 40 hours per week, remote, with US Eastern or Central working hours preferred. The source gives a planned December 2026 pilot start.