Senior Product Manager - Trading Platform, Backend & Data; India, Chennai

About Go Charting

GoCharting is a web-native charting and trading workflow platform with institutional-grade orderflow and DOM tools — footprint/cluster charts, volume/market profile, cumulative delta, imbalance charts, DOM trading. We are the only platform that delivers these capabilities fully on the web. Comparable to Trading View for general charting, but differentiated as the leader in the professional orderflow niche. PE-acquired and funded in 2025, profitable, 3M+ registered traders globally, with a mandate to scale 10x over 4 years.

A US rebrand is underway and multi-asset coverage (US equities and options) is being added — the platform is entering its most important chapter, and the backend is where that growth is won or lost.

This is a senior, hands-on product role at the core of how GoCharting works. The product's moat is technical — real-time market data, orderflow, and the systems that move it — and this role owns the part of the roadmap that makes that moat deeper. You will run backend and platform product work and own our third-party data integrations end-to-end: the exchange feeds, broker connections, and market-data vendors that everything traders see is built on.

You are the product counterpart to a backend engineering team we are scaling right now — new senior engineers on the payments/billing platform, on market-data and broker connectivity, and on the core platform and SDK. Your job is to sequence and scope that work into a coherent roadmap, write the specs engineers build from, and hold the line on quality and reliability.

You report to the Head of Product and partner daily with the CTO and his engineers, with Business Development (who sign the deals), and with QA and Support. This is an individual-contributor role — no direct reports, plenty of ownership.

You move fast, write clearly, and make decisions with engineers, not over them. You are comfortable in the technical detail — APIs, data contracts, latency, schemas — without needing to be told what matters. In year one, success looks like a backend roadmap that ships, faster and more reliable data integrations, and a platform that stops being the thing users complain about.

• Own the backend & platform roadmap — market-data services, real-time pipelines, APIs, the SDK, and the systems behind charts, alerts, and trading — write clear specs and acceptance criteria, and partner with engineering from design through ship
• Own third-party data integrations end-to-end — exchange feeds, broker connections, and market-data vendors, from evaluation through onboarding to production — and build the playbook so the tenth integration is faster than the first
• Manage the provider relationship on the product side — scope, data quality, licensing constraints, SLAs, and the day-to-day of keeping feeds healthy (BD owns the commercial deal; you own the technical delivery)
• Make the trade-offs that matter — latency, reliability, cost, and coverage — and defend them with data
• Run dependency management — work across Product and Engineering so backend work is well understood, scoped, and scheduled to unblock other teams, sequenced against US expansion and ROI
• Treat quality and reliability as product features — define what “good” means, measure against it, triage data and platform issues with engineering, and close the loop with Support and power users

Must-haves:

• 6–9 years in product management
  , with real depth on backend, platform, API, or data-heavy products — you've owned infrastructure/data as a product, not just user-facing features
• Trading, investing, fintech, or financial-data background — you understand market data and the audience
• You are technical — comfortable with APIs, data models, schemas, and latency/reliability trade-offs, and able to hold your own in an engineering discussion (you read specs and schemas natively; you don't need to write production code)
• You have shipped third-party or data integrations end-to-end — evaluating providers, onboarding feeds, and owning data quality in production
• Strong written communication — you write specs and decisions engineers can build from without a meeting
• Shar…