Product Manager

About StanceBeam
StanceBeam is a Bengaluru-headquartered sports technology company. We built the world's first commercial smart cricket bat sensor and have since grown into a full performance-technology stack: sensors, ball tracking, computer vision, video analytics and an affordable Decision Review System. Our technology is deployed across India, Australia, New Zealand, South Africa, the United Kingdom and the United States, and our work has been recognised through the KPMG Game Changers Award, the Karnataka Government's Elevate100 programme and a granted patent portfolio.
About the role
You will be the product manager across StanceBeam's product portfolio: the mobile and tablet applications our players, coaches and operators use, the web platforms and administration tools behind them, and the sensor, ball-tracking and computer-vision systems that feed them. A significant part of the role is our international client engagements.
The product is a connected suite rather than a single app: consumer applications on iOS and Android, tablet applications used in live operational settings, web-based administration portals and websites, with integrations across hardware, access control, payments and analytics.Underneath that sit our sensors, ball tracking and computer vision.
You will work directly with the founders and directly with our clients. The founders will set direction and commercial priorities with you, and you will be working directly with international clients and product teams.
Why this role
Ownership of live products with real users, in facilities, academies and matches
A rare mix of software, hardware, AI, and computer vision in one portfolio.
International exposure: clients in the US, UK, Australia and the Gulf, overseas travel a few times a year, and work that spans time zones.
A small, senior team where the scope is as large as you can handle.
What you will do
Discovery and definition
Own the product backlog across the portfolio and keep it prioritised, current and understood by everyone who works from it.
Talk to the people who actually use the product. Separate what they ask for from the job they are trying to get done, and write up the difference.
Write PRDs, user stories and acceptance criteria that engineering and QA can build and test from, and a proper technical specification with a rollback plan for anything that touches firmware or devices.
Prioritise in a way you can defend, showing the reasoning and the trade-off, not just the ranking.
Where hardware meets software
Keep track of which app versions, firmware versions and hardware revisions work together, and plan releases accordingly.
Plan staged rollouts for firmware and model updates, with a kill switch and a rollback plan written before launch.
Take responsibility for the data pipeline from device to screen. Everything downstream is only as good as what comes in.
Plan around hardware lead times. A software fix ships in a sprint; a firmware or hardware change is measured in months, and sequencing around that is your job.
Where the physical world is involved, run structured pilots rather than live experiments, with defined cohorts and clear exit criteria.
Client-facing work
Be the day-to-day product contact for our clients' product and operations teams - for features, releases, defects and timelines.
Run weekly working sessions, sprint demos and release walkthroughs.
Capture incoming requests, diagnose the underlying business need, and turn them into considered proposals
Translate technical and hardware constraints into language the client can act on, and translate their operational reality back into requirements the team can build.
Protect the integrity of the platform. Know when a one-off request would fragment the product, and be able to say no while keeping the relationship intact.
Assess change requests for effort and timeline impact, present the trade-off clearly, and bring anything with commercial or contractual implications
Keep the client informed in writing: release notes, status summaries and decision logs, so nothing important lives only in someone's memory.
Delivery, quality and release
Run sprint planning, refinement and reviews with the engineering and QA leads, and keep the delivery plan realistic and current.
Coordinate acceptance testing with clients: prepare the scope, support them through it, triage findings and drive the agreed fix list to closure.
Own release readiness: release notes, environment checks, sign-off criteria and the go/no-go call. Flag risk before a date slips, not after.
Work with the technical lead on third-party integrations so partner and vendor commitments stay aligned with our release calendar.
Make a considered call on technical debt: when to accept it to hit a hardware-linked date, and when it is too risky to defer.
Contribute to operational readiness for each launch: standard operating procedures, administrator playbooks, training material and support documentation.
What we are looking for
Essential
6 to 10 years in product management, business analysis or a closely related role, with clear ownership of a backlog and written specifications.
Direct client-facing experience. You have run meetings with a client, taken difficult questions and been trusted to represent your company without supervision.
Hands-on experience with a product where software meets the physical world: hardware and firmware, sensors or IoT, computer vision, embedded systems or similar. You personally owned part of it rather than sitting next to the team that did.
Experience across more than one platform, for example a consumer app alongside an internal or administrative system.
Comfort working closely with engineers: you can read an API contract or a technical specification, understand why something is hard, and question an estimate without being adversarial.
Agile delivery in practice, sprint planning through to release, not just as a certification.
Confident use of AI tools in your day-to-day work, drafting, synthesising feedback and analysis, with the judgement to know when the output is wrong.
Comfort with ambiguity and a start-up reality. You will often be the person who has to go and find the answer.
Desirable
A technical background: an engineering or computer science degree, or time spent as a developer, data or QA engineer before moving into product. We want someone who can hold their own in a technical discussion and read code when needed.
Interest in sport and sports technology. It is the domain we work in, and curiosity about it will make your product decisions better.
Experience with a product where a machine-learning or vision model was part of the user-facing behaviour.
Experience supporting international clients.
Familiarity with Jira or Azure Boards, Figma, Postman, and an analytics stack

Work arrangement
No