Strategic IT Sourcing Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes "What We're Looking For", "What You'll Do", "What You Need To Succeed", "Nice to Have", "Compensation", "Why Choose Us", "About Us". Also maybe "About the role" not present. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The headings we can use: "Responsibilities" for "What You'll Do". "Requirements" for "What You Need To Succeed". "Qualifications" maybe for "Nice to Have"? Actually Nice to Have could be "Qualifications" or "Skills". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - Responsibilities: "What You'll Do" - Requirements: "What You Need To Succeed" - Qualifications: "Nice to Have" (or maybe "Skills") - Skills: maybe combine? But we can have both Qualifications and Skills if content fits. The Nice to Have list includes experience, certifications, etc. That could be "Qualifications". Skills could be maybe not present. We'll include only sections with content. - Benefits: "Why Choose Us" includes benefits list. So we can have Benefits heading. - Pay: "Compensation" includes salary range. - Schedule: not present, so omit. - About the role: maybe not needed; we have introductory paragraph at top describing company and role. Could be "About the role". The instruction says do NOT repeat the job title as a heading. But we can have About the role as a heading summarizing the role description. The introductory paragraph includes description of role and company. We could put that under About the role. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. Also remove "THIS POSTING IS FOR A CURRENT VACANCY..." maybe not needed? It's metadata but could be minor; we can fold into short p or drop. Probably drop. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Intro paragraph: "Corporate Technology Michael Baker International understands that people require choices in where they want to build a sustainable future. For more than 85 years, Michael Baker International has maintained an entrepreneurial work environment that fosters great careers and brings great success to the organization. Michael Baker offers many opportunities to grow professionally — whether in Finance, IT, Human Resources, Technology, Communications, or our National Practice and Market segments. Take your next step with us and help make a difference in the lives of those you work with and those we serve." Then "What We're Looking For Michael Baker International is seeking a Strategic IT Sourcing Lead to join our corporate Technology team. In this role, you will lead enterprise-wide technology sourcing initiatives across software, cloud infrastructure, SaaS applications, telecommunications, managed services, and professional services — driving competitive supplier evaluations, negotiating complex commercial agreements, and delivering measurable cost savings and cost avoidance. You will build and govern strategic supplier relationships that support MBI's technology operations, partnering closely with IT, Finance, Legal, Security, HR, and business unit stakeholders to ensure technology contracts are well-structured, competitively priced, and operationally sound. This is a senior individual contributor role within our corporate IT/PMO Operations organization. You will shape MBI's technology sourcing strategy, establish and mature vendor governance practices, and leverage data analytics and emerging AI-enabled procurement tools to continuously improve sourcing efficiency and supplier value. Michael Baker International does not sponsor employment visas for this position." That's basically role description; could go under About the role. Then "What You'll Do" list: many bullet-like sentences but not bullet formatted. We need to convert to

