Project Architect

We need to produce HTML fragment with sections: About the role? Actually we need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not put Job ID as heading. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About AECOM" maybe? That's company description but could be considered "About the role"? Actually "About AECOM" is company description, not role. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly. We have: Company Description (first paragraph) - could be "About the role"? Actually "About the role" would be description of role. The company description is more about AECOM. Might be considered "About the role"? Not exactly. But we could include a section "About the role" summarizing the role description. The job description paragraph: "AECOM is seeking a talented and motivated Project Architect...". That's about the role. So we can put that under

About the role

with

. Then Responsibilities: we have bullet list after "Responsibilities include but are not limited to :" with items: Design Leadership, Project Coordination, Documentation, Client Interaction, Team Collaboration. Each with description. We'll put

• each. Then Requirements: maybe "Key Competencies" could be Skills? Actually "Key Competencies" list: Design Excellence, Communication, Problem-Solving, Attention to Detail, Collaboration. Those are skills/competencies. Could go under Skills. Then "To be fully proficient in this role, the candidate must possess the following experience and skills:" then bullet list: Licensed Architect in Texas (or ability to obtain within a year), Proficiency in design software..., Strong understanding of building codes... That's Requirements/Qualifications. We'll treat as Requirements. Then Qualifications: Minimum Requirements and Preferred Qualifications. We'll put under Qualifications. Then Benefits: paragraph about AECOM benefits: "AECOM is proud to offer comprehensive benefits...". That's Benefits. Pay: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $70000 to $100000." That's Pay. Schedule: Not mentioned. No schedule info. So we omit Schedule section. Also we have "Additional Information" about sponsorship, Day 1 onboarding. That's maybe not a standard heading; could be omitted or folded into something else? It's substantive but not fitting headings. Could be placed under a generic

  maybe after Qualifications? But instruction: Prefer a few substantive sections over many thin ones. Could include as part of Qualifications? Not really. Might be better to include as a separate section like "Additional Information" but not in allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. Additional info could be omitted if not fitting. However we must preserve ALL substantive information. So we need to include that info somewhere. Could add a

  after Qualifications without a heading, or under a heading like "Additional Information" but that's not in the list. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but suggests we should use those for those sections. For other info, we can just use

  without heading. Thus we will output:

  About the role

  AECOM is seeking a talented and motivated Project Architect to join our Buildings + Places business line in Houston, Dallas and Austin Texas. This role provides an exciting opportunity to contribute to impactful projects for public and private clients. The ideal candidate will have strong design and technical expertise, a collaborative mindset, and the ability to lead design efforts while delivering high-quality architectural solutions. As a Project Architect you will play a key role in project delivery, working closely with multidisciplinary teams to ensure design excellence and client satisfaction. This position is ideal for an experienced architect looking to advance their career by taking on greater leadership responsibilities.

  Then Responsibilities. Then Skills (Key Competencies). Then Requirements (the "must possess"). Then Qualifications (Minimum and Preferred). Then Benefits. Then Pay. We also have "US West Buildings + Places as a vast market spread..." that's more about the business line; could be part of About the role or maybe omitted? It's substantive. Could be included in About the role paragraph as extra sentence. We also have "As a dynamic team of Architects, Planners, and Engineers..." etc. That's also about team. Could be included. We must preserve all substantive info. So we need to incorporate those paragraphs somewhere. Let's extract all substantive paragraphs: - Company Description (first big paragraph) about AECOM delivering better world etc. That's company overview, not role. Might be considered "About AECOM". Not in headings list but we could include as a

  before About the role? The instruction says remove boilerplate, but this is not boilerplate; it's company description. Could be kept as a

  without heading. - Job Description paragraph (the one we used for About the role). Already captured. - "US West Buildings + Places as a vast market spread and geography, providing opportunities across a wide range of project typologies, including Science & Technology, Advanced Manufacturing, Commercial, Aerospace, Higher Education, Industrial and Process, Transportation, Aviation, Sports and Federal market sectors across the western United States and beyond. As a dynamic team of Architects, Planners, and Engineers. We strive to incorporate beauty, sustainability, resiliency, equity, and innovation in our projects." This is substantive about the team/market. Could be added to About the role or as its own paragraph. - Responsibilities list. - Key Competencies list. - "To be fully proficient in this role, the candidate must possess the following experience and skills:" list. - Qualifications section (Minimum Requirements, Preferred Qualifications). - Additional Information: sponsorship, Day 1 onboarding. - Benefits paragraph. - Pay range. - "About AECOM" later paragraph (again company description). Duplicate of earlier? It's similar but more detail. Could be omitted as duplicate? It says remove duplicated lines. This is similar to earlier company description but not identical; still about AECOM. Might be considered duplicate content; we could keep one version. To avoid duplication, we could keep the earlier company description and omit the later "About AECOM" paragraph. - "What makes AECOM a great place to work" paragraph: that's also substantive about culture. Could be included under Benefits? Or maybe as its own section? Not in headings list. Could be added as a

  after Benefits. - EEO etc boilerplate to remove. - ReqID etc metadata to drop. Thus we need to include all substantive info: company description (first), US West Buildings + Places paragraph, About the role (job description), Responsibilities, Key Competencies (Skills), Requirements (must possess), Qualifications, Additional Information (sponsorship, Day 1 onboarding), Benefits, Pay, What makes AECOM a great place to work. We must not create sections with filler. All sections we create have content. We'll structure:

  Company description...

  US West Buildings + Places paragraph...

  About the role

  Job description paragraph...

  Responsibilities

  ...

  Skills

  ...

  Requirements

  ...

  Qualifications

  Minimum Requirements: ...

  Preferred Qualifications: ...

  Benefits

  AECOM is proud to offer comprehensive benefits...

  Pay

  Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $70000 to $100000.

  What makes AECOM a great place to work paragraph...

  We also need to include Additional Information (sponsorship, Day 1 onboarding). Could be placed after Qualifications as a

  without heading. Let's craft the content precisely, preserving details. Company Description first paragraph: "Work with Us. Change the World. At AECOM, we're delivering a better world. Whether improving your commute, keeping the lights on, providing access to clean water, or transforming skylines, our work helps people and communities thrive. We are the world's trusted infrastructure consulting firm, partnering with clients to solve the world’s most complex challenges and build legacies for future generations. There has never been a better time to be at AECOM. With accelerating infrastructure investment worldwide, our services are in great demand. We invite you to bring your bold ideas and big dreams and become part of a global team of over 50,000 planners, designers, engineers, scientists, digital innovators, program and construction managers and other professionals delivering projects that create a positive and tangible impact around the world. We're one global team driven by our common purpose to deliver a better world. Join us." We'll keep as is. US West Buildings + Places paragraph: "US West Buildings + Places as a vast market spread and geography, providing opportunities across a wide range of project typologies, including Science & Technology, Advanced Manufacturing, Commercial, Aerospace, Higher Education, Industrial and Process, Transportation, Aviation, Sports and Federal market sectors across the western United States and beyond. As a dynamic team of Architects, Planners, and Engineers. We strive to incorporate beauty, sustainability, resiliency, equity, and innovation in our projects." Note there is a period after "Engineers." Might be okay. About the role paragraph: "AECOM is seeking a talented and motivated Project Architect to join our Buildings + Places business line in Houston, Dallas and Austin Texas. This role provides an exciting opportunity to contribute to impactful projects for public and private clients. The ideal candidate will have strong design and technical expertise, a collaborative mindset, and the ability to lead design efforts while delivering high-quality architectural solutions. As a Project Architect you will play a key role in project delivery, working closely with multidisciplinary teams to ensure design excellence and client satisfaction. This position is ideal for an experienced architect looking to advance their career by taking on greater leadership responsibilities." Responsibilities list items: - Design Leadership : Lead the design process for projects in commercial, industrial, logistics, and interiors sectors, ensuring innovative and functional solutions. - Project Coordination : Collaborate with project teams, including engineers, consultants, and other stakeholders, to integrate architectural and technical solutions. - Documentation : Prepare and oversee detailed design documentation, including drawings, specifications, and reports, ensuring accuracy and compliance with building codes. - Client Interaction : Support client engagement efforts, including presentations, design reviews, and addressing project-related inquiries. - Team Collaboration : Work closely with senior architects and project managers to deliver projects on time and within budget. We need to keep the colon after each heading? In original they have "Design Leadership :" etc. We'll keep as is. Skills list (Key Competencies): - Design Excellence : Passion for creating innovative and functional architectural solutions. - Communication : Strong verbal and written communication skills, with the ability to present ideas clearly to clients and stakeholders. - Problem-Solving : Creative and analytical thinker capable of addressing complex design challenges. - Attention to Detail : Commitment to accuracy and quality in all aspects of project delivery. - Collaboration