Senior Data Engineer

ph3bSenior Data Engineer /b /h3h3bAbout Keyrock /b /h3pSince our beginnings in 2017, we've grown to be a leading change-maker in the digital asset space, renowned for our partnerships and innovation. /ppToday, we partner with over 250 team members around the world. Our diverse team hails from 42 nationalities, with backgrounds ranging from self-taught DeFi natives to PhDs. Predominantly remote, we have hubs in London, Brussels, and Singapore, and host regular online and offline hangouts to keep the crew tight. /ppWe are trading on more than 80 trading venues, and working with a wide array of asset issuers. As a well-established market maker, our distinctive expertise led us to expand rapidly. Today, our services span market making, options trading, high-frequency trading, OTC, and DeFi trading desks. /ppBut we’re more than a service provider. We’re an initiator. We're pioneers in adopting the Rust Development language for our algorithmic trading, and champions of its use in the industry. We support the growth of Web3 startups through our Accelerator Program. We upgrade ecosystems by injecting liquidity into promising DeFi, RWA, and NFT protocols. And we push the industry's progress with our research and governance initiatives. /ppAt Keyrock, we're not just envisioning the future of digital assets. We're actively building it. /ph3bAbout the team and why the role exists /b /h3pThe Central Data Team (CDT) is only a few months old, but data has been Keyrock's lifeblood since day one. We're now building the Keyrock Data Platform to give Keyrockers, and the AI agents working alongside them, the data and context they need to act fast and autonomously within agreed boundaries and aligned with our shared goals. Doing that means taking data from across the company and making sense of it in real time for all the functions that depend on it: trading desks, wealth and asset management, product, risk, finance, compliance, and research to name a few. /ppYou'd be one of the early hires in CDT and we expect you to contribute to most of the bigger decisions and build work. The standards we settle on and the way the team ends up working are still open. /ph3bWhat You’ll Do /b /h3ullipBuild streaming and batch pipelines that ingest, normalise, and distribute market, trading, and portfolio data, resilient to feed and exchange failures. /p /lilipBuild the self-serve tooling (SDKs, patterns, templates, AI agents) so other teams publish, consume, and build on data products without waiting on us. /p /lilipOwn data contracts and schema evolution. Keep schema changes from turning into multi-team coordination events. /p /lilipDesign the lakehouse and time-series layer around consumer query patterns. /p /lilipBuild and evolve the Data Governance and Data Quality Framework: stale-feed detection, schema validation, range checks, idempotent writes, lineage, ownership, self-healing. /p /lilipBuild the derived analytics the business runs on: cross-exchange spreads, VWAP at depth, order book microstructure for the desks; portfolio views, exposure, performance for wealth and asset management. /p /lilipMake observability, cost, and performance first-class from day one. /p /lilipTreat infrastructure as code (Docker, Terraform, CI/CD) alongside our Central Infrastructure Team. /p /lilipWork in the open: write things down, partner closely with Architecture, Infrastructure, Platform, and the rest of the teams. /p /li /ulh3bWhat We’re Looking For /b /h3pTools matter less to us than how you think about problems. That said, here's the shape of the person we have in mind. /ppEngineering Craft /pullip8+ years of building production data systems that other people rely on. /p /lilipStrong proficiency in Python and SQL: not just being able to write a query, but being able to reason about what the engine is doing with it. /p /lilipCode that's easy for someone else to read, test, and delete later. /p /lilipStrong understanding of data modelling for both streaming and analytical workloads. /p /lilipEfficiency, quality, idempotency, and observability are taken seriously by default. /p /li /ulpSystems Design /pullipYou've designed and operated streaming systems on Kafka, Redpanda, MSK, or Kinesis, and you have opinions about partitioning, consumer groups, offsets, and schema registries. /p /lilipYou've used a time-series store in production (ClickHouse ideally; TimescaleDB, QuestDB, or similar are fine too) and can talk about table design as a function of query patterns. /p /lilipYou've worked with a lakehouse architecture and reason about table layout, partitioning, and compaction as design choices that shape query performance and storage cost. /p /lilipYou build for self-healing and idempotency. Reprocessing is safe, retries don't double-write, and the system recovers without a human in the loop. /p /li /ulpOperational Readiness /pullipDocker, Terraform, and CI/CD are how you work, not a separate "DevOps" thing. /p /lilipYou think about cost and performance e