Commercial Solutions Portfolio Lead - Application Management Services (AMS)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Job Description Must Have Technical/Functional Skills (list of duties). Then "Roles & Responsibilities" (more prose). Then "Salary Range: $120,000 - $150,000 per year". Then "TCS Employee Benefits Summary" (list). Then "Qualifications: BACHELOR OF COMPUT OF COMPUTER SCIENCE". Also maybe "Skills" could be derived from technical/functional skills list. We need to avoid repeating job title. No Job ID. Remove boilerplate like EEO etc. Not present. We need to preserve all substantive info. So we need sections: About the role (maybe from first paragraph?), Responsibilities (from Roles & Responsibilities), Qualifications (Bachelor of Computer Science), Skills (technical/functional skills list), Benefits (list from TCS Employee Benefits Summary), Pay (salary range). Schedule not present, so omit. We must not create sections with filler. So include only those with content. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to ensure we don't repeat job title as heading. Let's extract content. First part: "Job Description Must Have Technical/Functional Skills Own end-to-end AMS delivery across the Commercial Solutions portfolio, ensuring SLA/KPI adherence across L1, L2, and L3 support tiers. Manage portfolio health for the highest-complexity systems in the portfolio (Pricing Group 4–6, the top autonomy/complexity tier) — including the confirmed higher-complexity CRM and marketing platforms, Salesforce (SFDC) ACE/Talkdesk and Optimizely/Bynder — plus the unnamed PG5–PG6 applications, prioritizing these for incident, problem, and change management attention. Own delivery for CRM/contact center (Salesforce (SFDC) ACE, Talkdesk) and digital marketing/content tooling (Optimizely, Bynder), covering integration touchpoints with commerce and analytics systems. Maintain broader portfolio coverage for the remaining lower-complexity applications (contact center, SEO/search tooling, commerce, and customer analytics) at a lighter operational touch, without diverting focus from the PG4–6 tier. Drive continuous service improvement through automation, AIOps-led monitoring, and proactive problem management to reduce incident volume and recurring issues, using ServiceNow ITSM as the system of record. Lead a team of application managers and functional/technical SMEs aligned to each stage of the portfolio (CRM/contact center, marketing, commerce); manage staffing, capacity planning, and skill development, weighted toward the higher-complexity systems. Serve as the primary delivery escalation point for the sales, service, and marketing business stakeholders; run governance cadences (service reviews, steering committees, CAB). Own portfolio-level reporting: SLA/KPI dashboards, root cause trends, ticket volume analysis, and productivity/cost metrics for leadership and client review." That's a list of duties. Could be considered Skills? Actually it's responsibilities. But we also have separate "Roles & Responsibilities" section later. Might combine? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have "Job Description Must Have Technical/Functional Skills" heading in source. That suggests Skills section. The content after that is a list of duties/skills. So we can treat that as Skills. Then "Roles & Responsibilities" section: prose about role. That can be About the role or Responsibilities. Since we already have Skills, we could put that as About the role (summary) and Responsibilities maybe duplicate. But we need to avoid duplication. Perhaps we treat "Roles & Responsibilities" as About the role (or Responsibilities). Let's decide: Use About the role for the prose description (Roles & Responsibilities). Use Responsibilities for the list of duties from the first part? But the first part is also responsibilities. However the instruction says prefer few substantive sections over many thin ones. Could combine duties and responsibilities into one Responsibilities section, and Skills separate. But we have a heading "Job Description Must Have Technical/Functional Skills" which is clearly skills. So we can have Skills section (list). Then Responsibilities section (maybe from Roles & Responsibilities prose). But the prose also includes responsibilities. Could be About the role. Let's assign: - About the role: the prose from "Roles & Responsibilities" (the paragraph after that heading). - Responsibilities: maybe we could omit because it's similar to About the role? But we need to include substantive info; we could put the list of duties under Responsibilities as a

  . However the list of duties is quite detailed; we could put that under Responsibilities. Then Skills could be a separate list of technical/functional skills (maybe extracted from the same list? Actually the list includes technical skills like Salesforce, Talkdesk, Optimizely, Bynder, ServiceNow ITSM, etc. Could be considered skills. But we already used that list for responsibilities. Might be overlapping. Better: Use Skills for the technical/functional skills list (maybe bullet list of specific technologies). Use Responsibilities for the duties (own end-to-end delivery, manage portfolio health, etc.) as bullet list. Use About the role for the prose summary (Roles & Responsibilities). That seems reasonable. Let's extract Skills list: The first paragraph includes many items: end-to-end AMS delivery, SLA/KPI adherence, manage portfolio health, etc. Those are responsibilities not pure skills. But the heading says "Technical/Functional Skills". The content after that is more like responsibilities. However we can still treat it as Skills section (list of duties/skills). The instruction: Use
  • for any list of duties/requirements/benefits. So we can put that list under Skills as a list. Then Responsibilities: we could use the prose from Roles & Responsibilities as a paragraph (maybe not a list). But we could also turn that into bullet list? It's prose. We'll put as

    . Qualifications: "BACHELOR OF COMPUTER SCIENCE". That's a requirement. Could be under Qualifications as

    or

    . We'll use

    . Benefits: list from TCS Employee Benefits Summary. We'll make

    . Pay: Salary Range: $120,000 - $150,000 per year. We'll make

    under Pay heading. Schedule: not present, omit. Now ensure we don't include boilerplate like "Discretionary Annual Incentive." etc. That's benefits list; we keep. We must not repeat job title as heading. Not needed. Now produce HTML fragment:

    About the role

    ... prose from Roles & Responsibilities ...

    Responsibilities

    • Own end-to-end AMS delivery across the Commercial Solutions portfolio, ensuring SLA/KPI adherence across L1, L2, and L3 support tiers.
    • Manage portfolio health for the highest-complexity systems in the portfolio (Pricing Group 4–6, the top autonomy/complexity tier) — including the confirmed higher-complexity CRM and marketing platforms, Salesforce (SFDC) ACE/Talkdesk and Optimizely/Bynder — plus the unnamed PG5–PG6 applications, prioritizing these for incident, problem, and change management attention.
    • Own delivery for CRM/contact center (Salesforce (SFDC) ACE, Talkdesk) and digital marketing/content tooling (Optimizely, Bynder), covering integration touchpoints with commerce and analytics systems.
    • Maintain broader portfolio coverage for the remaining lower-complexity applications (contact center, SEO/search tooling, commerce, and customer analytics) at a lighter operational touch, without diverting focus from the PG4–6 tier.
    • Drive continuous service improvement through automation, AIOps-led monitoring, and proactive problem management to reduce incident volume and recurring issues, using ServiceNow ITSM as the system of record.
    • Lead a team of application managers and functional/technical SMEs aligned to each stage of the portfolio (CRM/contact center, marketing, commerce); manage staffing, capacity planning, and skill development, weighted toward the higher-complexity systems.
    • Serve as the primary delivery escalation point for the sales, service, and marketing business stakeholders; run governance cadences (service reviews, steering committees, CAB).
    • Own portfolio-level reporting: SLA/KPI dashboards, root cause trends, ticket volume analysis, and productivity/cost metrics for leadership and client review.

    Skills

    • End-to-end AMS delivery
    • SLA/KPI adherence across L1, L2, L3 support tiers
    • Portfolio health management for high‑complexity systems (Pricing Groups 4‑6)
    • Experience with Salesforce (SFDC) ACE, Talkdesk, Optimizely, Bynder
    • Integration touchpoints with commerce and analytics systems
    • ServiceNow ITSM
    • Team leadership, staffing, capacity planning, skill development
    • Stakeholder escalation and governance (service reviews, steering committees, CAB)
    • Portfolio‑level reporting and analytics
    But note that Skills list may duplicate responsibilities. However we already used responsibilities list. Might be okay but could be considered thin. Perhaps better to combine responsibilities and skills into one Responsibilities section and omit Skills. But we have a heading "Technical/Functional Skills" in source; we should reflect that. Could treat that as Skills but we need to ensure not duplicate content. Could extract specific technical skills from that list: Salesforce (SFDC) ACE, Talkdesk, Optimizely, Bynder, ServiceNow ITSM, maybe also AIOps, automation. Let's extract those. Let's create Skills list with specific technologies/tools: Salesforce (SFDC) ACE, Talkdesk, Optimizely, Bynder, ServiceNow ITSM, AIOps-led monitoring, automation, maybe also CRM/contact center, digital marketing/content tooling. We'll keep Skills concise. Now Responsibilities list we already have (the duties). Good. Now About the role: use the prose from Roles & Responsibilities. Let's copy that prose exactly: "The Commercial Solutions Portfolio Lead owns end-to-end delivery for the Sales, Service & Marketing application portfolio within the AMS engagement — spanning CRM and contact center platforms, digital marketing and content systems, commerce/customer transaction platforms, and the customer analytics tools that support them. This role is accountable for service quality, portfolio health, and continuous improvement across that landscape, while acting as the primary delivery-side point of contact for the commercial (sales, service, and marketing) business stakeholders. This portfolio skews toward higher complexity: roughly a third of its applications (Pricing Groups 4–6, the highest autonomy/complexity tier) are complex, highly customized, or integration-heavy systems rather than simple off-the-shelf SaaS tools. The role should be weighted accordingly toward candidates comfortable managing that complexity band." We'll put that in

    . Qualifications: "BACHELOR OF COMPUTER SCIENCE". We'll put

    . Benefits: list items from TCS Employee Benefits Summary: - Discretionary Annual Incentive. - Comprehensive Medical Coverage: Medical & Health, Dental & Vision, Disability Planning & Insurance, Pet Insurance Plans. - Family Support: Maternal & Parental Leaves. - Insurance Options: Auto & Home Insurance, Identity Theft Protection. - Convenience & Professional Growth: Commuter Benefits & Certification & Training Reimbursement. - Time Off: Vacation, Time Off,