Business Consulting Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. 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 boilerplate etc. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: First paragraph: "You are strategic, resilient, engaging with people, and a natural self-starter with a passion for solving complex business challenges. If this sounds like you, this could be the perfect opportunity to join EPAM as a Business Consulting Manager within our Energy business unit. In this role you will lead high-impact strategic advisory and consulting engagements for energy clients, helping them transform their business operations, modernize core capabilities, and successfully leverage EPAM’s world-class software engineering and product development teams. The Business Consulting Manager will be involved in developing and implementing diverse strategies and working with our delivery teams to develop fit-for-purpose technology solutions to drive bottom line results. You will support client engagements and shepherd projects from pre-sales initiatives through client solution development, while keeping a pulse on stakeholder engagement and solution adoption. At EPAM, you can make a difference. We are entrepreneurial and collaborative in our culture, making EPAM a recognized great place to work. We enable our people to take ownership and responsibility in setting the direction for all our engagements and across practices." That's about the role. Could be "About the role" or "Overview". Use

  About the role

  then

  with that content. Then "Req.#1094390414" is metadata; we should fold minor metadata into a short

  or drop it. Probably we can include a

  with the requisition number? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a

  with "Req.#1094390414". Probably after the overview. Then "Responsibilities" heading with list items. Responsibilities list: - Help identify and pursue EPAM project and business development opportunities - Support the definition, development, and scoping of business-related proposals, Statements of Work (SOWs), and projects - Lead core management consulting activities, such as current state assessments, process documentation improvement, requirements gathering, and business case development efforts - Facilitate organization and role-mapping activities to support strategic, process, and structural transitions - Manage own activities and work with team members to deliver desired business outcomes and ensure quality completion of deliverables - Establish positive relationships with clients and peers that build rapport, liaising and pulling through other relevant service offerings, amplifying EPAM's impact - Empower team members, mentors, and support career development efforts - Keeps current on trends within emerging technology (particularly regarding AI capabilities), best practices, and policies - Demonstrate executive presence and cross-team facilitation skills - Contribute to practice growth and development for EPAM through involvement with professional organizations, conference attendance, white papers, and any marketing activities aligning with EPAM’s goals That's a list. Then "Requirements" heading with list items: - More than five (5) years of relevant experience in an established consulting firm environment. - A blend of consulting and industry is also acceptable - Understands and speaks confidently; keeps current on trends within emerging technology, best practices, and policies; uses broad base of experience to advise clients on project and implementation approaches - Knowledge of Agile and Design Thinking methodologies - Bachelor's degree. MBA or Master’s degree preferred Note: "Understands and speaks confidently; keeps current on trends within emerging technology, best practices, and policies; uses broad base of experience to advise clients on project and implementation approaches" is a sentence. Then "Benefits" heading with list items (the benefits list). The posting includes: - 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 need to include Benefits section only if posting actually states them. Yes. Pay and Schedule: Not mentioned. So we should NOT include Pay or Schedule sections. Skills: Not explicitly a separate section; maybe we could combine with Requirements? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. If we don't have specific content for Skills, we shouldn't create it. We have Requirements; maybe also Qualifications? The posting includes "Requirements" and also "Bachelor's degree...". Could treat that as Qualifications. But we already have Requirements covering experience, education, etc. Could split into Requirements and Qualifications but not necessary. The instruction: prefer few substantive sections over many thin ones. So we can keep Requirements as one section covering experience, education, etc. No need for separate Qualifications. Skills: Not explicit; maybe we could infer from responsibilities but better not to create unless explicit. So we skip Skills. Thus sections: About the role, Responsibilities, Requirements, Benefits. We also need to include the requisition number maybe as a short

  after About the role before Responsibilities. We must not include boilerplate like "EPAM is a leading global provider..." etc. That's after the benefits? Actually after benefits there is a paragraph about EPAM being leading global provider etc. That's boilerplate? It's describing EPAM; might be considered generic but it's substantive? It's about the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EPAM description might be considered boilerplate but it's not legal/EEO. It's a generic description; could be considered filler but it's not explicitly prohibited. However we should preserve ALL substantive information; does that description count as substantive? It's about EPAM's mission etc. Might be considered generic but still part of posting. The instruction says "Prefer a few substantive sections over many thin ones." Could include it in About the role? Already we have overview; we could add a paragraph about EPAM's culture etc. But we already captured some of that in the overview. The later paragraph: "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 Applications will be accepted on a rolling basis. EPAM will not provide new H-1B visa sponsorship for this position. Candidates with existing transferable H-1B status may be considered." That includes info about H-1B sponsorship (important). That's substantive. Also "Applications will be accepted on a rolling basis." That's application instruction? Might be considered application instruction; we should remove application instructions. The instruction says remove application instructions. So we should drop "Applications will be accepted on a rolling basis." and the H-1B sponsorship note? That's not exactly application instruction but it's about visa sponsorship; could be considered relevant. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Visa sponsorship is not those; it's a condition. Might be kept. However it's near the end; we could include a short paragraph about visa sponsorship. But we must not include boilerplate like "Engineer the Future with a Career at EPAM". That's a tagline; maybe considered boilerplate but not prohibited. However we should avoid fluff. The instruction: Prefer few substantive sections over many thin ones. So we could incorporate the EPAM description into About the role section as additional prose. Thus About the role section could contain two paragraphs: first the initial description, second the EPAM description (excluding application instructions). We'll need to remove "Applications will be accepted on a rolling basis." and maybe the tagline "Engineer the Future with a Career at EPAM". The tagline is not substantive; could be dropped. Thus About the role: combine: Paragraph1: "You are strategic, resilient, engaging with people, and a natural self-starter with a passion for solving complex business challenges. If this sounds like you, this could be the perfect opportunity to join EPAM as a Business Consulting Manager within our Energy business unit. In this role you will lead high-impact strategic advisory and consulting engagements for energy clients, helping them transform their business operations, modernize core capabilities, and successfully leverage EPAM’s world-class software engineering and product development teams. The Business Consulting Manager will be involved in developing and implementing diverse strategies and working with our delivery teams to develop fit-for-purpose technology solutions to drive bottom line results. You will support client engagements and shepherd projects from pre-sales initiatives through client solution development, while keeping a pulse on stakeholder engagement and solution adoption. At EPAM, you can make a difference. We are entrepreneurial and collaborative in our culture, making EPAM a recognized great place to work. We enable our people to take ownership and responsibility in setting the direction for all our engagements and across practices." Paragraph2: "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. EPAM will not provide new H-1B visa sponsorship for this position. Candidates with existing transferable H-1B status may be considered." We should not include "Applications will be accepted on a rolling basis." as it's application instruction. Now Responsibilities section as

  • ... etc. Requirements section as
    • ... etc. Benefits section as
      • ... etc. We need to ensure we don't repeat job title as heading. Already we didn't. We need to output only HTML fragment, no /, no markdown. Thus final output:

        About the role

        You are strategic, resilient, engaging with people, and a natural self-starter with a passion for solving complex business challenges. If this sounds like you, this could be the perfect opportunity to join EPAM as a Business Consulting Manager within our Energy business unit. In this role you will lead high-impact strategic advisory and consulting engagements for energy clients, helping them transform their business operations, modernize core capabilities, and successfully leverage EPAM’s world-class software engineering and product development teams. The Business Consulting Manager will be involved in developing and implementing diverse strategies and working with our delivery teams to develop fit-for-purpose technology solutions to drive bottom line results. You will support client engagements and shepherd projects from pre-sales initiatives through client solution development, while keeping a pulse on stakeholder engagement and solution adoption. At EPAM, you