IT Enterprise Applications Technical Project Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to parse the job description and extract sections. Let's identify content: - Intro paragraph: "Job Description IT Enterprise Applications Technical Project Manager Collaborate with Innovative 3Mers Around the World Choosing where to start and grow your career..." This is like About the role? Could be "About the role" or maybe "Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections accordingly. We need to decide which sections have content. From posting: - About the role: The initial paragraphs describing the role, impact, etc. Could be "About the role". We'll include that. - Responsibilities: There's a "Key Responsibilities" section with bullet-like sentences. We'll extract those as list items. - Requirements: There's "Your Skills And Expertise To set you up for success in this role from day one, 3M requires (at a minimum) the following qualifications:" then list: Bachelor’s degree..., Six (6) years of IT projects... That's requirements. - Qualifications: Additional qualifications that could help you succeed even further... That's like "Preferred qualifications" maybe "Qualifications". We'll treat as "Qualifications" (or "Preferred Qualifications"). - Skills: Might be overlapping; but we have "Your Skills And Expertise" includes both required and additional. Could split: Requirements = minimum qualifications; Qualifications = additional qualifications; Skills maybe not needed separately. But we can still include Skills if there is distinct skill list. The posting includes many skill-like items under additional qualifications. Could treat that as Skills section. However instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one "Requirements" section with both minimum and preferred. But they said use headings like Requirements, Qualifications, Skills. We need to decide based on content. We have: - Minimum qualifications: Bachelor's degree, 6 years IT projects. - Additional qualifications: Strong understanding..., Experience managing projects..., Experience using project management tools..., Strong organizational skills..., PMP/Agile/Scrum Master/ITIL/cybersecurity certification..., Experience with vulnerability management tools..., Experience supporting enterprise application portfolios..., Familiarity with cloud platforms..., Experience with application rationalization..., Background working in regulated, global, or large matrixed enterprise environment. These could be considered "Qualifications" (preferred) or "Skills". The heading "Skills" could be used for skill-based items like Strong organizational skills, experience with tools, familiarity with cloud platforms, etc. The "Qualifications" could be for certifications and degrees. But we have both. Given instruction to prefer few substantive sections, we could have: - About the role (intro) - Responsibilities - Requirements (minimum qualifications) - Qualifications (additional qualifications) - Benefits (if any) - Pay (if any) - Schedule (if any) We have Pay info: "Applicable to US Applicants Only: The expected compensation range for this position is $145,676 - $178,049, which includes base pay plus variable incentive pay, if eligible." That's pay. Benefits: "In addition, this position may be eligible for a range of benefits (e.g., Medical, Dental & Vision, Health Savings Accounts, Health Care & Dependent Care Flexible Spending Accounts, Disability Benefits, Life Insurance, Voluntary Benefits, Paid Absences and Retirement Benefits, etc.). Additional information is available at: https://www.3m.com/3M/en_US/careers-us/working-at-3m/benefits/". So we have benefits. Schedule: "Work location: This role has on-site working model, with the employee working at least four days a week in the office at 3M Center, located in Maplewood, MN. Travel: May include up to 5% domestic/international Relocation: Is not authorized". That's schedule/work location. Could be Schedule section. We also have other details like "Must be legally authorized to work in country of employment without sponsorship for employment visa status (e.g., H1B status)." That's a requirement (maybe under Requirements). Also "Good Faith Posting Date Range 09/23/2026 To 10/23/2026 Or until filled" - that's metadata, could be dropped. Also "All US-based 3M full time employees will need to sign an employee agreement..." - that's legal boilerplate, drop. Also safety/EHS etc - drop as boilerplate. Also "3M does not discriminate..." - EEO boilerplate drop. Also "Please note: your application may not be considered if you do not provide your education and work history..." - application instruction, drop. Also "3M Global Terms of Use and Privacy Statement..." drop. Thus we keep substantive content: intro/about role, responsibilities, requirements (minimum), qualifications (additional), benefits, pay, schedule (work location/travel). Also maybe include "Relocation: Is not authorized" under schedule. We must not repeat job title as heading. The job title is "IT Enterprise Applications Technical Project Manager". We'll not use that as heading. Now format: Use

