16 Nov
|
Digital India
|
Noida
16 Nov
Digital India
Noida
About the Platform The Digital Office Platform is a multi-tenant, configuration-driven government case-management platform that lets many independent government bodies each configure their own case lifecycle
• data model, intake forms, versioned workflows, roles, SLAs, notifications, audit and reporting
• and run real cases end-to-end without custom code per tenant. It is built as ~20 independent Spring Boot microservices (engines), each owning its own PostgreSQL database, coordinated behind a Next.js web application, and deployed hosting-agnostic on sovereign / government cloud using open-source components. Tenant isolation is by tenant_id; published workflow versions are immutable and live cases pin to their version; security and data boundaries fail closed. Role and Responsibilities
• Elicit, analyse and document requirements for each onboarding government body; prepare the BRD / FRD with unique requirement IDs, acceptance criteria and a requirement traceability matrix linking every requirement to a design element and a test case.
• Translate each body’s case lifecycle into configuration — business object types and fields, dynamic intake forms (sections, rows, columns, conditional visibility, calculated fields), versioned workflows (stages, tasks, actions, transitions), roles / personas, rules / decision tables, SLAs, notification templates and dashboards — so a recent office is stood up by configuration, not code.
• Define the workflow-versioning and in-flight case-migration policy: published versions are immutable, live cases pin to the version in force when filed, and any migration between versions is explicit, mapped stage-to-stage and audited.
• Specify SLA, clarification, escalation and reminder rules, and the notification matrix (EMAIL / SMS / WhatsApp / push / in-app / webhook)
per workflow stage and actor class.
• Specify role-based access needs across the four actor classes — platform admin, tenant staff, citizens / applicants, and second parties / respondents — and the RBAC / ABAC / policy model with the IAM owner.
• Define reporting and dashboard requirements as curated, tenant-scoped datasets and named metrics (never ad-hoc cross-tenant SQL), and the KPIs each role needs.
• Own the product roadmap, MoSCoW prioritisation, release phasing and scope discipline across the ~20 engines; chair backlog grooming and sprint planning.
• Coordinate stakeholders across government bodies, DIC and the platform team; plan and drive UAT, capture sign-off, and manage change requests through a controlled process.
• Author and maintain product documentation — user manuals per actor class, configuration playbooks, release notes and onboarding guides. Qualifications and Experiences Bachelor's degree in any discipline with 5+ years of experience in business analysis/ product management for enterprise or government IT systems; experience with case-management, grievance-redressal or workflow platforms preferred. Required Skill Set
• Strong requirements engineering and documentation (requirement specifications, manuals, traceability) and stakeholder management across technical and non-technical audiences.
• Business-process and workflow modelling (BPMN an advantage); ability to express case lifecycles as configuration rather than code.
• Working understanding of multi-tenant SaaS, metadata / configuration-driven platforms, RBAC / ABAC, SLA design and notification workflows.
• Knowledge of GIGW, accessibility and DPDP (Act 2023 / Rules 2025) compliance as they affect requirements.
• Comfortable reading REST API contracts, data models and configuration schemas; proficient with Agile tooling (Jira / Confluence).
📌 Product Manager (Noida)
🏢 Digital India
📍 Noida