Jobs · Education · New York

Principal Project Management

Mott MacDonald · New York, NY · 3 wk ago
Education$190k–$232k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about company, then role description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions. We need to parse content. Let's extract sections: - About the role: The description of role: "MacDonald is seeking a Principal Project Manager, Transportation to take a role in the leadership of transportation professionals in a range of discipline areas, leading the delivery of transportation projects, and the growth and development of our transportation business overall. This role and the team will be focused mainly on aviation projects. The role requires 10 to 15 years of experience in project delivery in the transportation sector, preferably within aviation. This experience may have been gained either owner-side, or consultancy or contracting or a combination. The role is based in New York City out of our midtown Manhattan office, and will require attendance at Client offices in the New York area, occasional travel to Clients further afield. In-office attendance is encouraged with a minimum of three days a week in-office working" Also earlier paragraphs about company purpose etc. Might be considered "About the role"? Usually "About the role" includes description of role and maybe company context. We'll include that. - Responsibilities: The bullet list under "Key Responsibilities:" includes several items. We'll list them as
  • . - Requirements: The "Minimum requirements:" list includes bullet points: Over 10 years of project delivery experience in the transportation field, preferably in aviation; Bachelor’s degree in architecture, relevant branch of engineering, or a relevant construction management field; Professional registration, preferably Professional Engineering (PE); Demonstrated ability to lead complex projects, with diligent effective management of cost, time, quality and risk.; Contract and commercial acumen with respect to scope clarity, change management and contractor performance oversight; Excellent communication skills. - Qualifications: Might overlap with requirements. The posting doesn't have separate qualifications beyond requirements. Could combine? But we need separate sections only if content exists. There's no explicit "Qualifications" heading. Could we treat "Minimum requirements" as Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to decide if we have content for Qualifications separate from Requirements. The posting includes "Minimum requirements:" which is essentially qualifications. Could treat that as Qualifications. But we also have Requirements maybe from responsibilities? Actually responsibilities are separate. So we could map: Requirements = maybe the "Minimum requirements". Qualifications maybe not present. However we could also treat "Minimum requirements" as Requirements and not have Qualifications. The instruction: include a section ONLY when the posting has real, specific content for it. So if we don't have distinct qualifications beyond requirements, we should not create Qualifications section. We'll have Requirements section. - Skills: The posting mentions "Excellent communication skills" under requirements, also maybe "Contract and commercial acumen", "Demonstrated ability to lead complex projects". Those could be considered skills. But we already have them under requirements. Could we create a Skills section separate? Might be redundant. Better to keep them under Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we likely will not create Skills unless there is explicit skills list. There's not. - Benefits: The posting includes "Benefits & Rewards" with salary range and benefits details. So we need Benefits section. Also Pay section: The posting includes salary range. Should we create Pay section separate? The instruction: include Pay section only if posting actually states them. It does state salary range. So we should have Pay section with that info. Benefits section can include other benefits (medical, dental, etc). However the Benefits & Rewards paragraph includes both salary and benefits. We could split: Pay: salary range. Benefits: list of benefits. That seems appropriate. - Schedule: The posting mentions in-office attendance encouraged with a minimum of three days a week in-office working. Also hybrid approach. So we have schedule info: minimum three days per week in-office. So we can create Schedule section with that. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Equal opportunity is the law..." etc. Also remove "Location(s): New York, NY, US Contract Type: Regular (US only) Work Pattern: Full Time Market: Transport Discipline: Aviation Job Ref: 17363 Recruiter Contact: Jaclyn Barone" - that's metadata, should be folded into short p or dropped. According to instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include a short p with location and maybe contract type. But we might drop it as not substantive? It's location and contract type, maybe useful. But we can include a short p at end. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, requirements, benefits, pay, schedule, about the role. Let's extract each piece precisely. About the role: We'll combine the introductory paragraphs about company and role. But we must not repeat job title as heading. The paragraphs: "At Mott MacDonald, we are driven by purpose and powered by brilliant people. As a trusted engineering, management, and development consultancy, we work with clients to solve complex challenges and deliver sustainable outcomes that make a meaningful difference for the communities we serve. When you join us as an experienced professional, you will bring your expertise to work that matters while continuing to grow your career. You will collaborate with talented colleagues across disciplines and geographies, contribute your perspective, and help shape better outcomes through technical excellence, innovation, and integrity. Build on your experience while helping shape what comes next. At Mott MacDonald, you'll work alongside talented people on complex and rewarding projects that make a real difference. We value fresh perspectives, encourage collaboration, and provide opportunities to expand your skills, take on new challenges, and grow your career. Whether you're deepening your technical expertise, broadening your leadership experience, or exploring new opportunities across our business, you'll be supported by a team that is committed to helping you succeed." Then role specifics: "MacDonald is seeking a Principal Project Manager, Transportation to take a role in the leadership of transportation professionals in a range of discipline areas, leading the delivery of transportation projects, and the growth and development of our transportation business overall. This role and the team will be focused mainly on aviation projects. The role requires 10 to 15 years of experience in project delivery in the transportation sector, preferably within aviation. This experience may have been gained either owner-side, or consultancy or contracting or a combination. The role is based in New York City out of our midtown Manhattan office, and will require attendance at Client offices in the New York area, occasional travel to Clients further afield. In-office attendance is encouraged with a minimum of three days a week in-office working" We should keep all that. Responsibilities: The list after "Key Responsibilities:" includes: - Project Management of delivery projects, in a client-facing and client-centric role, ensuring client’s needs are properly understood and addressed through close collaboration and alignment - Working with the client to establish deliverable scope, budget and timescales for tasks, and then collaborating with the internal team, subconsultants and contractors to ensure on-time and on-budget delivery - Coordination of activities on different projects and management of risks, interfaces and contingencies; coordination of design and construction activities to yield integrated delivery of solutions - Leading diligent delivery within compliance with the Mott MacDonald project management and quality systems, and within any client imposed processes - Driving personal development and learning within the role, including promoting and sponsoring the appropriate development of project staff with your team - This role will take on certain business development responsibilities, including identifying suitable opportunities, development and delivery of capture strategies and pursuits, maintenance and development of Client relationships including following Mott MacDonald’s processes for the capture and conversion of opportunities. We need to keep each as

  • . Requirements (Minimum requirements): - Over 10 years of project delivery experience in the transportation field, preferably in aviation - Bachelor’s degree in architecture, relevant branch of engineering, or a relevant construction management field - Professional registration, preferably Professional Engineering (PE) - Demonstrated ability to lead complex projects, with diligent effective management of cost, time, quality and risk. - Contract and commercial acumen with respect to scope clarity, change management and contractor performance oversight - Excellent communication skills We'll put those as
  • . Benefits: From "Benefits & Rewards" paragraph: - Expected salary for this position is $190,000 - $232,000. (We'll put in Pay) - Individual pay is determined based on several factors such as work location, education, experience, and unique skills. - In addition to base salary, Mott MacDonald offers performance-based bonuses and a comprehensive benefits package, giving employees a direct connection to our success. - Our comprehensive benefits package is designed to support the health, wellbeing, financial security, and professional growth of our employees. - Eligible employees have access to medical, dental, and vision coverage, FSA and HSA accounts, company-paid life insurance, short-term and long-term disability coverage, and a competitive 401(k) plan with company matching. - We also provide paid time off, paid holidays, caregiver leave, employee referral bonuses, professional registration and membership reimbursements, and tuition assistance to support continued learning and career development. We'll split: Pay section: salary range and maybe note about individual pay determination. Benefits section: list of benefits (medical, dental, vision, FSA/HSA, life insurance, disability, 401k matching, paid time off, paid holidays, caregiver leave, employee referral bonuses, professional registration/membership reimbursements, tuition assistance). Also performance-based bonuses could be part of Pay or Benefits; but we can include in Pay as performance-based bonuses. Schedule: From text: "In-office attendance is encouraged with a minimum of three days a week in-office working" and later: "Our hybrid approach centers on an in-office culture, with most of your time spent collaborating face-to-face and a minimum of three days per week in the office. We balance flexibility with connection, so you and your manager can choose how to meet clients, team, and personal commitments." We'll capture schedule: minimum three days per week in-office; hybrid approach; most time face-to-face. We'll put as

    maybe. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

    About the role

    ... paragraphs ...

    Responsibilities

    • ...
    • ...

    Requirements

    • ...
    • ...

    Pay

    ... salary range and individual pay determination ...

    Benefits

    • ...
    • ...

    Schedule

    ... hybrid approach ...

    Potentially also include a short p for location/metadata? Could add after schedule:

    Location: New York, NY; Contract type: Regular full‑time.

    But instruction says fold minor metadata into a short p or drop it. It's not required but could be included. However we must not invent. Location is given: New York City out of midtown Manhattan office. Contract type: Regular (US only) Work Pattern: Full Time. We could include a short p after schedule. But we already have location in About the role. Might be redundant. Safer to not add extra. We must ensure we don't include any boilerplate like EEO, legal, etc. Also remove duplicated lines. Check for

Similar jobs

Principal Project Management

Gainwell TechnologiesCalifornia, United States· 2 wk ago
RemoteEducation$116k–$166k/yrapply on jobs.gainwelltechnologies.com