BE-04 · Backend engineering · Priority
Senior Backend Engineer - Platform & Indexing
Build the service layer for dataset metadata, compute-job orchestration, event indexing, receipts and operational reporting.
- Location
- Remote · APAC overlap
- Engagement
- Full-time or long-term contract
- Path
- Core opening
Mandate
Make off-chain runtime state reliable, observable and reconcilable against the protocol source of truth.
Model artifacts, datasets, evaluation records and high-frequency runtime state do not belong on a public chain. They require a disciplined service layer with explicit provenance, retention, access and recovery rules.
First 90 days
Four operational outcomes that make state dependable.
- 01
Define the canonical model for datasets, models, jobs and compute receipts.
- 02
Build idempotent event ingestion with replay and reconciliation support.
- 03
Ship versioned APIs with meaningful error contracts for product clients.
- 04
Add operational visibility for lag, mismatch and failed work.
You will own
- Design TypeScript services and relational data models.
- Consume and reconcile Grid events without double-processing.
- Implement audit-friendly change histories and access boundaries.
- Create API contracts, integration fixtures and recovery runbooks.
- Own queues, retries, observability and production debugging.
Strong fit
- Strong Node.js, TypeScript and SQL production experience.
- Experience with event-driven or data-intensive systems.
- Comfort with idempotency, consistency and reconciliation tradeoffs.
- Clear API design and operational debugging skills.
- Working understanding of on-chain events and RPC services.
Stack
Application
Show how you kept an event-driven system correct under failure.
Share public or sanitized material only. Do not send confidential source code, private keys or client-restricted documents.
- An event pipeline you operated in production
- A reconciliation failure you designed for
- An API contract you improved across teams
