Senior Software Architect

Senior Software ArchitectFunction : Engineering - Architecture

Reports to : CTO / VP Engineering & Product Development

Direct reports : None - technical authority and mentorship across all engineering squads

Experience : 12+ years building software, including 5+ years as an architect or principal engineer

Working Shift : 11 : 30 AM to 8 : 30 PM

The role :

We are hiring a Senior Software Architect to own the technical design of the systems Delta6Labs builds across exchanges, wallets and custody, trading infrastructure, and the white-label core that underpins our client deployments. You will report to the CTO / VP Engineering & Product Development and work across every squad without owning any of them.

Education : B.E. / B.Tech / M.C.A. in Computer Science, Engineering or a related discipline. Equivalent practical experience considered.

What you will own : System and platform architecture :

• Design end-to-end architectures for new platforms and major subsystems from context and constraints through service decomposition, data models, integration contracts and deployment topology.

• Design high-throughput, low-latency paths order matching, order-book and market-data distribution, risk checks, liquidity routing against explicit written latency and throughput budgets rather than hopeful assumptions.

• Design wallet and custody architecture : hot, warm and cold segregation, MPC and multi-signature schemes, key lifecycle and rotation, withdrawal approval and limit flows, and integration with providers such as Fireblocks.

• Own data architecture relational modelling, event schemas and their evolution, caching strategy, analytical and time-series stores, retention and data-residency requirements across jurisdictions.

• Define non-functional architecture explicitly : availability and latency targets, failure domains and blast radius, degradation behaviour, capacity headroom, and disaster-recovery design with real RPO and RTO figures.

Reuse, the white-label core and technical strategy :

• Own the architectural line between the reusable platform core and client-specific extension so customisation happens at configuration and extension points rather than by forking, and one client's requirement does not become everyone's regression.

• Design tenant isolation, configuration and feature-flag models that let us onboard a new client without re-architecting, and ship a fix to one without endangering the rest.

• Maintain reference architectures and reusable building blocks for our recurring product shapes - CEX, derivatives, wallet, launchpad so each engagement starts from proven ground rather than a blank page.