Senior Project Manager ' Aviation / Civil

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Must not include filler like "commensurate with experience". Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph(s) describing company and role: "At McFarland Johnson (MJ), we're more than infrastructure consultants ' we are a 100% employee-owned firm with 80 years of commitment to delivering innovative planning, engineering design, environmental services, technology, and construction solutions that make a lasting impact in the communities we serve. We're looking for an experienced Civil Engineer Aviation Project Manager to join our growing Aviation and Infrastructure team throughout New England. This is a great opportunity for someone who enjoys leading diverse projects, developing trusted client relationships, and helping our technical team succeed." That's about the role. - Responsibilities: The "Key Responsibilities" bullet list. - Requirements/Qualifications: The "What We're Looking For" list includes experience, etc. Also "Professional Engineer (PE) license in NH, MA, ME, CT, RI, or VT Bachelor's degree in Civil Engineering (ABET-accredited) or related field". Could be under Requirements or Qualifications. We'll decide. - Skills: maybe "Strong leadership, communication, organization, and relationship management", "Experience mentoring and developing engineers and technical staff", "Interest in client relationship management and business development", "Familiarity with the New England market, including funding sources". Could be under Skills. - Benefits: The "Compensation & Ownership Opportunity" section includes Performance Bonus, Employee Ownership (ESOP), Comprehensive Benefits: Medical (self-insured plan), 401(k) with match, HSA, generous PTO, flexible work options. Also "Why This Role is Different" includes some culture aspects but not benefits. So Benefits section: list those. - Pay: Not explicitly stated numeric salary. There's "Performance Bonus: Annual incentive plan tied to individual performance and company profitability". That's not base pay. No explicit salary range. So we should NOT create Pay section unless posting actually states them. It does not give a number, so we should omit Pay. - Schedule: Not mentioned. So omit. - Also "Why This Role is Different" includes bullet points: Client Leadership, Diverse Project Portfolio, Full Project Lifecycle, People-Centric, High-Performance Culture, Employee Ownership (again), Support System. Some of these could be part of About the role or maybe separate section like "What Makes This Role Unique". But we only allowed specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those. Could put some of those under About the role or Responsibilities. Probably incorporate into About the role (description) and maybe Responsibilities. We must not repeat job title as heading. So we will output something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

Benefits

• ...
...

We need to decide what goes where. Let's extract content precisely. About the role paragraph(s): "At McFarland Johnson (MJ), we're more than infrastructure consultants ' we are a 100% employee-owned firm with 80 years of commitment to delivering innovative planning, engineering design, environmental services, technology, and construction solutions that make a lasting impact in the communities we serve. We're looking for an experienced Civil Engineer Aviation Project Manager to join our growing Aviation and Infrastructure team throughout New England. This is a great opportunity for someone who enjoys leading diverse projects, developing trusted client relationships, and helping our technical team succeed." We could also include the "Why This Role is Different" bullet points as part of About the role? Might be better to incorporate them there to avoid extra sections. But we must preserve all substantive info. So we need to include those bullet points somewhere. Could add them under About the role as additional sentences or a list. But we must not create a new heading. So we can embed them in the About the role paragraph or as a

under About the role? The instruction: Use

