Product design question

You are the Product Manager at Flipkart. How would you design a UMS (User Management System) that would be used by different teams at Flipkart? You do not need to focus on the scalability of the system.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Internal platform product design for cross-team infrastructure: identifying the core needs of multiple internal stakeholder teams.

Clarify scope: a User Management System handling authentication, roles, and permissions used by multiple internal teams at Flipkart, explicitly excluding scalability per the prompt.
Identify the users: internal teams (customer support, marketplace operations, engineering) who each need different levels of access to user account data and actions.
Name pain points: without a unified system, teams likely build redundant access tools, creating inconsistent permission models and security risk.
Design core features: centralized user identity and role-based access control, an audit log of who accessed or modified what user data, and a self-serve permission request and approval workflow for new team needs.
Prioritize role-based access control and audit logging first, since security and compliance (who can see sensitive customer data) are the highest-risk, highest-priority requirements for this kind of system.
Define success as reduction in redundant, team-specific user management tools built outside the central system, and audit compliance coverage.

Explicitly respects the prompt's scoping constraint, focusing on functionality rather than getting distracted by scalability, which was ruled out.
Prioritizes role-based access control and audit logging as the highest-risk requirements, correctly reflecting security and compliance stakes for user data.
Names a concrete adoption metric, reduction in redundant team-built tools, that reflects whether the system actually became the single source of truth.

Spending significant time on scalability considerations despite the prompt explicitly excluding that concern.
Designing a single flat permission model that ignores the genuinely different access needs across different internal teams.

How would you handle a team that needs a permission level not covered by your standard roles?
How would you get teams to migrate off their existing, informal user management tools?