Business Execution Consultant 3

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - The posting starts with a promotional paragraph about the company and opportunity. - Then "Contract Duration: 12 Months" - this could be part of a "Schedule" or "Contract Details" section, but the rules say only include Pay/Schedule/Benefits if actually stated. It mentions "competitive benefit package" but no details. I'll include a "Contract Details" section maybe, but the rules say use specific headings like "Schedule". However, "Contract Duration" is not exactly schedule. Might fold into a short paragraph. - "Required Skills & Experience" - this is a Requirements/Qualifications section. - "What You Will Be Doing" - this is Responsibilities. The rules: use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Fold minor metadata into short

or drop. The posting has "Posted By: Blair Richardson" - that's metadata, drop or fold into a short p? Probably drop. The promotional paragraph at the beginning: "Outstanding long-term contract opportunity! ..." This could be "About the role" or "About the company". The rules say include a section ONLY when the posting has real, specific content for it. The promotional paragraph is somewhat generic but does describe the company and contract nature. I could create an "About the role" section with that prose. But the rules: "Prefer a few substantive sections over many thin ones." So I'll create sections for: - About the role (with the introductory paragraph) - Contract Details (maybe include duration and benefit mention) - Requirements (or Qualifications) - the "Required Skills & Experience" section - Responsibilities - "What You Will Be Doing" The "Required Skills & Experience" includes a list of skills and experience. I'll use