for section headings, use

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

  for prose. It doesn't forbid having a list under About the role if it's a list of duties? But they said "Use

  • for any list of duties/requirements/benefits". So if we have a list that is not duties/requirements/benefits, maybe we still can use
    but it's safer to keep lists only for those categories. The "Why This Role is Different" bullet points are more about role attributes, could be considered duties? Might be okay to put under Responsibilities? But they are not responsibilities exactly. Could be under About the role as prose. We could convert each bullet into a sentence in a paragraph. Let's list them: - Client Leadership: Serve as primary client contact and trusted advisor while strengthening long term relationships with airports throughout New England. - Diverse Project Portfolio: Aviation (airside & landside), airport terminals and hangars, civil/site development, aviation planning, and environmental coordination a plus - Full Project Lifecycle: Lead projects from initial planning and client engagement through permitting and design, to construction and close-out, providing continuity for both clients and project teams. - People-Centric, High-Performance Culture: Collaborative, growth-focused, and team-oriented approach to providing quality client service - Employee Ownership: Build your career and contribute to the long-term success of where all employees share in ownership as a 100% ESOP - Support System: Join one of the largest and most successful aviation infrastructure teams in New England. Collaborate daily with our New England-based Aviation Project Managers. Rely on a significant number of existing aviation engineers of all experience levels in New England to support your projects. We can incorporate these into About the role paragraph(s) as sentences. Now Responsibilities: The "Key Responsibilities" list: - Lead and deliver complex, multidisciplinary projects across aviation, civil/site, planning, and/or environmental. - Serve as a primary client manager, developing a thorough understanding of client needs, priorities, and long-term goals - Manage project scope, schedule, and budget while ensuring technical excellence and quality delivery - Guide and mentor engineers and technical staff across teams - Support workload planning, staff development, and the continued growth of the New England team - Contribute to business development, including proposals and client engagement - Represent MJ at client meetings, industry events, and professional organizations Now Requirements/Qualifications/Skills. What We're Looking For list: - 15+ years of progressive experience in project management (aviation, transportation, civil/site, or similar) - Proven ability to lead multidisciplinary teams and deliver complex projects - Experience working on airport projects or terminal facilities is a plus - Strong leadership, communication, organization, and relationship management - Experience mentoring and developing engineers and technical staff - Interest in client relationship management and business development - Familiarity with the New England market, including funding sources - Professional Engineer (PE) license in NH, MA, ME, CT, RI, or VT - Bachelor's degree in Civil Engineering (ABET-accredited) or related field We need to split into Requirements, Qualifications, Skills as appropriate. Usually Requirements: years of experience, PE license, degree. Qualifications: maybe similar. Skills: leadership, communication, etc. But we can decide. We must not create thin sections; better to have few substantive sections. Could combine Requirements and Qualifications into one section? But we have headings for both; we could use only one if the other would be thin. The instruction: "Prefer a few substantive sections over many thin ones." So we could use only Requirements (or Qualifications) and put all the list items there, and maybe Skills separate if we have enough content. But we need to decide what goes where. Let's think: Requirements could be the mandatory items: 15+ years experience, PE license, Bachelor's degree. Qualifications could be the preferred items: experience on airport projects, familiarity with New England market, etc. Skills could be leadership, communication, mentoring, etc. Thus we can have three sections: Requirements, Qualifications, Skills. Each will have substantive content. Now Benefits: we have: - Performance Bonus: Annual incentive plan tied to individual performance and company profitability - Employee Ownership (ESOP): As a 100% employee-owned firm, you'll receive company stock at no cost, allowing you to directly share in the firm's growth and profitability. - Comprehensive Benefits: Medical (self-insured plan), 401(k) with match, HSA, generous PTO, and flexible work options We could list each as
    • . Now we must not include Pay or Schedule sections. Now we need to ensure we don't repeat any content inadvertently. Let's craft HTML. We'll start with About the role: combine initial paragraph and the "Why This Role is Different" points as sentences. We'll write:

      At McFarland Johnson (MJ), we're more than infrastructure consultants — we are a 100% employee-owned firm with 80 years of commitment to delivering innovative planning, engineering design, environmental services, technology, and construction solutions that make a lasting impact in the communities we serve. We're looking for an experienced Civil Engineer Aviation Project Manager to join our growing Aviation and Infrastructure team throughout New England. This is a great opportunity for someone who enjoys leading diverse projects, developing trusted client relationships, and helping our technical team succeed.

      Then maybe a
      for the "Why This Role is Different"? But that list is not duties/requirements/benefits; it's more about role attributes. Could still be a list but might be considered a list of duties? Safer to embed as sentences. We can add a paragraph: "This role offers client leadership as the primary contact and trusted advisor for airports throughout New England, a diverse project portfolio covering airside and landside aviation, terminals, hangars, civil/site development, aviation planning, and environmental coordination; full lifecycle leadership from planning and client engagement through permitting, design, construction, and close-out; a people‑centric, high‑performance culture focused on collaboration and quality client service; the opportunity to build your career while sharing in ownership as a 100% ESOP; and a strong support system within one of New England’s largest aviation infrastructure teams, with daily collaboration with fellow Aviation Project Managers and access to experienced aviation engineers." That covers all bullet points. Now Responsibilities:

      Responsibilities

      with each item. Now Requirements:

      Requirements

      with mandatory items: 15+ years progressive experience in project management (aviation, transportation, civil/site, or similar); Professional Engineer (PE) license in NH, MA, ME, CT, RI, or VT; Bachelor's degree in Civil Engineering (ABET-accredited) or related field. Now Qualifications:

      Qualifications

      with preferred items: Experience working on airport projects or terminal facilities (a plus); Familiarity with the New England market, including funding sources; Proven ability to lead multidisciplinary teams and deliver complex projects (maybe this is also a skill but we can put here). Actually "Proven ability to lead multidisciplinary teams and deliver complex projects" is a skill/experience. Could be under Skills. But we need to allocate. Let's decide: Requirements: mandatory baseline. Qualifications: preferred/experience items: Experience on airport projects or terminal facilities; Familiarity with New England market; Proven ability to lead multidisciplinary teams and deliver complex projects (maybe this is a skill but okay). Skills: leadership, communication,