Team Lead · Capital Markets

Building resilient capital-market platforms — from the problem, not the technology.

Engineering leader with 12+ years in software and 8+ years architecting and modernizing mission-critical trading systems. The person management consults when a technical problem is important, unclear, or business-critical.

Ownership  ·  Pragmatism  ·  Architectural Thinking

View selected work Download CV ↓
Portrait of Niladri Neogy

Niladri Neogy

Capital Markets & Trading Platforms

  • Based in Kolkata, India
  • Domain Exchange-integrated trading (NSE / BSE)
  • Stack .NET · WebSocket · SQL Server · Flutter
12+Years in engineering
8+Years in capital markets
~5kConcurrent live-data users
<1msMarket-data latency
10+Years hiring engineers
01 — About

I start with the business problem, then choose the simplest architecture that lasts.

I don't describe my work in frameworks. I describe it in business problems, architectural trade-offs, user impact, and delivery. Over the last few years I've grown from writing software into being the technical decision-maker management consults before committing to major initiatives — evaluating feasibility, reducing uncertainty, and owning delivery from idea to production.

My niche is deep and hard to replace: low-latency, exchange-integrated trading systems — OMS, market-data broadcasting, binary packet processing, and protocol-level integration with NSE and BSE. I modernize legacy platforms incrementally and use AI as an accelerator while keeping full ownership of the architecture.

02 — Core expertise

Three areas where I create leverage.

Architecture & Engineering

  • Solution & backend architecture
  • API design · domain-driven modular design
  • Real-time & event-based communication
  • Legacy platform modernization

Capital Markets

  • OMS · exchange connectivity (NSE / BSE)
  • Market-data broadcasting · binary packets
  • Equity, F&O, currency & commodity
  • IPO bidding · account opening · margin allocation

Leadership & Delivery

  • Technical leadership & feasibility calls
  • Technical hiring & interviewing (10+ yrs)
  • Mentoring to individual strengths
  • Vendor coordination · Agile / Scrum
03 — Selected initiatives

Decisions I owned, end to end.

Pick an initiative to see the problem, the call I made, and what changed.

Core platform

Exchange Communication Backend

  1. Problem

    Every price a client sees and every order they place depends on one backend talking to NSE and BSE correctly, in real time.

  2. What I own

    The full backend end to end: receiving and parsing exchange broadcast data, streaming it to the front ends, routing orders to the exchange, and processing exchange responses.

  3. Outcome

    8 exchange-connected backends running the business, with zero missed trading sessions in 5 years.

Follow the data. Click any step.

Market data
Orders

NSE and BSE publish live market data as binary broadcast packets throughout the trading session.

Broadcast parsingOrder routingReal-time status
Signature initiative

WebSocket Platform Modernization

  1. Problem

    The legacy TCP market-data layer carried a large attack surface, was complex to integrate with, and stood in the way of new iOS, Android, and web apps.

  2. Decision

    Proposed, justified, and led its replacement with a standards-based WebSocket architecture.

  3. Outcome

    iOS and Android apps unlocked, with the web platform migration next. The broadcast engine streams to ~5k concurrent mobile users at sub-millisecond latency.

Protocol
Standards-based WebSocket
Attack surface
Reduced
Integration
Simpler, standard
Platforms
iOS + Android live, web next
Live reach
~5k concurrent · <1 ms
~5k concurrent users<1 ms latencyTCP → WebSocket
Delivery

Cross-Platform Mobile Trading

  1. Problem

    A year-long product gap: clients had no iOS app.

  2. Decision

    Build the backend first so Android and iOS share one platform. Recruited and led the Android developers, and personally shipped the iOS app with AI-assisted Flutter, with no prior Flutter experience.

  3. Outcome

    Both apps in production on one backend, owning flow, API contracts, and UX, and about Rs. 5 lakh in outsourcing avoided.

One shared mobile backend
AndroidTeam recruited & led
iOSBuilt personally · AI-assisted Flutter
Android + iOSAI-assisted Flutter~Rs. 5 lakh saved
Pragmatic trade-off

Trading API & Architecture Decision

  1. Problem

    A backend trading API for web and mobile clients, and a proposal to build it as microservices.

  2. Decision

    Recommended a domain-based modular architecture instead, and designed and built the API that way.

  3. Outcome

    Clear domain boundaries without operational overhead the team would gain nothing from. A decision to reduce complexity, not follow a trend.

Proposed · Microservices

  • More services to deploy, monitor, and keep in sync
  • Consistency-critical financial workflows split across services
  • Operational overhead for a focused team

Chosen · Domain-based modules

  • Clear boundaries by business domain
  • Tightly coupled workflows stay consistent
  • Right-sized for the team running it
