Director, Delivery Management

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We must not repeat job title. No Job ID heading. We need to preserve substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove Fair Chance Ordinance details? That's legal boilerplate; likely should be removed. Also remove "Applications will be accepted on a rolling basis." etc. Also remove EPAM description? Might be considered boilerplate but maybe it's substantive about company culture; but it's generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EPAM description about culture maybe not boilerplate but could be considered generic; but it's not duplicated. Might keep as part of About the role? The posting includes a paragraph about EPAM being leading global provider etc. That's substantive about company. Could be placed under About the role. We need to extract responsibilities, requirements, qualifications, skills, benefits, pay. Let's parse the posting. First sentence: "Drive and lead EPAM NA MS Business Applications business development and client engagement management, work on new EPAM offerings in the MS Dynamics and Power Platform space, and work on refining existing offerings." That's about the role. Then "Req.#1023321898" - job ID, drop. Then "Responsibilities" heading. List under Responsibilities: - Grow the MS Dynamics and Power Platform business portfolio - Discover, envision, and land MS Dynamics opportunities alongside EPAM teams & clients - Lead cross-functional EPAM and/or EPAM clients` teams through the journey of business challenges and solutions leveraging MS Dynamics and Power Platform stack - Work with clients to deliver MS Business Applications Products, which provide value to end-users - Bring your creative engineering mind to deliver end-to-end MS Business Applications solutions That's responsibilities. Then "Requirements" heading. Under Requirements, there are subcategories: Delivery Management, Consulting, MS Dynamics and Power Platform, Leadership, Nice to have. We need to capture all substantive content. Delivery Management bullet points: - Experience oversight of the entire project's execution, from initiation to delivery, ensuring it is completed on time, within scope, and on budget. - Knowledge of how to drive daily team operations in close cooperation with Leads, Solutions Architect, the clients's Product Owner, and Scrum Master. - Proven track record of experience in client communication and reports, as well as overall project governance Consulting: - Experience in exploration of the business problem and convergence to applied MS Business Applications technical solutions; expertise in pre-sales, solution definition activities, resource plan preparation, and estimations MS Dynamics and Power Platform: - 5+ years of hands-on experience with MS Dynamics and Power Platform, as well as experience in delivery of MS Business Applications solutions from concept to production, familiarity and expertise with Microsoft Cloud, and technical leadership Leadership: - Track record of delivery of complex MS Business Applications-empowering programs to clients in a leadership position - Experience in management and growth of the team to scale up MS Dynamics and Power Platform capabilities is a big plus - Excellent communication skills (active listening, writing and presentation), drive for problem-solving and creative solutions Nice to have: - One or more business domains of expertise (e.g. CPG, Retail, Financial Services, Insurance, Healthcare/ Life Science) - Knowledge of one or more products from the MS Business Applications family, including: Dynamics 365 Customer Insights Dynamics 365 Field Service Dynamics 365 Finance and Operations Dynamics 365 Supply Chain Dynamics 365 Commerce Microsoft Copilot Studio - Technologies Microsoft Dynamics 365 (CRM and ERP), Customer Insights - Journeys and Data, Power Platform with focus on Power Apps We need to decide what sections to output: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have responsibilities covered. Requirements could be the main requirements (Delivery Management, Consulting, MS Dynamics and Power Platform, Leadership). Qualifications maybe the nice-to-have? Or we could treat qualifications as separate but we have nice-to-have. Skills could be the specific technologies listed. Benefits we have a list. Pay we have salary range. Schedule not mentioned, so omit. We must not create sections with filler like "not specified". So only include sections with real content. Thus sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Skills (maybe the specific tech list), Benefits, Pay. We need to ensure we don't duplicate content. For Skills, we could list the specific technologies: Microsoft Dynamics 365 (CRM and ERP), Customer Insights - Journeys and Data, Power Platform with focus on Power Apps, plus the list of Dynamics 365 products etc. But those are also in nice-to-have. Might be better to put those under Skills. Qualifications could be the nice-to-have business domain expertise. Let's decide. We have nice-to-have: business domains expertise, knowledge of specific products, technologies. We could put business domain expertise under Qualifications, and the specific product/technology knowledge under Skills. Thus: About the role: paragraph(s) from first sentence plus EPAM description maybe. Responsibilities: ul list. Requirements: ul list with subheadings? The instruction: Use

for section headings. For subheadings inside a section, we could still use

? Probably not; they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only top-level sections get h3. Inside we can use

or

