Senior Backend Engineer - Perpetual/Derivatives Platform (SunCrypto)

nJaipur (on-site) | 4–8 years

nWe are building India's next-generation crypto derivatives venue: a perpetual futures platform where every microsecond, every satoshi and every state transition has to be right. We're hiring a senior backend engineer to own the core of that system.

n

nAbout SunCrypto

nSunCrypto is an FIU-IND registered Indian cryptocurrency exchange (Angelic Infotech Pvt. Ltd., FIU registration VA00031314), headquartered in Jaipur. We run a regulated spot exchange serving Indian retail and institutional customers, and we are now expanding into derivatives, starting with perpetual futures built in-house by a small, senior engineering team that reports directly to the CTO.

nWe operate under the Prevention of Money Laundering Act and India's VDA tax regime. That shapes how we engineer: auditability, reconciliation and exactly-once accounting are product requirements, not afterthoughts.

n

nThe role

nYou will design, build and operate the backend services behind our perpetual futures product: the order lifecycle, position and margin engine, real-time market data fan-out, liquidity and hedging integrations with global venues, and the ledger that ties it all together.

nThis is a hands-on senior individual-contributor role with real architectural ownership. You will write code most days, review the code of others, be on the on-call rotation for the systems you ship, and be trusted to make technical decisions that a CTO would otherwise have to make.

nThe problems are hard in the way exchange problems are hard: hot paths that cannot block, balances that must never drift, and a market that never closes.

n

nWhat you will own

nOrder and position engine

n

n
- Design and implement the order lifecycle for perpetual contracts, placement, matching hand-off, partial fills, cancels, amendments - with strict sequencing and deterministic replay.
n
- Build the position, margin and PnL engine: mark price, funding rate application, maintenance margin checks, liquidation triggers and insurance-fund logic.
n
- Model order books and state in Redis (sorted sets, Streams, Lua-scripted atomic operations) and persist authoritative state in MySQL 8 with correct isolation and locking.
n

nFinancial correctness and the ledger

n

n
- Implement a double-entry ledger with decimal arithmetic end-to-end, no floating point anywhere near money.
n
- Guarantee idempotency and exactly-once semantics across order, fill, funding and transfer events, including crash-recovery and replay.
n
- Build reconciliation jobs that prove our books balance against external venues, wallets and internal accounts, every hour of every day.
n

nReal-time market data and connectivity

n

n
- Scale our WebSocket layer (ws / uWebSockets.js)



to tens of thousands of concurrent connections: sharding, heartbeats, reconnect semantics, message batching and per-client backpressure.
n
- Own REST and WebSocket integrations with Binance, Bybit and OKX futures APIs — signed requests, rate-limit budgets, failover and staleness detection, for pricing, liquidity and hedging.
n

nReliability and operations

n

n
- Run what you build: Docker, Nginx, PM2 on Linux, with Prometheus / Grafana dashboards, alerting and structured logs that make 3 a.m. incidents debuggable.
n
- Write load tests and chaos scenarios for the hot path; define SLOs for latency and availability and hold the system to them.
n
- Raise the engineering bar through design reviews, code reviews, runbooks and mentoring of mid-level engineers.
n

nCore stack : what we expect you to know cold

n

n
- Node.js 20+: deep async internals, event loop, worker threads, clustering, backpressure handling
n
- MySQL 8: transactions, isolation levels, row locking, deadlock handling, partitioning, replication, query tuning
n
- Redis 7: Lua scripting for atomic ops, Streams, Pub/Sub, sorted sets for order books, cluster mode, persistence trade-offs
n
- WebSockets: scaling ws / uWebSockets.js, connection sharding, heartbeat and reconnect, message batching
n
- Financial correctness: decimal arithmetic (never floats), idempotency, double-entry ledgers, exactly-once processing
n
- Concurrency: race conditions, distributed locks, optimistic vs pessimistic locking, sequencer patterns
n
- APIs: REST + WS integration with Binance / Bybit / OKX futures APIs, rate limits, signed requests
n
- Ops: Linux, Docker, Nginx, PM2, Git, monitoring (Prometheus / Grafana), structured logging
n

nMust have

n

n
- 4–8 years of professional backend engineering, with at least 2 years on systems where correctness under concurrency was a hard requirement (payments, trading, ledgers, inventory, booking).
n
- Expert-level Node.js (20+) in production: you can explain the event loop, libuv thread pool, worker threads and clustering from first principles, and know when each is the wrong tool.
n
- Solid MySQL 8: you have chosen isolation levels deliberately, debugged a deadlock from the InnoDB status output, and tuned a query plan that mattered.
n
- Production Redis beyond caching: Lua scripts, Streams or Pub/Sub, and a clear view of AOF / RDB persistence trade-offs.
n




- You have built or scaled a real-time WebSocket service and dealt with the failure modes: slow consumers, reconnect storms, message ordering.
n
- Fluency with financial-grade correctness: decimal libraries, idempotency keys, double-entry accounting, exactly-once processing.
n
- Comfortable on Linux with Docker, Nginx, PM2, Git and a monitoring stack; you have been on call and improved the thing that paged you.
n
- Clear written and verbal communication: design docs, incident write-ups and pull-request descriptions that others can act on.
n
- Based in, or willing to relocate to, Jaipur.
n

n

nGood to have

n

n
- Rust or Go: the ability to read and contribute to a Rust/Go matching engine or risk service is a strong plus.
n
- Domain background: prior work at a crypto exchange, broker, prop desk, or a stock-broking / derivatives firm.
n
- Event pipelines: Kafka, NATS or RabbitMQ for trade, fill and ledger event streams.
n
- Analytical stores: ClickHouse or TimescaleDB for trade, candle and PnL analytics.
n
- Infrastructure as code: Kubernetes and Terraform.
n
- Quant exposure: market making, delta-neutral hedging or options pricing.
n
- Open-source contributions or public writing on distributed systems, databases or trading infrastructure.
n

n

nHow we work

n

n
- Correctness first, then latency, then features. A slow trade is a bug; a wrong balance is an incident.
n
- Small, senior team. No layers between you and the CTO. Decisions are made in design docs and reviews, not meetings.
n
- You ship it, you run it.

Engineers own their services in production, with a humane on-call rotation.

n
- Regulated, and proud of it. We build for auditors as well as traders. Every state change is traceable.
n
- Growth.

Derivatives is SunCrypto's biggest bet. Engineers who build the first version will lead the teams that scale it.

n

n

nInterview process

nWe aim to complete the process within two weeks and give feedback at every stage.

n

n
1. Intro call (30 min): your background, our roadmap, mutual fit.
n
2. Technical deep-dive (60–75 min): Node.js internals, MySQL transactions and locking, Redis atomicity, WebSocket scaling. Conversation, not trivia.
n
3. Take-home or pair-programming exercise: a scoped problem from our domain, reviewed together.
n
4. System design (60 min): design a slice of a perpetual futures platform end-to-end and defend the trade-offs.
n
5. Founder conversation with the CTO and CEO on ownership, ambition and how you want to grow.
n

nCompensation: competitive, benchmarked to senior fintech roles.

nLocation: Jaipur, Rajasthan (on-site / hybrid). Full-time.

n

nWhen you apply, include a link to code you are proud of (GitHub, a write-up, or a system you shipped) and two or three lines on the hardest concurrency or correctness bug you have fixed.

n

n

📌 Senior Backend Engineer (Pragpura)
🏢 Suncrypto
📍 Pragpura