AWS Engineer

Job TitleThe RoleYou'll own the parts of the systems that make them trustworthy and connected: hardened batch pipelines, model governance and lineage, and the external data integrations the systems depend on. In a regulated setting this is not back-office work — the ability to show exactly how a model was trained, on what data, and why it flagged an account is a core requirement, and this seat owns it. The second seat arrives as the DeFi integration surface materializes: attribution vendors, chain-data providers, and the international exchange's market-metadata feeds.What You'll DoHardening and maintaining the batch pipelines and feature infrastructure the models run on. This is proven, high-value work: turning multi-hour hangs into completing jobs took real data-skew engineering (pre-aggregation, windowing, connection-pool and capacity tuning), and that discipline needs a permanent owner.Model governance: versioning, lineage, reproducibility, and audit-ready records of how every model and flag was produced. We already stamp model-package version, scoring-run ID, and feature-snapshot time on every score, gate registration behind quality checks, and run a feature-contract check that stops a run rather than silently scoring on drifted features. This seat extends and defends that — across both estates.The external integrations that feed the systems — surveillance-vendor feeds (Eventus, in first-wave AWS ingestion), screening providers (PEP/sanctions), KYC/identity sources (a live feed plus historical), market/event data, and, as the DeFi build ramps, blockchain-attribution vendors and chain-data providers.The MLOps tooling that keeps deployments consistent and reversible.Keeping the systems audit-ready as they grow, in partnership with data science and compliance.