• . For requirements we can have multiple paragraphs or nested lists? We can just have a
  with each bullet as
  • . If we want to group by category, we could include a

    preceding each group. That's fine. Qualifications: maybe business domain expertise. Skills: list of specific technologies. Benefits: list. Pay: salary range. Let's extract benefits list: - Medical, Dental and Vision Insurance (Subsidized) - Health Savings Account - Flexible Spending Accounts (Healthcare, Dependent Care, Commuter) - Short-Term and Long-Term Disability (Company Provided) - Life and AD&D Insurance (Company Provided) - Employee Assistance Program - Unlimited access to LinkedIn learning solutions - Matched 401(k) Retirement Savings Plan - Paid Time Off - Legal Plan and Identity Theft Protection - Accident Insurance - Employee Discounts - Pet Insurance - Employee Stock Purchase Program We should keep them as

  • . Pay: Salary range: $200,000 - $220,000. Now About the role: combine first sentence and EPAM description. First sentence: "Drive and lead EPAM NA MS Business Applications business development and client engagement management, work on new EPAM offerings in the MS Dynamics and Power Platform space, and work on refining existing offerings." EPAM description: "EPAM is a leading global provider of digital platform engineering and development services. We are committed to having a positive impact on our clients, our employees, and our communities. We embrace a dynamic and inclusive culture. Here you will collaborate with multi-national teams, contribute to a myriad of innovative projects that deliver the most creative and cutting-edge solutions, and have an opportunity to continuously learn and grow. No matter where you are located, you will join a dedicated, creative, and diverse community that will help you discover your fullest potential. Engineer the Future with a Career at EPAM" We can combine into a paragraph or two. Now we must remove boilerplate: The Fair Chance Ordinance details, the "Applications will be accepted on a rolling basis." etc. Also remove the "In accordance with the LA County Fair Chance Ordinance..." etc. Also remove the "EPAM will not provide new H-1B visa sponsorship..." etc. Also remove the "This posting includes a good faith range..." maybe that's part of Pay? Actually that paragraph describes salary range; we already have salary range. The paragraph about salary range is substantive; we can keep the range but not the explanatory text? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the salary range statement and maybe the explanation? The explanation is about how compensation determined; that's substantive. But we already have Pay section; we could include that explanation as a

    under Pay. However the instruction says: 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. The posting does state salary range and explanation. So we can include Pay section with both the range and the explanation. Thus Pay section:

    Salary range: $200,000 - $220,000. The range provided reflects base salary only. Individual compensation offers within the range are based on a variety of factors, including, but not limited to: geographic location, experience, credentials, education, training; the demand for the role; and overall business and labor market considerations. Most candidates are hired at a salary within the range disclosed.

    Now Benefits section: we have list. Now we need to ensure we didn't include duplicated lines. The posting had duplicate lines? Not obvious. Now produce HTML fragment. Structure:

    About the role

    Drive and lead EPAM NA MS Business Applications business development and client engagement management, work on new EPAM offerings in the MS Dynamics and Power Platform space, and work on refining existing offerings. EPAM is a leading global provider of digital platform engineering and development services. We are committed to having a positive impact on our clients, our employees, and our communities. We embrace a dynamic and inclusive culture. Here you will collaborate with multi-national teams, contribute to a myriad of innovative projects that deliver the most creative and cutting-edge solutions, and have an opportunity to continuously learn and grow. No matter where you are located, you will join a dedicated, creative, and diverse community that will help you discover your fullest potential. Engineer the Future with a Career at EPAM

    Responsibilities

    • Grow the MS Dynamics and Power Platform business portfolio
    • Discover, envision, and land MS Dynamics opportunities alongside EPAM teams & clients
    • Lead cross-functional EPAM and/or EPAM clients` teams through the journey of business challenges and solutions leveraging MS Dynamics and Power Platform stack
    • Work with clients to deliver MS Business Applications Products, which provide value to end-users
    • Bring your creative engineering mind to deliver end-to-end MS Business Applications solutions

    Requirements

    Delivery Management:

    • Experience oversight of the entire project's execution, from initiation to delivery, ensuring it is completed on time, within scope, and on budget.
    • Knowledge of how to drive daily team operations in close cooperation with Leads, Solutions Architect, the clients's Product Owner, and Scrum Master.
    • Proven track record of experience in client communication and reports, as well as overall project governance

    Consulting:

    • Experience in exploration of the business problem and convergence to applied MS Business Applications technical solutions; expertise in pre-sales, solution definition activities, resource plan preparation, and estimations

    MS Dynamics and Power Platform:

    • 5+ years of hands-on experience with MS Dynamics and Power Platform, as well as experience in delivery of MS Business Applications solutions from concept to production, familiarity and expertise with Microsoft Cloud,