• . Each line separated by line breaks? The text includes many sentences separated by line breaks? We'll split at each leading verb? Better to treat each sentence as a list item. Let's extract bullet points: - Lead enterprise RFP, RFQ, and RFI processes for technology categories — software licensing, cloud infrastructure, SaaS applications, telecommunications, managed services, and professional services — including supplier identification, evaluation, scoring, and selection - Negotiate complex commercial agreements, including software licensing terms, SaaS subscriptions, cloud services agreements, telecom contracts, and managed services arrangements — covering pricing, SLAs, audit rights, data privacy provisions, and termination protections - Manage the full IT contract lifecycle from competitive sourcing through negotiation, execution, renewals, and closeout — maintaining a well-organized contract repository and proactive renewal calendar - Deliver measurable cost savings, cost avoidance, and total cost of ownership (TCO) improvements — with supporting financial analysis, benchmarking assessments, and documented savings methodology - Govern strategic supplier relationships through formal performance scorecards, KPI frameworks, and quarterly business reviews (QBRs) — escalating supplier performance issues and driving corrective action when needed - Conduct spend analytics and market benchmarking to identify sourcing opportunities, rationalize the supplier portfolio, and inform category strategies - Leverage procurement platforms, eSourcing tools, ERP systems, and spend analytics solutions to improve process efficiency, contract visibility, and data-driven decision-making - Identify and apply AI-enabled procurement tools, automation, and advanced analytics to enhance sourcing efficiency, supplier evaluation, contract analysis, and spend visibility - Partner with IT, Finance, Legal, Security, and business stakeholders to align sourcing priorities with enterprise technology strategy and ensure commercial agreements meet compliance, security, and operational requirements - Develop and maintain category strategies for key technology spend areas — defining market approach, preferred vendors, commercial terms standards, and renewal strategy That's 10 items. Now "What You Need To Succeed": list of requirements: - Bachelor's degree in Business, Supply Chain Management, Finance, Information Technology, or related field; equivalent experience accepted - 7+ years of progressively responsible experience in strategic sourcing, procurement, vendor management, or IT contract management — with evidence in dated role history - 3+ years specifically leading IT/technology sourcing initiatives — software, cloud, SaaS, telecom, managed services, or professional services — including direct involvement in vendor negotiations (not general procurement or purchasing) - Demonstrated experience managing or leading enterprise RFP, RFQ, or RFI competitive procurement events end-to-end — identifying vendors, structuring evaluations, scoring responses, and selecting suppliers - Experience managing the IT contract lifecycle — including software licensing, SaaS subscriptions, cloud services agreements, and telecom or managed services contracts — through negotiations, renewals, SLA oversight, and commercial risk management - Documented delivery of cost savings, cost avoidance, or TCO improvements — with supporting financial analysis; results should be evident in work history - Hands-on experience with procurement platforms, eSourcing tools, ERP systems, or CLM solutions (Oracle, SAP Ariba, Coupa, Jaggaer, Ivalua, or equivalent) in an operational role context That's 7 items. Now "Nice to Have": list: - Experience working within or directly serving Architecture, Engineering, or Construction (AEC) organizations - Experience applying AI-enabled procurement tools, robotic process automation, or advanced analytics to sourcing efficiency, contract analysis, supplier risk, or spend visibility - Oracle Financials or Oracle Procurement module experience — vendor management, PO processing, or invoice reconciliation - Ivanti or enterprise IT asset management (ITAM) tool experience - PowerBI or Power Automate experience in a procurement or spend analytics context - Professional certification: CPSM (Certified Professional in Supply Management), CSCP (Certified Supply Chain Professional), CPSD, ITIL Foundation, or CTPP (Certified Technology Procurement Professional) - Master's degree or MBA in Business Administration, Supply Chain, Finance, IT, or related field - Experience building or managing formal vendor performance scorecards, KPI frameworks, or quarterly business review (QBR) structures That's 8 items. Now "Compensation": The approximate compensation range for this position is $109,179 to $130,000. This compensation range is a good faith estimate for the position at the time of posting. Actual compensation is dependent upon factors such as education, qualifications, experience, skillset, and physical work location. We need to include Pay section with that info. Probably just a

  with the range. Now "Why Choose Us": list of benefits: - Medical, dental, vision insurance - 401(k) Retirement Plan - Health Savings Account (HSA) - Flexible Spending Account (FSA) - Life, AD&D, short-term, and long-term disability - Professional and personal development - Generous paid time off - Commuter and wellness benefits That's 8 items. Now "About Us": description of company. Could be included under About the role? But we already have About the role with intro. Maybe we keep About Us as separate section? The instruction says use headings like About the role, Responsibilities, etc. About Us not in list but could be considered "About the role"? Actually About Us is company description; we could put under About the role? But we already used About the role for role intro. Could combine both? Might be better to have About the role (role description) and About Us (company). However the instruction only gave examples; not strict to only those headings. It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. It didn't forbid other headings, but suggests using those. Safer to stick to those. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (role description + maybe company?), Responsibilities (What You'll Do), Requirements (What You Need To Succeed), Qualifications (Nice to Have), Skills? Could we treat Nice to Have as Skills? But we already used Qualifications for Nice to Have. Skills could be maybe empty; we should omit if no specific content. Benefits we have. Pay we have. Schedule none -> omit. Thus we will output:

  About the role

  ... (intro + What We're Looking For paragraph)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  The approximate compensation range for this position is $109,179 to $130,000. This compensation range is a good faith estimate for the position at the time of posting. Actual compensation is dependent upon factors such as education, qualifications, experience, skillset, and physical work location.

  We must not include boilerplate like EEO, legal, etc. Also remove "Michael Baker International does not sponsor employment visas for this position." That's substantive? It's a condition; we should keep it. It's part of role description. Keep it. Also remove "THIS POSTING IS FOR A CURRENT VACANCY..." maybe minor; we can drop. Also remove "About Us" section; we can incorporate company description into About the role? The About the role currently only has role description; we could add company description there as part of About the role. But the instruction says About the role heading; we can include both role and company description. That's fine. Thus About the role paragraph will combine the introductory corporate description and the "What We're Looking For" paragraph. Let's craft About the