NPI Project Manager

We need to output HTML fragment with sections: headings

for each section present: About the role? Actually the posting includes "Who Are We?" and "What You'll Be Doing", "What You Bring To The Table", "What You'll Get", "Additional Information", "Compensation Information". Also maybe "Travel" and "Work Environment" under Additional Information. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings if applicable, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we map content to those standard headings. However the posting has sections like "Who Are We?" (About the company), "What You'll Be Doing" (Responsibilities), "What You Bring To The Table" (Qualifications/Requirements/Skills), "What You'll Get" (Benefits), "Additional Information" (Travel, Work Environment), "Compensation Information" (Pay). So we can map: - About the role? Actually "Who Are We?" is about company, not role. Could be "About the role" maybe not. But we could use "About the role" heading for description of role? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we should use those. Probably we should produce sections: About the role (maybe combine Who Are We? and role description?), Responsibilities (What You'll Be Doing), Requirements (What You Bring To The Table - experience/education), Qualifications (maybe same as Requirements?), Skills (maybe list of skills), Benefits (What You'll Get), Pay (Compensation Information), Schedule (maybe not present). Travel and Work Environment could be under Additional Information but not a standard heading; maybe we can include under "Additional Information" as a

but not in 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 to be safe we could map Travel and Work Environment under a "Additional Information" heading as

as well, but that deviates from examples. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings; we should only use those if content exists. If we have extra content like Travel, we could incorporate into Benefits or Schedule? Not appropriate. Perhaps we can include them under "Additional Information" as a