• for the list items. The text has bullet-like items but not formatted as list. I'll parse them. Let me extract the requirements: - 4+ years of Business Execution, Implementation, or Strategic Planning experience, or equivalent demonstrated through one or a combination of the following: work or consulting experience, training, military experience, education. - Advanced proficiency in: SQL (complex queries, stored procedures, performance optimization), Java (enterprise applications, batch processing frameworks such as Spring Boot / Spring Batch preferred) - Strong understanding of: Data architecture and infrastructure design, ETL and data pipeline development, Distributed / scalable processing frameworks - Regulatory & Domain Experience (Direct Banking Experience is a “Nice to Have” – not completely essential, but if not, the technical expertise needs to be “off the charts”): Experience working in: Market Risk or Counterparty Risk environments, Regulatory reporting (e.g., FR Y 14Q, CCAR, Basel) preferred - Familiarity with: Stress testing processes, Risk aggregation and reporting controls - Delivery & Collaboration: Proven experience: Writing detailed requirements in Jira (user stories, acceptance criteria), Operating within Agile / hybrid delivery environments - Strong ability to: Translate SME discussions into concrete technical solutions, Partner across risk, data, and technology teams I'll structure these as a list, maybe grouped. Responsibilities: - Consult on or participate in moderately complex initiatives and deliverables within Business Execution and contribute to large-scale planning related to Business Execution deliverables. - Review and analyze moderately complex Business Execution challenges that require an in-depth evaluation of variable factors. - Contribute to the resolution of moderately complex issues and consult with others to meet Business Execution deliverables while leveraging solid understanding of the function, policies, procedures, and compliance requirements. - Collaborate with client personnel in Business Execution. Now, the introductory paragraph: "Outstanding long-term contract opportunity! A well-known Financial Services Company is looking for a Business Execution Consultant in Charlotte, NC (Hybrid). Work with the brightest minds at one of the largest financial institutions in the world. This is a long-term contract opportunity that includes a competitive benefit package! Our client has been around for over 150 years and is continuously innovating in today's digital age. If you want to work for a company that is not only a household name, but also truly cares about satisfying customers' financial needs and helping people succeed financially, apply today." I'll put this in an "About the role" section as a paragraph. Contract Duration: 12 Months. Also mentions "competitive benefit package". Could create a "Contract Details" section with a paragraph. But the rules say use headings like "Schedule" or "Benefits". Since it's a contract duration, maybe "Schedule" is appropriate? But schedule usually refers to work hours. Could be "Contract Details". However, the allowed headings are listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Contract Details" is not in the list. But the rules say "e.g." meaning examples. I think it's okay to use a relevant heading. But to be safe, I'll include a "Schedule" section with the contract duration and hybrid location. Or maybe "About the role" includes location and contract type. The intro already says "Charlotte, NC (Hybrid)" and "long-term contract". So I can fold that into About the role. The rules: "fold minor metadata into a short

  or drop it." The contract duration and location are minor metadata? They are important. I'll include in About the role. Also, "Posted By: Blair Richardson" - drop. Now, I need to output ONLY the HTML fragment, no html/body, no markdown. Let me craft the HTML. Structure:

  About the role

  Outstanding long-term contract opportunity! A well-known Financial Services Company is looking for a Business Execution Consultant in Charlotte, NC (Hybrid). Work with the brightest minds at one of the largest financial institutions in the world. This is a long-term contract opportunity that includes a competitive benefit package! Our client has been around for over 150 years and is continuously innovating in today's digital age. If you want to work for a company that is not only a household name, but also truly cares about satisfying customers' financial needs and helping people succeed financially, apply today.

  Contract Details

  Contract Duration: 12 Months

  But the rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "competitive benefit package" but no details. It states contract duration. I think it's okay to have a "Contract Details" section. However, the allowed headings list includes "Schedule". Could use "Schedule" for contract duration? Might be a stretch. I'll use "Contract Details" as a heading, but the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so other headings are allowed if they make sense. But to be safe, I'll use "Schedule" for contract duration? Actually, schedule could be work schedule. The posting says "Hybrid" which is work arrangement. I'll include a "Schedule" section with contract duration and hybrid. But the posting doesn't specify work hours. I'll create a "Schedule" section with a paragraph: "12-month contract, hybrid (Charlotte, NC)." Alternatively, fold into About the role. I'll decide to include a "Schedule" section because the rules mention Schedule as an example heading, and the posting has contract duration and hybrid info. Now, Requirements section: heading "Requirements" or "Qualifications". The posting says "Required Skills & Experience". I'll use "Requirements". Responsibilities: "What You Will Be Doing" -> "Responsibilities". Now, I need to use

  • for lists. For requirements, I'll create a list with each bullet as a li. But the requirements have sub-bullets. I can nest lists or just make each top-level item a li with sub-items as nested ul. However, the rules say "use
    • for any list of duties/requirements/benefits". It doesn't forbid nesting. I'll do nested lists for clarity. But the output should be clean. I'll make each major requirement a li, and sub-points as nested ul. Let's write. First, About the role:

      About the role

      Outstanding long-term contract opportunity! A well-known Financial Services Company is looking for a Business Execution Consultant in Charlotte, NC (Hybrid). Work with the brightest minds at one of the largest financial institutions in the world. This is a long-term contract opportunity that includes a competitive benefit package! Our client has been around for over 150 years and is continuously innovating in today's digital age. If you want to work for a company that is not only a household name, but also truly cares about satisfying customers' financial needs and helping people succeed financially, apply today.

      Schedule:

      Schedule

      12-month contract, hybrid (Charlotte, NC).

      Requirements:

      Requirements

      • 4+ years of Business Execution, Implementation, or Strategic Planning experience, or equivalent demonstrated through work or consulting experience, training, military experience, or education.
      • Advanced proficiency in:
        • SQL (complex queries, stored procedures, performance optimization)
        • Java (enterprise applications, batch processing frameworks such as Spring Boot / Spring Batch preferred)
      • Strong understanding of:
        • Data architecture and infrastructure design
        • ETL and data pipeline development
        • Distributed / scalable processing frameworks
      • Regulatory & Domain Experience (Direct Banking Experience is a “Nice to Have” – not completely essential, but if not, the technical expertise needs to be “off the charts”):
        • Experience working in Market Risk or Counterparty Risk environments
        • Regulatory reporting (e.g., FR Y 14Q, CCAR, Basel) preferred
      • Familiarity with:
        • Stress testing processes
        • Risk aggregation and reporting controls
      • Delivery & Collaboration:
        • Proven experience writing detailed requirements in Jira (user stories, acceptance criteria)
        • Operating within Agile / hybrid delivery environments
      • Strong ability to:
        • Translate SME discussions into concrete technical solutions
        • Partner across risk, data, and technology teams
      Responsibilities:

      Responsibilities

      • Consult on or participate in moderately complex initiatives and deliverables within Business Execution and contribute to large-scale planning related to Business Execution deliverables.
      • Review and analyze moderately complex Business Execution challenges that require an in-depth evaluation of variable factors.
      • Contribute to the resolution of moderately complex issues and consult with others to meet Business Execution deliverables while leveraging solid understanding of the function, policies, procedures, and compliance requirements.
      • Collaborate with client personnel in Business Execution.
      That seems comprehensive. Now, check rules: "Do NOT repeat the job title as a heading (the page already shows it)" - I didn't. "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short