Project Executive, Healthcare

We need to output HTML fragment with sections only if content exists. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content. From posting: Overview (not a heading we need? It says use

for section headings e.g. About the role, Responsibilities, etc. Overview could be considered "About the role". So we can put Overview content under

About the role

. Responsibilities: definitely present. Requirements: Not explicitly a heading but there is "Qualifications". There's also "Working Conditions". Could be considered Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if present. We have Qualifications section: yes. We have Skills? Not explicit but maybe implied in Qualifications. Could we create Skills heading? Probably not unless there is explicit skills list. Better not to create empty sections. Benefits: there is a Benefits paragraph near the end: "Benefits include, competitive salaries, auto allowances..." So we should include Benefits section. Pay: There's "Compensation Information" with base salary etc. It says "Base Salary for this position is just one component...". Also mentions salary ranges reviewed regularly. So we have pay info. Should we include Pay section? Yes, we have compensation info. Schedule: Not mentioned. No schedule info. So we should not include Schedule. Requirements: Could be covered by Qualifications? But we have both Requirements and Qualifications headings possible. The posting includes "Qualifications" with bullet-like paragraphs. There's also "Working Conditions". Could treat Working Conditions as Requirements? But better to follow instruction: include a section ONLY when posting has real, specific content for it. So we need to decide if there is content for Requirements separate from Qualifications. The posting has "Qualifications" section with bullet points. There's no separate "Requirements" heading. However, there is "Working Conditions" which could be considered part of Requirements? But it's not exactly. The instruction says we can use headings like Requirements, Qualifications, Skills, etc. If we don't have explicit Requirements, we could omit that heading. But we have Qualifications, so we will include Qualifications. We also have "About Suffolk" which is company description; could be considered "About the role"? Already used Overview for About the role. The About Suffolk could be separate but not in list of allowed headings. Could we put it under About the role? Probably better to keep Overview as About the role and maybe add a separate section like "About Suffolk" but not allowed headings. Since only allowed headings are those listed, we should not add other headings. So we can incorporate About Suffolk content into About the role or maybe omit. But we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. We could put it under About the role as additional paragraphs. Thus About the role will contain Overview paragraph plus About Suffolk description. Responsibilities: copy the responsibilities block. Qualifications: copy the qualifications block (including Working Conditions? Actually Working Conditions is separate but could be part of Qualifications? It's more about physical demands. Could be considered Requirements? But we don't have Requirements heading. Perhaps we should create a Requirements section for Working Conditions? The instruction says we can use Requirements heading for any list of duties/requirements/benefits. Working Conditions is a requirement (physical). So we could put Working Conditions under Requirements heading. However we also have Qualifications heading for education/experience etc. So we can have both Requirements and Qualifications sections. Thus: - About the role: Overview + About Suffolk description. - Responsibilities: responsibilities block. - Requirements: Working Conditions paragraph (maybe also any other requirements like "Self-perform experience a plus" etc? Those are in Qualifications though). We'll put Working Conditions under Requirements. - Qualifications: bullet list of qualifications (Bachelor's degree, 10-15 years experience, etc.) - Benefits: benefits paragraph. - Pay: compensation information paragraph. We must not include sections with filler like "commensurate with experience". Not present. We must not include Job ID etc. We must not include boilerplate like EEO, navigation, legal, scam-warning, duplicated lines, application instructions. So we need to strip EEO Statement, etc. Also remove "Compensation Information Where required by law..."? That's part of Pay, we keep. But we need to remove EEO statement entirely. Also remove "About Suffolk" maybe we keep as part of About the role. Also remove "At Suffolk, we believe that our total rewards program..." that's part of Benefits? Actually that is also benefits description; we can keep. We must preserve all substantive information. So we need to include the benefits paragraph that includes "competitive salaries, auto allowances and gas cards for certain roles, access to market leading medical..." etc. We also need to include the "Compensation Information" paragraph. Now format: Use

for each section heading. Then content: use

for prose,

• for any list of duties/requirements/benefits. We need to decide what constitutes a list. The responsibilities block is a paragraph with many sentences; could be turned into list items? The instruction: Use
  • for any list of duties/requirements/benefits. The responsibilities are a list of duties; we could split into
  • items. However the text is not explicitly bullet list; but we can treat each sentence as a duty? Might be overkill. Safer to keep as

    because it's not explicitly a list. But the instruction says use

    • for any list of duties/requirements/benefits. If we keep as

      , we might violate. However the responsibilities are not presented as a list in source; they are prose. The instruction likely expects that if there is a list (like bullet points) we use

      • . Since responsibilities are prose, we can use

        . Similarly for qualifications: they are prose sentences; we can use

        . For benefits: it's a list of benefits separated by commas; could be

        • . But it's also prose. I'd keep as

          for simplicity, but risk not following instruction. Let's examine: The responsibilities block includes many duties separated by line breaks? In the source, it's a paragraph with sentences. Not a list. So using

          is fine. Thus we will output:

          About the role

          Overview text...

          About Suffolk text...

          Responsibilities

          Responsibilities text...

          Requirements

          Working Conditions text...

          Qualifications

          Qualifications text...

          Benefits

          Benefits text...

          Pay

          Compensation Information text...

          We must ensure we removed boilerplate: EEO Statement, navigation, legal, scam-warning, duplicated lines, application instructions. Also remove "While performing the duties of this job..."? That's Working Conditions; we keep that under Requirements. We must also remove "Job site walking." that's part of Working Conditions. We must remove "EEO Statement" entirely. We must remove "Compensation Information Where required by law, pay ranges can be found in Suffolk's job postings." Actually that's part of Pay; we keep but maybe we need to trim the filler? It's substantive. We must remove "At Suffolk, we believe that our total rewards program should offer you and your family the support you need when it matters most. That’s why we have created a program that provides employees with access to a wide variety of options that can be personalized to support you and your loved ones physically, emotionally, and financially." That's part of Benefits; we keep. We must remove "For more information, click? here ." maybe part of Benefits; we can drop as it's a link instruction; but it's application instruction? It's a link for more info about benefits; could be considered boilerplate. Safer to drop that sentence. We must remove "Suffolk offers a comprehensive benefits package as part of its overall total rewards strategy." That's part of Benefits; we keep. We must remove "Salary ranges are reviewed regularly to reflect market trends." That's part of Pay; keep. We must remove "Base Salary for this position is just one component of Suffolk’s total rewards package for employees." Keep. We must remove "Actual salaries may be based on several factors including, but not limited to, a candidate's skill set, experience, education and other qualifications." Keep. We must remove "Suffolk offers a comprehensive benefits package as part of its overall total rewards strategy." Already considered. Now craft final HTML. Let's extract exact text snippets. Overview: "Overview The Project Executive provides overall leadership and direction on the construction project. Typically, the Project Executive is responsible for negotiating the Owner contract, is the main contact for the Project Manager for issues concerning budget, billing and client satisfaction, and ensures the fiscal success of the project. Suffolk is seeking people who are bold. Curious. Innovative. Caring. Looking for the career opportunity of a lifetime. We’ll challenge and inspire you to be your very best. We’ll embrace what makes you unique and lift you up as you take chances. Here, you’ll find a place where you can act with purpose and integrity, bringing intelligence and grit to every aspect of your job. Join us for the chance to achieve your ambitions and build your legacy." We'll keep as is. About Suffolk: "Suffolk is a national enterprise that builds, innovates, and invests. We provide value across the entire project lifecycle through our core construction management services and complementary business lines in real estate investment, design, self-perform construction, and technology start-up investment (Suffolk Technologies). By integrating data, artificial intelligence, and advanced technology through our Seamless Platform, we connect design, construction, and operations to deliver smarter, more predictable results and redefine how America builds. Suffolk – America’s Contractor – is a national company with more than $9 billion in annual revenue, 3,000 employees, and 17 offices, including Boston (headquarters), New York City, Miami, West Palm Beach, Tampa, Estero, Dallas, Los Angeles, San Francisco, San Diego, Las Vegas, Herndon, U.S. Virgin Islands, and other key markets. Suffolk manages some of the most complex and transformative projects in the country, serving clients across healthcare, life sciences, education, gaming, aviation, transportation, government, mission critical, and commercial sectors. Suffolk is privately held and is led by founder, chairman and CEO John Fish. Suffolk is ranked #8 on ENR’s list of “Top CM-at-Risk Contractors.” For more information, visit www.suffolk.com and follow Suffolk on Facebook , Twitter , LinkedIn , YouTube , and Instagram ." We'll keep that. Responsibilities block: need to copy exactly the responsibilities paragraph(s). It's a long paragraph with many sentences. We'll copy as is. Responsibilities text: "Provide leadership in business judgment and all financial and profitability aspects of projects under your jurisdiction Participate extensively in and the work acquisition process, working to define and develop project budgets and schedules that will achieve profitability objectives taking into account project-specific challenges Set appropriate milestones and assign staff qualified to handle the scope and complexity of the project Work closely with clients, owners, architects, and subcontractors to develop relationships that exceeds the client satisfaction to Suffolk’s demanding standards Provide oversight in managing all necessary resources throughout the entire project from start-up through closeout and ensure that the Owner’s expectations regarding budget, schedule, and quality, as well as Suffolk’s profitability objectives are met or exceeded It is expected that the Project Executive is the “common thread” that owns the project from Pre-Construction through Closeout and beyond. This involves: Oversight of projects at a high level from beginning to end including budget, costs