but it's not in the list; but the instruction didn't forbid other headings, just gave examples. I'd include Additional Information as a heading. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, etc. Also remove application instructions, cookie/navigation/legal. We need to preserve all substantive information. So we need to include details from each section. Let's extract content: Who Are We? paragraph about GTU, ITW, etc. What You'll Be Doing: bullet-like paragraphs each starting with bold headings: Lead with Purpose, Bring Ideas to Market, Drive Results, Own the Process, Collaborate and Support, Find the Perfect Fit, Deliver Quality, Communicate with Impact, Improve the Future. Each has description. What You Bring To The Table: sections: Passion for Product Development, Natural Project Leader, Problem Solver by Nature, Organized and Accountable, Strong Communicator, Collaborative Mindset, Technical and Business Awareness, Experience that Matters (list of bullet items). We'll need to capture all. What You'll Get: bullet list: An open and collaborative work environment..., Opportunities..., Exposure..., Professional development..., Competitive compensation..., The opportunity... Additional Information: Travel (up to 20% domestic and international...), Work Environment (primarily an office setting...), Reasonable accommodations... Compensation Information: salary range $101,000- $130,000 annually plus performance incentive. Also note about compensation transparency. We must not include boilerplate like "ITW is an equal opportunity employer..." etc. Remove that. We also need to not include "Compensation Transparency" heading? It's part of Compensation Information; we can keep the paragraph but not as heading. We need to output only HTML fragment, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which content is list vs prose. Responsibilities: each bullet could be list items. We'll make

  • for each responsibility. Requirements/Qualifications/Skills: Could split: Experience that Matters as list; the other traits (Passion for Product Development etc.) could be list items as skills/qualities. We could treat them as
    • under Skills or Qualities. But we need to follow headings: Requirements, Qualifications, Skills. We could put experience under Requirements, traits under Skills, maybe Qualifications for education? Let's map: - Requirements: Education (Bachelor's degree in Engineering, Business, Project Management, or related field) and years of experience (3+ years experience in Product Development, Engineering, Manufacturing, or related technical disciplines; 2+ years experience managing cross-functional projects). Could be list. - Qualifications: Experience with structured product development and launch processes; APQP, PPAP, PFMEA, MOI, or related quality and launch methodologies preferred; Familiarity with manufacturing processes including machining, casting, molding, stamping, or assembly operations preferred. - Skills: Passion for Product Development, Natural Project Leader, Problem Solver by Nature, Organized and Accountable, Strong Communicator, Collaborative Mindset, Technical and Business Awareness. But the instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one "Requirements" section, and Skills into another. But we have headings list; we can use only those that have content. We'll produce sections:

      About the role

      maybe combine Who Are We? and role description? Actually "About the role" could be description of the role (What You'll Be Doing). But we already have Responsibilities. So maybe "About the role" could be brief summary: "As our business continues to grow, we are looking for a passionate and driven NPI Project Manager to help lead the successful delivery of innovative products from concept through launch phases." That's in the Who Are We? section after description. We'll put that as prose under About the role. But we also have "Who Are We?" describing company. Could we put that under About the role? Might be okay. However the instruction says "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including company description. We'll include it under About the role as prose. Responsibilities:

      Responsibilities

      with
      • each. Requirements:

        Requirements

        with
        • for education and experience. Qualifications:

          Qualifications

          with
          • for structured processes, APQP etc., manufacturing familiarity. Skills:

            Skills

            with
            • for the traits. Benefits:

              Benefits

              with
              • for What You'll Get items. Pay:

                Pay

                with

                for salary range. Schedule: Not present, so omit. Additional Information: Could be

                Additional Information

                with
                • for Travel and Work Environment. We must not include boilerplate like "Reasonable accommodations may be made..." that's part of Work Environment; we can keep it. We must not include EEO etc. Now let's craft the HTML. We'll need to escape any special characters? Not needed. Let's write:

                  About the role

                  We, the Global Tool Unit (GTU), are part of ITW's Construction Segment. We specialize in the innovation, development, and manufacturing of best-in-class fastening solutions for the global construction market. Our highly differentiated products are trusted across a wide range of applications, from wood framing and finish work to steel-to-concrete installations. We place strong emphasis on Customer Back Innovation because we know our customers' time is valuable, and shortcuts are never an option. Every product we bring to market is designed with performance, reliability, and productivity in mind because our customers depend on them every day to get the job done. The GTU currently provides more than 30 tool models across a global market that combine electromechanical subsystems, balancing both pneumatic and cordless technologies, to optimize the fastening experience throughout the trades. ITW is a Fortune 200 diversified manufacturer of specialized industrial equipment, consumables, and related service businesses operating in more than 50 countries worldwide. With a culture built on innovation, entrepreneurship, and continuous improvement, ITW empowers employees to make a meaningful impact while developing their careers. As our business continues to grow, we are looking for a passionate and driven NPI Project Manager to help lead the successful delivery of innovative products from concept through launch phases.

                  Responsibilities

                  • Lead with Purpose - Own and drive New Product Implementation (NPI) projects from concept development through product launch. Lead cross-functional teams by providing direction, managing priorities, and ensuring alignment across the business unit.
                  • Bring Ideas to Market - Guide new products through the entire development lifecycle, ensuring customer requirements, technical performance, manufacturing readiness, and business objectives remain aligned throughout the project.
                  • Drive Results - Develop and maintain project schedules, key milestones, risk management plans, and execution strategies that keep programs on track for quality, cost, and timing targets. Proactively identify project risks, facilitate issue resolution, and drive cross-functional decision making to maintain momentum and achieve successful product launches.
                  • Own the Process - Lead project reviews, phase-gate activities, launch readiness assessments, and cross-functional meetings. Ensure all project deliverables are completed on time and in compliance with established development processes.
                  • Collaborate and Support - Partner closely with Engineering, Manufacturing, Quality, Supply Chain, Marketing, and external suppliers to ensure products are designed, sourced, validated, and launched successfully. Build strong relationships across the organization, fostering collaboration and accountability while helping teams navigate challenges and competing priorities.
                  • Find the Perfect Fit - Coordinate supplier activities, prototype builds, validation efforts, and production preparation activities to ensure smooth transitions from development into manufacturing.
                  • Deliver Quality - Work closely with Quality, Engineering, and Supply Chain teams to identify potential risks early and implement robust mitigation plans. Support quality planning activities including APQP, PFMEA, PPAP, validation testing, and launch readiness reviews as required.
                  • Communicate with Impact - Serve as the primary point of communication for project status, risks, opportunities, and key decisions. Present updates to leadership and stakeholders while ensuring alignment across all levels of the organization.
                  • Improve the Future - Identify opportunities to strengthen project management processes, improve execution