> Markdown version of [/jobs/ext/3958987-product-owner-adobe-target](https://www.wearedevelopers.com/jobs/ext/3958987-product-owner-adobe-target). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Product Owner - Adobe Target

- **Company:** Motion Recruitment
- **Location:** Charlotte, NC, United States
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** Adobe Experience Manager, Scrum Methodology, E2e Testing, Test Case, Adobe Target
- **Published:** October 27, 2026
- **Apply:** https://www.thejobnetwork.com/job/d74941f8-8450-4764-91a0-b23fad582976/product-owner-adobe-target

## About the Role

* 4+ years of Digital Product Management experience operating within an enterprise-level organization.
\n

 * Demonstrated history working within technically complex environments with solid technical acumen.
\n

 * Hands-on experience with personalization and experimentation platforms, with a strong preference for Adobe Target.
\n

 * Working knowledge/exposure to Adobe Experience Management (AEM).
\n

 * Demonstrated expertise in requirement gathering, backlog prioritization, and user story writing (including acceptance criteria).
\n

 * Strong background in leading and overseeing end-to-end testing activities, test case definition, and defect tracking.
\n

## Description

We are seeking a Digital Product Owner with strong technical acumen to drive personalization and experimentation initiatives in a technically complex, enterprise-level digital environment. In this role, you will lead requirement gathering, write clear user stories, manage the product backlog, and collaborate cross-functionally to ensure high-quality, testing-first digital experiences., n
\n

 * Manage and prioritize the product backlog to ensure timely feature delivery aligned with sprint goals.
\n

 * Gather business requirements and translate them into detailed user stories with clear acceptance criteria.
\n

 * Oversee testing activities-including test planning, defining test cases, defect tracking, reviewing test results, and approving feature readiness.
\n

 * Partner closely with the Scrum Master to remove blockers, keep sprints on track, and track progress against sprint commitments.
\n

 * Lead meetings to clarify requirements, review progress, and resolve issues across engineering, content, and stakeholder teams.
\n

 * Collaborate directly with engineering and content teams to refine specifications and guide technical implementation.
\n

 * Provide regular sprint progress updates, roadmaps, and status reports to key business stakeholders.
\n

 * Support release planning activities and ensure operational readiness prior to deployment.
\n