Associate Vice President, Enterprise Digital Platforms
Jobgether · United States · 1 mo ago
RemoteRemoteOTHR$203k–$280k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have responsibilities (accountabilities). We have requirements. We have benefits. We have pay (base salary range). We have schedule (40-hour scheduled work week). Also maybe "About the role" could be the introductory paragraph. We must not repeat job title as heading. Also not include Job ID etc. Remove boilerplate like "This position is listed on behalf of a partner company..." maybe part of about? It's meta but we can keep as part of about? It's not substantive? Might be considered boilerplate but it's describing the role. We'll keep a brief about paragraph.
We need to preserve all substantive information, not invent. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out sections like "How Jobgether Works", "Why Apply Through Jobgether?", "Data Privacy Notice", etc. Also remove "Equal employment opportunity workplace..." maybe considered EEO boilerplate; remove. Also remove "Remote employees must maintain internet service..." maybe schedule? It's a requirement but could be part of schedule? It's about remote work requirements; maybe include in schedule? But schedule section is for work hours; we have "40-hour scheduled work week." That's schedule. The internet speed requirement is more of a remote work requirement; could be part of schedule or maybe not needed. The instruction says include schedule section only if posting actually states them. It does state "40-hour scheduled work week." So schedule section with that. The internet speed requirement maybe could be part of schedule but not explicitly schedule; maybe we can include as a note in schedule? But better to keep only explicit schedule. Could also include as part of responsibilities? Not needed.
We need to output only HTML fragment, no markdown fences.
Structure:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have responsibilities (accountabilities). We have requirements. We have benefits. We have pay (base salary range). We have schedule (40-hour scheduled work week). Also maybe "About the role" could be the introductory paragraph. We must not repeat job title as heading. Also not include Job ID etc. Remove boilerplate like "This position is listed on behalf of a partner company..." maybe part of about? It's meta but we can keep as part of about? It's not substantive? Might be considered boilerplate but it's describing the role. We'll keep a brief about paragraph.
We need to preserve all substantive information, not invent. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out sections like "How Jobgether Works", "Why Apply Through Jobgether?", "Data Privacy Notice", etc. Also remove "Equal employment opportunity workplace..." maybe considered EEO boilerplate; remove. Also remove "Remote employees must maintain internet service..." maybe schedule? It's a requirement but could be part of schedule? It's about remote work requirements; maybe include in schedule? But schedule section is for work hours; we have "40-hour scheduled work week." That's schedule. The internet speed requirement is more of a remote work requirement; could be part of schedule or maybe not needed. The instruction says include schedule section only if posting actually states them. It does state "40-hour scheduled work week." So schedule section with that. The internet speed requirement maybe could be part of schedule but not explicitly schedule; maybe we can include as a note in schedule? But better to keep only explicit schedule. Could also include as part of responsibilities? Not needed.
We need to output only HTML fragment, no markdown fences.
Structure:
About the role
...
Responsibilities
- ... each accountability as li
Requirements
- ... each requirement bullet
Benefits
- ... each benefit
Pay
Base salary range of $203,400–$279,800 per year, with individual compensation varying based on geographic location, skills, experience, education, certifications, and other job-related factors. Eligibility for a bonus incentive plan based on individual and/or organizational performance.
Schedule
40-hour scheduled work week.
We must not include sections like Qualifications, Skills if not distinct; we have Requirements covering qualifications. Could combine but we already have Requirements. No need for Skills separate. We must ensure we don't include filler like "commensurate with experience". Not present. Now extract responsibilities from "Accountabilities" list. Let's list them: - Define the multi-year vision, product strategy, target outcomes, investment roadmap, and adoption agenda for the enterprise digital platform portfolio. - Translate enterprise priorities and customer needs into validated opportunities, assessing desirability, viability, quality, and execution feasibility before scaling investment. - Own portfolio priorities and investment recommendations, balancing evidence, enterprise value, customer impact, risk, dependencies, and time to value. - Lead the enterprise design system as a platform product, including its roadmap, governance, service model, reusable components, standards, and enablement capabilities. - Develop and execute enterprise adoption strategies that translate platform capabilities into priority business and customer use cases. - Partner with business and channel product leaders to establish activation plans, readiness requirements, dependencies, and measurable time-to-value outcomes. - Drive adoption of reusable and accessible design-system components across web, mobile, and associate experiences. - Establish enablement programs, standards, playbooks, communities of practice, and feedback mechanisms that improve usability, consistency, and self-service adoption. - Define product operating model decision rights for demand intake, portfolio prioritization, capability reuse, funding trade-offs, and lifecycle management. - Lead enterprise and design-system governance, including contribution standards, stage-gate decisions, release priorities, exceptions, and adoption requirements. - Partner with technology and engineering leaders to align product, architecture, and delivery roadmaps while maintaining clear accountability for technical execution and operations. - Lead executive portfolio and investment reviews, using evidence and realized value to resolve trade-offs, reallocate resources, manage dependencies, and evaluate strategic vendors. - Establish portfolio objectives, key results, baselines, targets, and executive scorecards to measure performance and value realization. - Track adoption and reuse, experience consistency and accessibility, speed to market, customer and business impact, cost reduction, and return on investment. - Use performance insights to validate benefits, address adoption gaps, reprioritize investments, and communicate progress, risks, and decisions to senior leadership. - Lead and develop directors, senior product leaders, and persistent cross-functional platform teams with clear accountability for strategy, adoption, and outcomes. - Build a customer-focused culture centered on discovery, experimentation, evidence-based prioritization, enterprise reuse, accountability, and continuous learning. - Strengthen product operating model capabilities, roles, ways of working, succession planning, and career development across a matrixed enterprise. That's many; we keep all. Requirements list: - 10+ years of progressive leadership experience in product management, platform strategy, digital transformation, MarTech, experience design enablement, or a related discipline, including leadership of enterprise-scale portfolios and teams. - Demonstrated success operating within a product operating model, including persistent product ownership, cross-functional teams, outcome-based roadmaps, evidence-based investment decisions, and continuous value realization. - Experience with customer engagement and experience-enablement platforms, such as customer data, journey orchestration, content management, consent, personalization, analytics, design systems, or reusable digital services. - Strong understanding of design systems as platform products, including reusable components, accessibility, governance, contribution models, and adoption across design and engineering teams. - Proven ability to establish product decision rights and value-realization frameworks, supported by strong business and financial acumen in a complex or regulated environment. - Exceptional executive influence, communication, and stakeholder-management skills, with experience leading senior leaders and high-performing teams across business, design, and technology. - Experience with Adobe Experience Platform capabilities such as Real-Time CDP, Journey Optimizer, Customer Journey Analytics, Adobe Analytics, or Adobe Experience Manager is preferred. - Experience with next-best-action, decisioning, AI or machine-learning-driven personalization, propensity models, and experimentation frameworks is preferred. - Experience in healthcare, financial services, insurance, or another highly regulated consumer industry is preferred. - Experience rationalizing platforms, increasing capability reuse, and retiring duplicative technologies or solutions is preferred. - Strong strategic thinking, organizational leadership, prioritization, and decision-making skills, with the ability to navigate complex enterprise environments and drive measurable outcomes. Benefits list: - Fully remote position within the United States. - Base salary range of $203,400–$279,800 per year, with individual compensation varying based on geographic location, skills, experience, education, certifications, and other job-related factors. (But we already have Pay section; maybe we should not duplicate salary in benefits; but benefits list includes that line; we can keep it in benefits but also have Pay section. However we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary info somewhere. We have Pay section for salary; we could still include the salary line in benefits but that duplicates. Better to keep salary only in Pay section and not repeat in Benefits. However the benefits list includes that line as part of benefits; but we can treat it as part of Pay. The instruction says preserve all substantive information; we can keep it in Pay and not duplicate in Benefits. That's still preserving. We'll omit the salary line from Benefits to avoid duplication but still have it in Pay. Other benefits: - Eligibility for a bonus incentive plan based on individual and/or organizational performance. - Medical, dental, and vision benefits. - 401(k) retirement savings plan. - Paid time off, company holidays, and personal holidays. - Paid parental and caregiver leave. - Short-term and long-term disability coverage. - Life insurance and additional employee benefits supporting whole-person well-being. - 40-hour scheduled work week. (But we have Schedule section; we could keep schedule separate; but we can keep schedule in Schedule section and not duplicate in Benefits.) - Occasional travel to offices for training or meetings may be required. - Remote employees must maintain internet service with at least 25 Mbps download and 10 Mbps upload speeds and work from a dedicated space that protects confidential health information. (This is more of a requirement; maybe we could include in Schedule? but it's not schedule; maybe we could add a note in About? But we can keep as a separate requirement? Not listed as a requirement; but it's a condition. Could be part of Schedule? Not exactly. Might be considered part of remote work policy; we could include in About? But to preserve all substantive info, we need to include it somewhere. Could add aunder About or maybe a separate section like "Remote Work Requirements". But we only allowed headings from list; we could add a
under About that includes that info. However the instruction: Use