[01] Open Role

founding engineer

Build backend infrastructure for the liquidity layer of finance.

A small team building trading infrastructure on top of Hyperliquid, with a focus on execution quality, margin efficiency, and systems reliability.

High ownership: Fast feedback loops and a strong bias toward shipping.
Pragmatic engineering quality: Clean interfaces, strong testing discipline, and measured performance work.
High leverage: A small team where your work directly defines core architecture.

Backend infrastructure: Build and scale backend systems for trading infrastructure.
Event-driven systems: Design reliable event-driven systems with durable logs, idempotent processing, replayability, and operational recovery.
Rust performance work: Implement performance-critical components in Rust with careful attention to latency, throughput, and correctness.
TypeScript services: Build product-facing APIs and services in TypeScript, integrating backend primitives cleanly and safely.
System quality: Own testing strategy, observability, incident response, and performance profiling across the stack.

Must-haves

Strong backend fundamentals: Concurrency, distributed systems, consistency, performance, and reliability.
TypeScript and Rust fluency: Comfort working in TypeScript for APIs, services, and tooling, plus lower-level languages such as Rust for latency-sensitive systems.
Systems mindset: Reason about trade-offs, keep designs simple, and prevent edge-case failures.

Strong bonus points

Quant or trading systems experience: Market data, execution, risk, simulation, or adjacent backend systems.
Exchange and derivatives exposure: Built or worked on exchanges, perps, derivatives, or margin and risk engines.
Low-latency engineering: Familiarity with efficient data structures, profiling, and cache-aware engineering patterns.
Storage systems: Experience with Postgres, LMDB, RocksDB, event logs, or similar storage layers.
Crypto-native infrastructure: Comfort with wallet and custody patterns or onchain and offchain reconciliation.

Interview process

Technical screen: A short conversation covering systems and coding fundamentals.
Architecture discussion: A deeper trading-systems conversation around perps, risk, and order flow.
Practical exercise: A small backend component or design review.

To apply

notional.xyz