Specialist, Business Analyst - Content Studio

Merck; Hyderabad; On-site; INR 1,200,000 - 2,400,000; Full time

Job summary

Merck's Digital Human Health (DHH) unit is seeking a Product Owner for Content Studio to turn business needs into build-ready requirements and user stories for AI-enabled content creation.

You will own backlog readiness, collaborate with engineering, UX, and partners, coordinate UAT, and ensure compliance with brand rules, AI labeling, auditability, and risk controls, while aligning with stakeholder priorities and delivery schedules.

Responsibilities

• Run discovery with business users to understand workflows, pain points, and desired outcomes before writing requirements.
• Write user stories with clear acceptance criteria, edge cases, and dependencies, and resolve open questions before development starts.
• Prepare refinement and sprint planning with the Product Owner. Bring a ready, sized backlog and a recommended priority order.
• Turn workflows into clear product behavior, including user flows, error handling, and human-in-the-loop review points.
• Manage requirement changes and log scope decisions so everyone knows what changed and why.

Job description

About Digital Human Health (DHH)

Digital Human Health (DHH) connects technology, data, and people to enable and accelerate Human Health business across global markets. DHH supports commercial and medical teams by delivering customer-centric digital platforms, data capabilities, and technology-enabled operating models that enable flexible go-to-market approaches, actionable insights, and personalized customer experiences in a regulated environment.

Within DHH, the Content Creation & Storage pillar of Digital Content & Customer Experience (DCCE) builds the platforms and capabilities that help Human Health create compliant, on-brand content faster. As part of the Content Accelerator, the pillar is moving content creation from manual production to AI-generated content that is built to brand and compliance standards from the start, combining agentic content creation platform (Content Studio), Adobe capabilities, and the design system.

Role Purpose

Own business analysis for Content Studio, AI-enabled content creation capability. Turn business needs into clear, build-ready, and traceable requirements, and work hands-on alongside engineering, UX, and implementation partners from discovery through release.

The role is the Product Owner's day-to-day partner. As the person grows, they will be expected to take on product ownership for defined Content Studio features or components, including backlog decisions, stakeholder alignment, and release outcomes.

Scope of Ownership & Adjacent Responsibilities

• Accountable for (owns the deliverable and its quality):
• Content Studio requirements: functional specifications, user stories, and acceptance criteria for assigned features and components.
• Backlog readiness: stories meet the agreed Definition of Ready before sprint planning.
• The product source of truth (Confluence/JIRA): workflows, business rules, input/output requirements, integrations, known limitations, and the decision log.
• Requirements traceability from business need to story, test, and released functionality.
• UAT coordination with business users, including tracking feedback and gaps through to closure.
• The user feedback loop: capturing feedback from content creators, brand teams, and reviewers, and turning it into prioritized backlog items.

• Partners on (contributes; another role makes the final decision):
• Backlog prioritization and release scope, with the Product Owner.
• Solution design and technical approach, with engineering and implementation partners.
• Integration requirements with adjacent platforms (e.g., Adobe capabilities, design system, guardrails/rules engine, Veeva Vault PromoMats), with the respective product teams.
• Adjacent: Flex across other Content Creation & Storage workstreams (e.g., Adobe Brand Intelligence experiments, design system) as priorities shift.

Key Responsibilities

Requirements & Backlog Ownership

• Run discovery with business users to understand workflows, pain points, and desired outcomes before writing requirements.
• Write user stories with clear acceptance criteria, edge cases, and dependencies, and resolve open questions before development starts.
• Prepare refinement and sprint planning with the Product Owner. Bring a ready, sized backlog and a recommended priority order.
• Turn workflows into clear product behavior, including user flows, error handling, and human-in-the-loop review points.
• Manage requirement changes and log scope decisions so everyone knows what changed and why.

Working with Tech Teams & Validation

• Work closely with engineering during sprints to clarify requirements and resolve open questions quickly.
• Get hands-on with Content Studio's AI features (e.g., prompts, agent inputs/outputs, brand rules) to understand how they behave and confirm they meet requirements.
• Build a working understanding of the platform's architecture, integrations, and APIs to have informed discussions with engineering and partners.
• Coordinate UAT with business users, capturing feedback, defects, and gaps and following them through to resolution.

Documentation, Governance & Communication

• Keep the Content Studio source of truth current and easy to understand for new team members, business users, engineers, and partners.
• Maintain the decision log, open questions, risks, and dependencies across internal and partner teams.
• Build compliance into requirements, including human-in-the-loop controls, AI labeling, auditability, and alignment with AI and content policies.
• Share concise updates on progress, decisions, risks, and releases with the Product Owner and stakeholders.

Stakeholder & Vendor Collaboration

• Facilitate requirement workshops and working sessions that end in clear decisions and owners.
• Review vendor and partner solutions against documented requirements, and raise gaps early.
• Act as the bridge between business and technical teams so both share the same understanding of what is being built and why.

What Success Looks Like

Stories reach sprint planning ready to build, with little rew