for each section heading. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We can keep the substance but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the original sentences but maybe break into list items. We'll produce:

  About the role

  Job Description IT Enterprise Applications Technical Project Manager Collaborate with Innovative 3Mers Around the World Choosing where to start and grow your career has a major impact on your professional and personal life, so it’s equally important you know that the company that you choose to work at, and its leaders, will support and guide you. With a wide variety of people, global locations, technologies and products, 3M is a place where you can collaborate with other curious, creative 3Mers. This position provides an opportunity to transition from other private, public, government or military experience to a 3M career The Impact You’ll Make in this Role As An IT Enterprise Applications Technical Project Manager, You Will Have The Opportunity To Tap Into Your Curiosity And Collaborate With Some Of The Most Innovative People Around The World. Here, You Will Make An Impact By We are seeking an experienced IT Enterprise Applications Technical Project Manager to lead project management efforts focused on reducing application vulnerabilities, addressing technical debt, and improving the stability, security, and maintainability of enterprise application environments.

  But that's a bit messy due to concatenation. Maybe better to split into two paragraphs: first intro, then impact statement. However we must preserve all info; we can keep as is but maybe clean up duplicate phrases. Let's extract the meaningful prose: From the start: "Job Description IT Enterprise Applications Technical Project Manager Collaborate with Innovative 3Mers Around the World Choosing where to start and grow your career has a major impact on your professional and personal life, so it’s equally important you know that the company that you choose to work at, and its leaders, will support and guide you. With a wide variety of people, global locations, technologies and products, 3M is a place where you can collaborate with other curious, creative 3Mers. This position provides an opportunity to transition from other private, public, government or military experience to a 3M career" Then: "The Impact You’ll Make in this Role As An IT Enterprise Applications Technical Project Manager, You Will Have The Opportunity To Tap Into Your Curiosity And Collaborate With Some Of The Most Innovative People Around The World. Here, You Will Make An Impact By" Then: "We are seeking an experienced IT Enterprise Applications Technical Project Manager to lead project management efforts focused on reducing application vulnerabilities, addressing technical debt, and improving the stability, security, and maintainability of enterprise application environments." We can combine into a coherent paragraph. Now Responsibilities: The bullet-like sentences after "Key Responsibilities". Let's list them: - This role will partner closely with application owners, cybersecurity teams, infrastructure teams, architects, vendors, and application stakeholders to plan, prioritize, and execute remediation initiatives across a complex enterprise technology landscape. - The ideal candidate has strong technical project management skills, experience with enterprise applications, and the ability to drive cross-functional teams toward measurable risk reduction and operational improvement. - Leading technical projects focused on vulnerability remediation, technical debt reduction, application modernization, and platform risk mitigation. - Partner with cybersecurity, infrastructure, application, and architecture teams to assess findings, define remediation plans, and track progress. - Develop project plans, timelines, milestones, dependencies, risks, and status reporting for multiple concurrent initiatives. - Coordinate vulnerability remediation efforts across application portfolios, including patching, upgrades, configuration changes, decommissioning, and technology refresh activities. - Facilitate prioritization of technical debt based on business impact, security risk, operational risk, compliance needs, and resource availability. - Track remediation progress against defined service-level expectations, risk thresholds, and project commitments. - Collaborate with technical teams to ensure remediation plans are realistic, actionable, and aligned with enterprise architecture and security standards. Note: The second bullet "The ideal candidate has strong technical project management skills..." seems more like a requirement but it's placed under responsibilities; we can keep it as responsibility? Might be better to move to requirements but we must preserve info; we can keep it under responsibilities as it's part of the posted responsibilities section. However it's about candidate qualifications; but we will keep as is. Now Requirements (minimum): "Your Skills And Expertise To set you up for success in this role from day one, 3M requires (at a minimum) the following qualifications: Bachelor’s degree in Business, Computer Science, or Technology field (completed and verified prior to start) Six (6) years of IT projects in an enterprise environment in a private, public, government or military environment" Also later: "Must be legally authorized to work in country of employment without sponsorship for employment visa status (e.g., H1B status)." That is also a requirement. Thus requirements list: - Bachelor’s degree in Business, Computer Science, or Technology field (completed and verified prior to start) - Six (6) years of IT projects in an enterprise environment in a private, public, government or military environment - Must be legally authorized to work in country of employment without sponsorship for employment visa status (e.g., H1B status). Now Qualifications (additional): list of items after "Additional qualifications that could help you succeed even further in this role include:" We'll extract each sentence. - Strong understanding of enterprise applications, application lifecycle management, infrastructure dependencies, cybersecurity concepts, and technology risk. - Experience managing projects related to vulnerability remediation, application upgrades, technical debt reduction, modernization, or platform stabilization. - Experience using project management and collaboration tools such as Jira, Azure DevOps, ServiceNow, Smartsheet, Microsoft Project, or similar platforms. - Strong organizational skills with the ability to manage multiple initiatives simultaneously. - PMP, Agile, Scrum Master, ITIL, or cybersecurity-related certification. - Experience working with vulnerability management tools or processes, such as Qualys, Wiz, or similar platforms. - Experience supporting enterprise application portfolios, including ERP, HR, finance, manufacturing, or supply