API designDomain-drivenPragmatic trade-off
Under deadline

NSE Encryption — Protocol Debugging

  1. Problem

    An undocumented exchange change to order-request packet encryption, minimal vendor support, and a regulatory deadline.

  2. What I did

    Reverse-engineered the change, debugging at the binary-protocol level for more than 10 days.

  3. Outcome

    The fix was delivered one week before the regulatory deadline.

  1. Change hitsUndocumented, little vendor help
  2. 10+ daysBinary-level debugging
  3. Fix shippedOrder flow restored
  4. DeadlineStill one week away
Binary protocolReverse-engineering1 week early
In progress

Exchange Integration — BSE F&O · NSE Commodity

  1. Problem

    Expanding what the firm can offer clients means integrating new exchange segments from scratch.

  2. What I own

    The BSE Futures & Options integration from the ground up: two-way order flow, packet structures, and real-time derivatives broadcast.

  3. Next

    NSE Commodity is the next integration in the pipeline.

  1. BSE F&OIn progress · order flow, packets, broadcast
  2. NSE CommodityNext in the pipeline
Order flowDerivatives broadcastGreenfield
Product

Digital Account Opening

  1. Problem

    Account opening was a manual, physical process that took days and capped volume.

  2. What I did

    Replaced it with a fully paperless journey (KYC, document upload, e-signature), owning the flow, backend, and UX.

  3. Outcome

    Faster onboarding at ten times the volume. Now building the next-generation onboarding system and its API.

BeforeAfter
Time to onboard
~2 days
< 1 day
Accounts per day
< 10
~100
~2 days → <1 day<10 → ~100 / dayPaperless

Also: full trading-backend Disaster Recovery replica · client collateral-to-exchange margin transfer · high-volume transactional email delivery (queue & retry) · trading-website modernization.

04 — Experience

A career that followed problems, not hype.

  1. Team Lead2018 — Present

    Shriram Insight Share Broker Ltd · Kolkata

    Technical lead for a business-critical trading platform — ~3–4k clients/day across equity, F&O, currency & commodity; 8 exchange-connected backends, 5–6 services, 7–8 SQL Server databases. Promoted from Software Engineer (2018–2021) to Team Lead (2021–present). Primary escalation point and feasibility advisor; drove every major modernization initiative.

  2. PHP Developer2017 — 2018

    Express Atmospheric Science & Research · Kolkata

    Built and maintained the Farmneed SaaS portal with role-based secured workflows; integrated weather/data APIs for real-time crop alerts and documented REST endpoints for mobile.

  3. Project Manager2015 — 2017

    4I BRANDZ · Kolkata

    Delivered 40+ web/mobile projects on scope and deadline — including an online streaming platform (2016) and the company's first payment-gateway integration (2015).

  4. Trainee Software Engineer2013 — 2015

    Aasa Globsys · India

    Full-SDLC delivery of government and private-sector projects using PHP, ASP.NET, JavaScript, and SQL Server.

05 — Toolbox

Technologies I actually use.

No buzzword padding, only what I've shipped with in production.

01

Core platform

The backend of the trading platform, its services and APIs.

C#.NET FrameworkASP.NET MVCASP.NET CoreEntity Framework
02

Real-time & exchange

Talking to NSE and BSE and streaming live data to clients.

MultithreadingWindows Services
03

Data

7–8 production databases behind trading, back office, and reporting.

Microsoft SQL ServerMySQL
04

Infrastructure

Hosting and deploying the trading platform's services.

IISWindows ServerGit
05

Mobile

The Android and iOS trading apps on one shared backend.

iOSAndroid
06

AI-assisted development

Faster delivery and legacy migration, with the architecture still mine.

ClaudeOpenAI Codex

Click a highlighted technology to open the project where I used it.

Earlier roles PHP · CodeIgniter · WordPress · JavaScript · ASP.NET

Certifications & education

Certification · Scrum Alliance

Certified ScrumMaster

Agile delivery with Scrum: running sprints, clearing blockers, and keeping a team focused on shipping.

Certification · PeopleCert / AXELOS

ITIL 4 Foundation

IT service management: incident, change, and service continuity, the discipline behind a platform that never misses a trading session.

Education · 2009 – 2013

B.Tech, Computer Science & Engineering

West Bengal University of Technology (WBUT)

CGPA 8.15 / 10

Continuous learning AI-assisted engineering · Software architecture · Capital-market technology · Cloud

06 — Contact

Let's talk architecture, trading systems, or hard problems.

Open to conversations about solution architecture, capital-market platforms, and engineering leadership. The fastest way to reach me is email.

Email me Download CV ↓