Senior Project Manager, Aviation
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content for Responsibilities (list), Qualifications (list), Work Arrangement & Travel (maybe schedule?), Physical Requirements (maybe schedule?), Compensation And Benefits (benefits). Also maybe "About the role" could be the introductory paragraphs describing role. We should not repeat job title. No Job ID. Remove boilerplate like EEO etc. Also remove navigation etc.
We need to preserve all substantive info. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections:
- About the role: could contain the introductory paragraphs describing the role (the first few paragraphs before "Responsibilities").
- Responsibilities: list of duties.
- Qualifications: list of qualifications (education, licensure, experience, etc.)
- Skills: maybe we can extract skills from qualifications: leadership, communication, negotiation, presentation, business development, client account management, etc. Could be separate.
- Benefits: from Compensation And Benefits section.
- Pay: The posting says "Compensation will be determined based on factors such as experience, education, licensure, skills, internal equity, and location." That's not a specific number, but it's still compensation info. The rule: never create Pay section unless posting actually states them. It does state compensation will be determined based on factors... That's still stating compensation info, albeit not a number. Should we include Pay? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation info, so we can include Pay section with that sentence. However we also have Benefits section. Could combine? But they said prefer few substantive sections over many thin ones. Could combine Compensation and Benefits into one Benefits section? But they have separate headings possible. We could have a Benefits section that includes both compensation description and benefits. But they said use headings for Benefits, Pay, Schedule. If we combine, we might lose specificity. However we can include Pay section with the compensation determination sentence, and Benefits section with list of benefits.
- Schedule: Work Arrangement & Travel includes full-time on-site, travel required. That's schedule info. Could be Schedule section.
- Physical Requirements maybe could be part of Schedule or separate? Not a standard heading; we could incorporate into Schedule or maybe omit as not matching headings. But we need to preserve all substantive info. Could put physical requirements under Schedule as part of work arrangement? Or maybe under Responsibilities? Better to create a Schedule section that includes work arrangement and travel and physical requirements.
But the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to decide which to include.
We have:
- About the role: intro paragraphs.
- Responsibilities: list.
- Qualifications: list (education, licensure, experience, etc.)
- Skills: maybe we can extract from qualifications: leadership, communication, negotiation, presentation, business development, client account management, etc. Could be separate.
- Benefits: list of benefits.
- Pay: compensation determination statement.
- Schedule: work arrangement, travel, physical requirements.
We should not include Requirements heading if we have Qualifications and Skills; but we could combine Requirements with Qualifications? The heading list includes Requirements as possible. But we have Qualifications already. Could we omit Requirements and just use Qualifications? Probably fine.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO statement at end. Also remove navigation like "Read about it here." and "FSB has joined Colliers Engineering & Design. Read about it here." That's promotional; we should remove that line. Also remove "Why FSB" paragraph? That's promotional but still substantive about company; maybe we can keep as part of About the role? But it's after responsibilities etc. It's more about company culture. Could be considered boilerplate? Not exactly EEO. It's about why FSB. Might be considered promotional but still substantive. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Why FSB" paragraph is not exactly boilerplate; it's describing the firm. Could be considered part of About the role? Might be okay to keep. However we already have About the role intro; we could incorporate that paragraph there.
But we must preserve ALL substantive information. So we need to include that info somewhere. Could add to About the role section.
Let's extract the intro paragraphs before "Responsibilities":
"FSB has joined Colliers Engineering & Design. Read about it here. At FSB Architects + Engineers, we believe our greatest projects begin with lasting relationships. For decades, we've partnered with clients to solve complex challenges, deliver exceptional design solutions, and create spaces that strengthen communities. Our success is built on trust, collaboration, and a commitment to delivering value far beyond a single project. We're seeking an experienced Senior Project Manager to lead the successful delivery of complex architecture and engineering projects within the Aviation Market while also taking an active role in strategic client management and the development of less experienced Project Managers. In addition to overseeing projects from planning through construction, this role works closely with Aviation Market Sector Principals to strengthen client relationships, identify opportunities for continued partnership, and support long-term client success through exceptional project execution within the aviation design space. If you're passionate about leading high-performing teams, delivering exceptional projects, and building trusted client relationships that create lasting partnerships, we'd love to connect with you."
We should remove the first sentence about FSB joining Colliers and "Read about it here." as promotional/navigation. So we start from "At FSB Architects + Engineers, we believe..."
Thus About the role section will contain that paragraph (maybe two paragraphs). Also we could add the "Why FSB" paragraph later? That paragraph: "Why FSB At FSB Architects + Engineers, our people and relationships set us apart. We bring together architects, engineers, interior designers, and planners to deliver innovative solutions across aviation, federal, civic, commercial, education, healthcare, mission critical, and other specialized markets. If you're passionate about building trusted client relationships, leading high-performing teams, and helping grow a collaborative design firm, we'd love to hear from you." That's also substantive about company. Could be appended to About the role.
Now Responsibilities: list of duties. We need to extract each duty as
- . The responsibilities paragraph is a long sentence with many duties separated by periods. We need to split into list items. Let's parse:
"Lead planning and execution of the firm’s largest and most complex architecture and engineering projects within the aviation market through all phases, ensuring successful delivery of scope, schedule, budget, and quality.
Develop and implement Project Strategic Plans aligned with client objectives and aviation market sector goals.
Serve as the primary client contact, building trusted relationships through proactive communication and exceptional service to aviation clients and project stakeholders.
Prepare and negotiate scopes of work, fee proposals, contracts, and consultant agreements for aviation design projects.
Lead multidisciplinary project teams by coordinating internal staff, consultants, and resources to achieve project objectives across aviation facilities and related infrastructure.
Monitor project budgets, schedules, profitability, invoicing, quality, and risk, proactively addressing issues and implementing recovery plans when needed.
Communicate project status, priorities, and strategic direction with Aviation Market Sector Principals, Discipline Directors, and firm leadership.
Provide oversight, mentoring, and support to less experienced Project Managers and project team members while fostering collaboration, accountability, and continuous improvement.
Serve as key contributor to business development and pursuit activities within the aviation market, including proposal strategy and development, scope and fee development, interview preparation, and client presentations.
Build and strengthen client relationships by serving as a trusted advisor, identifying opportunities to add value throughout project delivery.
Partner closely with Aviation Market Sector Principals to expand existing client relationships, identify project opportunities, and contribute project delivery insight to pursuit strategy.
Participate in and, when assigned, lead client meetings, presentations, interviews, and business development activities within the aviation market to support client retention, repeat work, and continued partnership."
We'll make each as
- .
Qualifications: list:
"Bachelor's or Master's degree in Architecture, Engineering, Construction Management, or other closely related field.
Professional licensure preferred.
Candidates who are not licensed must hold a PMP or other equivalent project management certification.
15+ years of experience leading complex architectural and engineering projects and multidisciplinary teams, including at least five years of project management experience.
Experience managing aviation design projects, including airport, airline, terminal, hangar, maintenance, support facility, or related aviation infrastructure projects, is preferred.
Demonstrated success developing and maintaining long-term client relationships.
Strong understanding of project management principles, including budgeting, contracts, scheduling, resource planning, and quality management.
Excellent leadership, communication, negotiation, and presentation skills.
Business development and client account management experience within the aviation market preferred."
We'll make each as
- .
Skills: Could extract from qualifications: leadership, communication, negotiation, presentation, business development, client account management, etc. But we already have those in qualifications. To avoid duplication, maybe we skip Skills section and keep Qualifications only. However the instruction says we can use Skills heading if we have specific content. We could create Skills section listing: Leadership, Communication, Negotiation, Presentation, Business Development, Client Account Management, Strategic Planning, etc. But that would duplicate info from Qualifications. Better to not create Skills if it would be thin or duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills and keep Qualifications.
Benefits: list from Compensation And Benefits: "This role is eligible for a benefits package that may include medical, dental, vision, paid time off, paid holidays, and retirement plan options. Stated benefits are for regular full-time positions. Temporary and part-time roles eligible for limited benefits."
We'll make each benefit as
- . Also note the statement about temporary/part-time; we can include as a
maybe.
Pay: "Compensation will be determined based on factors such as experience, education, licensure, skills, internal equity, and location."
We'll put that as
under Pay section.
Schedule: Work Arrangement & Travel plus Physical Requirements.
Work Arrangement & Travel: "This is a full-time, on-site position based in our Oklahoma City, Tulsa or Dallas office. Travel is required to support client meetings, project site visits, construction observation, airport coordination meetings, business development activities, and industry conferences. Travel frequency will vary based on project assignments."
Physical Requirements: list items:
- Prolonged periods of sitting at a desk and working on a computer.
- Regular participation in client meetings, presentations, and collaborative project discussions.
- Ability to travel to project sites, airports, and client locations.
- Ability to navigate active construction sites and airport facilities, including walking, climbing stairs, and standing for extended periods while conducting site observations.
- Must be able to occasionally lift and carry plans, project documents, or other materials up to 25 pounds.
We'll make each as
- under Schedule.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
... paragraphs ...
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- medical
- dental
- vision
- paid time off
- paid holidays
- retirement plan options
Stated benefits are for regular full-time positions. Temporary and part-time roles eligible for limited benefits.
Pay
Comp
for prose. We need to decide sections: - About the role: could contain the introductory paragraphs describing the role (the first few paragraphs before "Responsibilities"). - Responsibilities: list of duties. - Qualifications: list of qualifications (education, licensure, experience, etc.) - Skills: maybe we can extract skills from qualifications: leadership, communication, negotiation, presentation, business development, client account management, etc. Could be separate. - Benefits: from Compensation And Benefits section. - Pay: The posting says "Compensation will be determined based on factors such as experience, education, licensure, skills, internal equity, and location." That's not a specific number, but it's still compensation info. The rule: never create Pay section unless posting actually states them. It does state compensation will be determined based on factors... That's still stating compensation info, albeit not a number. Should we include Pay? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation info, so we can include Pay section with that sentence. However we also have Benefits section. Could combine? But they said prefer few substantive sections over many thin ones. Could combine Compensation and Benefits into one Benefits section? But they have separate headings possible. We could have a Benefits section that includes both compensation description and benefits. But they said use headings for Benefits, Pay, Schedule. If we combine, we might lose specificity. However we can include Pay section with the compensation determination sentence, and Benefits section with list of benefits. - Schedule: Work Arrangement & Travel includes full-time on-site, travel required. That's schedule info. Could be Schedule section. - Physical Requirements maybe could be part of Schedule or separate? Not a standard heading; we could incorporate into Schedule or maybe omit as not matching headings. But we need to preserve all substantive info. Could put physical requirements under Schedule as part of work arrangement? Or maybe under Responsibilities? Better to create a Schedule section that includes work arrangement and travel and physical requirements. But the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to decide which to include. We have: - About the role: intro paragraphs. - Responsibilities: list. - Qualifications: list (education, licensure, experience, etc.) - Skills: maybe we can extract from qualifications: leadership, communication, negotiation, presentation, business development, client account management, etc. Could be separate. - Benefits: list of benefits. - Pay: compensation determination statement. - Schedule: work arrangement, travel, physical requirements. We should not include Requirements heading if we have Qualifications and Skills; but we could combine Requirements with Qualifications? The heading list includes Requirements as possible. But we have Qualifications already. Could we omit Requirements and just use Qualifications? Probably fine. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO statement at end. Also remove navigation like "Read about it here." and "FSB has joined Colliers Engineering & Design. Read about it here." That's promotional; we should remove that line. Also remove "Why FSB" paragraph? That's promotional but still substantive about company; maybe we can keep as part of About the role? But it's after responsibilities etc. It's more about company culture. Could be considered boilerplate? Not exactly EEO. It's about why FSB. Might be considered promotional but still substantive. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Why FSB" paragraph is not exactly boilerplate; it's describing the firm. Could be considered part of About the role? Might be okay to keep. However we already have About the role intro; we could incorporate that paragraph there. But we must preserve ALL substantive information. So we need to include that info somewhere. Could add to About the role section. Let's extract the intro paragraphs before "Responsibilities": "FSB has joined Colliers Engineering & Design. Read about it here. At FSB Architects + Engineers, we believe our greatest projects begin with lasting relationships. For decades, we've partnered with clients to solve complex challenges, deliver exceptional design solutions, and create spaces that strengthen communities. Our success is built on trust, collaboration, and a commitment to delivering value far beyond a single project. We're seeking an experienced Senior Project Manager to lead the successful delivery of complex architecture and engineering projects within the Aviation Market while also taking an active role in strategic client management and the development of less experienced Project Managers. In addition to overseeing projects from planning through construction, this role works closely with Aviation Market Sector Principals to strengthen client relationships, identify opportunities for continued partnership, and support long-term client success through exceptional project execution within the aviation design space. If you're passionate about leading high-performing teams, delivering exceptional projects, and building trusted client relationships that create lasting partnerships, we'd love to connect with you." We should remove the first sentence about FSB joining Colliers and "Read about it here." as promotional/navigation. So we start from "At FSB Architects + Engineers, we believe..." Thus About the role section will contain that paragraph (maybe two paragraphs). Also we could add the "Why FSB" paragraph later? That paragraph: "Why FSB At FSB Architects + Engineers, our people and relationships set us apart. We bring together architects, engineers, interior designers, and planners to deliver innovative solutions across aviation, federal, civic, commercial, education, healthcare, mission critical, and other specialized markets. If you're passionate about building trusted client relationships, leading high-performing teams, and helping grow a collaborative design firm, we'd love to hear from you." That's also substantive about company. Could be appended to About the role. Now Responsibilities: list of duties. We need to extract each duty as
maybe. Pay: "Compensation will be determined based on factors such as experience, education, licensure, skills, internal equity, and location." We'll put that as
under Pay section. Schedule: Work Arrangement & Travel plus Physical Requirements. Work Arrangement & Travel: "This is a full-time, on-site position based in our Oklahoma City, Tulsa or Dallas office. Travel is required to support client meetings, project site visits, construction observation, airport coordination meetings, business development activities, and industry conferences. Travel frequency will vary based on project assignments." Physical Requirements: list items: - Prolonged periods of sitting at a desk and working on a computer. - Regular participation in client meetings, presentations, and collaborative project discussions. - Ability to travel to project sites, airports, and client locations. - Ability to navigate active construction sites and airport facilities, including walking, climbing stairs, and standing for extended periods while conducting site observations. - Must be able to occasionally lift and carry plans, project documents, or other materials up to 25 pounds. We'll make each as
About the role
... paragraphs ...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- medical
- dental
- vision
- paid time off
- paid holidays
- retirement plan options
Stated benefits are for regular full-time positions. Temporary and part-time roles eligible for limited benefits.
Pay
Comp