Salesforce Program Manager

We need to produce HTML fragment with sections: About the role? Actually we have sections: Job Summary, Who We Are, Responsibilities, Required Qualifications, Desired Qualifications, Preferred Salesforce Certifications, Benefits, maybe Salary, Work Location, Modes of Work? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Job Summary (description) - Who We Are (description) - Responsibilities (list) - Required Qualifications (list) - Desired Qualifications (list) - Preferred Salesforce Certifications (list) - Benefits (list) - Salary (specific numbers) - Work Location (Ann Arbor Campus) - Modes of Work (Hybrid Mobile/Remote Full/Part Time Full-Time Regular/Temporary Regular) - Application Deadline (posting dates) - FLSA Status Exempt - Organizational Group etc. We need to decide which sections to include: The instructions list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map. - About the role: could be Job Summary + Who We Are? Might be separate sections: "Job Summary" and "About the University" but they said prefer few substantive sections over many thin ones. Could combine Job Summary and Who We Are into an "About the role" section? But they said do NOT repeat the job title as a heading. "About the role" is okay. We could have sections: About the role (Job Summary + Who We Are), Responsibilities, Qualifications (maybe combine Required and Desired?), Benefits, Pay (Salary), Work Location? Not in list but could be included as part of About the role? Might be better to include a "Work Location" section if specific. However instructions only gave examples but not strict; we can add other headings if they have real content. But they said prefer a few substantive sections over many thin ones. So we should limit number of sections. Potential sections: - About the role (Job Summary + Who We Are) - Responsibilities - Qualifications (maybe combine Required and Desired? Could separate Required Qualifications and Desired Qualifications as subheadings? But they'd be thin? Might be okay to have two sub-sections under Qualifications using

  ? But only

  allowed for section headings. Could use

  for Required Qualifications and another

  for Desired Qualifications. That's two sections. - Benefits - Pay (Salary) - Work Location and Modes of Work maybe combined into "Work Details"? Could be a section "Work Location & Schedule". But schedule not given; we have modes of work (Hybrid Mobile/Remote Full/Part Time Full-Time Regular/Temporary Regular). That's somewhat schedule info. Could include as "Work Arrangement". But we need to avoid filler. All these have real content. We must not include application instructions, EEO, etc. We need to preserve all substantive information: So we must include details like salary range, benefits list, responsibilities list, qualifications lists, certifications list, work location, modes of work, posting dates maybe? The posting dates are metadata but could be considered minor; but they said fold minor metadata into a short

  or drop it. Posting dates maybe minor but could be included in a short paragraph. We need to decide what to keep: The posting begin/end date maybe not essential but could be kept as minor metadata. We need to output only HTML fragment. Let's craft:

  About the role

  Information and Technology Services (ITS) is looking for a Salesforce Program Manager to join the Enterprise Application Services team within ITS. The Salesforce Program Manager will help shape the University's enterprise Salesforce strategy and lead the delivery and ongoing operation of its Salesforce services. The role supports the Salesforce Center of Excellence (SFCOE) in planning for future needs, managing day-to-day priorities, and delivering major initiatives, including Education Cloud for student recruitment and advising. The Program Manager will supervise Salesforce developers and business systems analysts (BSAs), guide solution architecture, and work with university stakeholders to turn business needs into secure, sustainable solutions.

  Information and Technology Services (ITS) supports U-M faculty, researchers, staff, and students in their use of technology to teach, learn, research, and work, and be leaders in their fields. We are dedicated to creating cohesive digital experiences and promoting university wide innovations. ITS's mission is to be trusted enablers of technology for the U-M community. ITS works together to provide cohesive digital experiences and seamless support to the U-M community. For more information about ITS, visit: https://its.umich.edu/about

  That's about the role. Then Responsibilities:

  Responsibilities

  • Partner with SFCOE leadership on Salesforce strategy, service planning, roadmaps, investment priorities, and governance.
  • Lead the planning and delivery of enterprise Salesforce initiatives, particularly Education Cloud implementations for recruitment, advising, and student success.
  • Manage operational needs, including service requests, production issues, enhancements, release planning, and support priorities.
  • Supervise, coach, and set priorities for Salesforce developers and BSAs, balancing project delivery with ongoing service commitments.
  • Guide architecture and solution design across applications, data, integrations, security, automation, and user experience.
  • Partner with stakeholders to define requirements, scope, timelines, dependencies, and measures of success.
  • Coordinate testing, data migration, change management, deployment, and transition to operational support.
  • Manage vendor and implementation partner deliverables, identify risks, and provide clear recommendations to sponsors and governance groups.
  Qualifications: maybe separate Required and Desired.

  Required Qualifications

  • Bachelor's degree in information technology, computer science, business administration, or a related field, or an equivalent combination of education and relevant experience.
  • Experience managing complex Salesforce programs and ongoing platform operations.
  • Experience designing or leading Salesforce solution architecture, including data, integration, and security decisions.
  • Experience implementing or supporting Salesforce Education Cloud, preferably in recruitment, advising, student success, or other higher education processes.
  • Experience supervising Salesforce developers and BSAs, including work prioritization, coaching, and delivery oversight.
  • Strong knowledge of Salesforce configuration, development practices, release management, and platform governance.
  • Ability to connect strategic goals with practical delivery plans and operational priorities.
  • Strong communication and stakeholder management skills.

  Desired Qualifications

  • Experience with Experience Cloud, Marketing Cloud, Data Cloud, Education Cloud, or other Salesforce technologies.
  • Experience with enterprise integrations, student data, privacy requirements, and identity and access management in higher education.
  • Experience developing platform roadmaps, service models, and standards for a Salesforce Center of Excellence.

  Preferred Salesforce Certifications

  • Salesforce Certified Platform Administrator and Salesforce Certified Education Cloud Consultant.
  • Salesforce Certified Application Architect or Salesforce Certified System Architect, reflecting the role's architecture design responsibilities.
  • Salesforce Certified Business Analyst, Platform Data Architect, or Platform Integration Architect.
  • Certifications relevant to the services managed, such as Experience Cloud Consultant or Marketing Cloud Engagement Administrator.

  Benefits

  • Generous time off
  • A retirement plan that provides two-for-one matching contributions with immediate vesting
  • Many choices for comprehensive health insurance
  • Life insurance
  • Long-term disability coverage
  • Flexible spending accounts for healthcare and dependent care expenses
  • Dental and Vision Insurance
  • Parental and Maternity Leave

  Pay

  Salary $125,000.00 - $135,000.00

  Work Location & Arrangement

  Work Location: Ann Arbor Campus, Ann Arbor, MI

  Modes of Work: Hybrid Mobile/Remote Full/Part Time Full-Time Regular/Temporary Regular

  We could also include posting dates as minor metadata: maybe a short paragraph. But we need to avoid duplication and boilerplate. The "Application Deadline" etc is boilerplate? It's specific but maybe minor. Could include as a short paragraph. But we need to preserve all substantive information. The posting dates are substantive? They indicate when the job is posted. Might be considered metadata but could be kept. We could add a

  Posting period: 9/25/2026 - 10/02/2026

  under Work Location & Arrangement or separate. But we need to avoid too many sections. Could add a short paragraph after Work Location & Arrangement. Let's include:

  Work Location & Arrangement

  Work Location: Ann Arbor Campus, Ann Arbor, MI

  Modes of Work: Hybrid Mobile/Remote Full/Part Time Full-Time Regular/Temporary Regular

  Posting period: 9/25/2026 - 10/02/2026

  That's fine. Check for any duplicated lines: We have not included the "Apply Now" etc. We have not included EEO statement. We have not included FLSA Status Exempt, Organizational Group etc. Those are minor metadata; could be omitted or folded into a short paragraph. The instructions: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a short paragraph for those minor metadata like FLSA Status, Organizational Group, Job Opening ID, etc. But we need to preserve ALL substantive information. Are those substantive? They might be considered metadata but still information. The instruction says fold minor metadata into a short

  or drop it. So we can include them in a short paragraph. Let's add a paragraph after Work Location & Arrangement maybe: "Job Opening ID: 283568; Working Title: Salesforce Program Manager; Job Title: IT Program Manager; FLSA Status: Exempt; Organizational Group: ITS AIS Department ITS EAS CRM & Mktg Comms Sys". That's a lot but could be a short sentence. But we need to avoid too many sections; we can just add a

  with that info. Let's decide to include a paragraph "Additional details: Job Opening ID 283568; Working Title Salesforce Program Manager; Job Title IT Program Manager; FLSA Status Exempt; Organizational Group ITS AIS Department ITS EAS CRM