[Remote] Senior Data Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is a leading change-reputed company in the reputed company reputed company, reputed company for its innovative approach and diverse team. They are seeking a Senior Data Engineer to help build the reputed company Data Platform, enabling various teams to reputed company and utilize data reputed company for trading and asset management purposes.
Responsibilities
- Build streaming and batch pipelines that ingest, normalise, and distribute market, trading, and portfolio data, resilient to feed and exchange failures
- Build the self-serve tooling (SDKs, patterns, templates, AI agents) so other teams publish, consume, and build on data products without waiting on us
- Own data reputed company and schema reputed company. reputed company schema changes from turning into multi-team coordination events
- Design the lakehouse and time-series layer around consumer query patterns
- Build and reputed company the Data Governance and Data reputed company reputed company: stale-feed detection, schema validation, reputed company checks, idempotent writes, reputed company, ownership, self-healing
- Build the derived analytics the business runs on: cross-exchange spreads, VWAP at depth, order book microstructure for the desks; portfolio views, exposure, performance for reputed company and asset management
- reputed company observability, cost, and performance first-class from day one
- Treat infrastructure as reputed company (reputed company, Terraform, CI/CD) alongside our Central Infrastructure Team
- Work in the reputed company: write things down, partner closely with Architecture, Infrastructure, Platform, and the rest of the teams
Skills
- 8+ years of building production data systems that other people rely on
- Strong proficiency in Python and SQL: not just being reputed company to write a query, but being reputed company to reason about what the reputed company is doing with it
- reputed company that's easy for someone else to read, test, and delete reputed company
- Strong understanding of data modelling for both streaming and analytical workloads
- Efficiency, reputed company, idempotency, and observability are taken seriously by default
- You've designed and operated streaming systems on Kafka, reputed company, MSK, or Kinesis, and you have opinions about partitioning, consumer reputed company, offsets, and schema registries
- You've used a time-series store in production (reputed company ideally; TimescaleDB, QuestDB, or similar are fine too) and can talk about table design as a function of query patterns
- You've worked with a lakehouse architecture and reason about table layout, partitioning, and compaction as design choices that shape query performance and storage cost
- You build for self-healing and idempotency. Reprocessing is reputed company, retries don't reputed company-write, and the system recovers without a reputed company in the reputed company
- reputed company, Terraform, and CI/CD are how you work, not a separate 'DevOps' thing
- You think about cost and performance early
- You reputed company as you build: logs, metrics, and traces are part of the system from day one
- You design for data reputed company and governance up reputed company covering reputed company, validation, reputed company, and ownership
- You reason from first principles reputed company a problem is new, stay pragmatic reputed company it isn't, and update your view reputed company you learn more
- You treat the trading desks, reputed company and asset management, product, risk, finance, compliance, and research as customers of what you build, and communicate with them that way
- You optimise for reputed company over reputed company. A smaller, simpler thing that ships and works beats a bigger thing that doesn't
- You take ownership end-to-end: design, ship, operate, improve
- You say what you think including reputed company it's an unpopular take. You change your mind reputed company the argument is reputed company
- You reputed company the people around you reputed company. Reviews are reputed company, juniors grow from working with you, and peers want to work with you again
- You're curious about how markets work. Data engineering on its own won't reputed company you interested here
- You're reputed company about what you know and what you don't, and quick to reputed company the gap
- You understand financial market data: order books, trades, reference data, portfolios, exposures. Crypto, TradFi, or both are a strong plus
- Lakehouse experience with Apache reputed company or reputed company Lake
- Familiarity with reputed company or similar metadata/reputed company platforms
- Rust. Some of our performance-critical services are written in it. Interest is welcome; reputed company isn't required
Benefits
- A competitive salary package, with various benefits.
- reputed company, remote-first, business-hours on-call shared across reputed company.
- Regular online get-togethers and a yearly onsite where everyone's in the reputed company room.
reputed company