Our client is a leading Indian gaming group with international operations across game formats and teams in India, Singapore, Berlin and the US. They invest in, acquire and build game companies globally. Their Central Tools team builds the shared tools and agents that every studio in the group runs on, across rummy, casual and shooter games in India, the US and Europe.
They are standardising the group's data and tools in four layers: one warehouse, an observability layer of dashboards and analyst agents, an action layer for experimentation, configuration and ML, and an agentic layer that automates the actions.
Sigma is the platform that houses all of these tools: one sign-in, one permission model and one UI. The tools on it include the data warehouse platform, the data catalog, the experimentation platform, the creative dashboard, and agents such as the DA agent and the RC agent. Their users are internal teams across the group — analysts, UA and creative teams, product teams, and the engineers and analysts who onboard data. Most of them are experts in their own field.
The role
Engineers build Sigma's tools. You make them usable by the people they are for, and consistent with each other, so someone who has learned one tool can pick up the next.
You own user flows and user experience on Sigma itself and on its most important tools. Priorities and the cross-tool roadmap are set by the team lead. You work with platform engineers who build Sigma's services, a frontend engineer who builds its UI, and the ML engineers who build its agents.
The users are experts, and the flows are not consumer flows. Requesting and approving access, setting up an experiment, or reviewing an action an agent proposes each need their own design — and they need to work the same way across six or more tools.
What you will work on
Platform flows: sign-in, access requests and approvals on Sigma's central permissions, admin views of who can see what, and navigation and discovery across tools.
Agents (DA, RC): how a user asks a question, how a verdict or proposed action is shown with its evidence, and how it is approved, rejected or overridden, with every override recorded.
Experimentation platform: setting up a test, checking it before launch, and reading the results.
Data catalog and warehouse platform: finding a table or metric and deciding whether to trust it (owner, freshness, definition), and onboarding a new data source through configuration.
Creative dashboard: scanning creative performance and acting on it.
Shared patterns: permission states, navigation and review flows that behave the same way in every tool, built with the frontend engineer.
How you will work
Specs that cover edge cases and permission states, so engineers can build from them without a meeting.
Wireframes and prototypes, with the frontend engineer.
Usability sessions with internal users, and iteration on what they show.
Instrumentation of adoption and task success, release QA, and docs and onboarding for each tool.
What you need
4–5 years as a product manager, or PM-shaped work on technical products. Years in engineering or analytics before that count in your favour.
At least one flow or feature you specified and shipped to real users — you can explain a decision you made inside it, the user evidence behind it, and what changed as a result.
Experience with technical users or products: internal tools, developer or data platforms, B2B or SaaS, analytics or admin products, or a hands-on engineering or analytics background.
Enough technical fluency to understand how a permission model, an API, a data model or an experiment works, and to discuss trade-offs with engineers.
Clear writing: specs, decision notes and docs that others can act on.
Strong signals
Identity and access: SSO, role-based access, access-request and approval flows, audit views.
Experimentation platforms, feature flags, BI or metrics products, or data catalogs.
Human-in-the-loop AI: flows for reviewing, approving and overriding agent or model actions, with override rate or evaluation as acceptance criteria.
Design-system or multi-product consistency work.
Prototyping in Figma or in code.
SQL for your own usage and adoption analysis.
Gaming or ad-tech.
This role is not
Project or programme management, scrum or business analysis without flow ownership; growth marketing (campaigns, CRM journeys, ROAS reporting); setting the cross-tool roadmap; or building the UI or the systems themselves.
#J-18808-Ljbffr