Senior Enterprise Systems Developer - Procurement Systems

inside the responsibilities section? But instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those top-level headings should be h3. Inside we can use

and

• . So we need to convert the duty paragraphs into list items. Thus under Responsibilities we will have
  with each duty as
  • . Possibly we can break each major duty area into list items, maybe each bullet as a sentence. Similarly Requirements/Qualifications/Skills: The "What We're Looking For" section includes Experience, Platform Expertise, Integration & Development Skills, AI & Innovation Acumen, Audit & Compliance Acumen, Process-Oriented, Communication. Those could be split into Requirements, Qualifications, Skills. We need to decide mapping. The instructions: Use headings for those categories if posting has real specific content. We can create separate sections for Requirements, Qualifications, Skills. But we must not create thin sections; prefer few substantive sections. Could combine Requirements and Qualifications into one? But we have distinct content: Experience (years, degree) maybe Requirements; Platform Expertise, Integration & Development Skills, AI & Innovation Acumen, Audit & Compliance Acumen maybe Qualifications; Communication maybe Skills. However we could also just have one Requirements section containing all. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine into Requirements (or Qualifications) and Skills. Let's think. We have: Experience: Bachelor’s degree ... 5-7+ years... Platform Expertise: Deep experience configuring and developing in Zip, Ironclad, Oracle Fusion Cloud (Procurement modules), and Coupa. Integration & Development Skills: Strong understanding of system integration logic (REST/SOAP APIs) and data flows across intake, CLM, and ERP ecosystems. Experience with scripting and building complex conditional workflows. AI & Innovation Acumen: Familiarity with deploying, testing, or administering AI and machine learning features within SaaS platforms, specifically tailored to contract lifecycle and spend management. Audit & Compliance Acumen: Extensive experience working in a SOX-compliant environment... Process-Oriented: A deep understanding of core Procure-to-Pay (P2P), Source-to-Pay (S2P), and Contract Lifecycle Management (CLM) business processes. Communication: Excellent communication skills... Thus we could have Requirements (Experience + Process-Oriented?), Qualifications (Platform Expertise, Integration & Development Skills, AI & Innovation Acumen, Audit & Compliance Acumen), Skills (Communication). But that's three sections. Alternatively we could have Requirements (Experience, Platform Expertise, Integration & Development Skills, AI & Innovation Acumen, Audit & Compliance Acumen, Process-Oriented) and Skills (Communication). That's two sections. Given instruction to prefer few substantive sections, we could do: About the role, Responsibilities, Requirements, Skills, Benefits. Benefits from "What Makes Cloudflare Special?" includes description of projects Galileo, Athenian Project, 1.1.1.1, privacy commitment. That's substantive. Pay and Schedule: not mentioned, so omit. Thus final sections: About the role, Responsibilities, Requirements, Skills, Benefits. We need to use

    for each section heading. Inside each section, we need

    for prose and

    • for lists. For About the role: we have a paragraph: "At Cloudflare, we are on a mission to help build a better Internet. To achieve this, our internal operations must run seamlessly, securely, and efficiently. We are seeking a highly skilled, forward-thinking Senior Enterprise Systems Developer to join our Enterprise Systems team with a dedicated focus on our Procurement and Spend Management ecosystem. In this role, you will be the primary technical owner for our Procure-to-Pay (P2P) and Contract Lifecycle Management (CLM) applications. Your core tech stack will include Zip (Intake/Orchestration), Ironclad, Oracle Fusion Cloud (Procurement), and managing the transition out of Coupa. Your primary customer will be the Procurement Organization, and you will partner closely with them to optimize the way Cloudflare sources, contracts, and purchases at scale. If you are a builder at heart who enjoys solving complex supply chain and procurement workflow challenges, leveraging AI and automation, and designing seamless enterprise integrations, this role is for you." We can put that as

      . Responsibilities: list items from the four duty areas. We'll create

      with each duty area as
      • containing the description. We need to preserve all substantive information; not invent or summarize away detail. So we need to include the details within each duty area. Let's extract each duty area text: 1. Application Administration & Environment Management - Serve as the primary subject-matter expert and developer for Cloudflare’s Procurement technology stack (Zip, Ironclad, Oracle Procurement, Coupa). - Manage user provisioning, complex role-based access control (RBAC), and security settings specific to purchasing limits and contract approvals. - Manage application environments (e.g., Production vs. Sandbox/Demo), ensuring alignment across all environments from both a data and release perspective. - Monitor ongoing application performance and reliability, managing incident workflows to ensure ticket SLAs for the Procurement organization are consistently met. - Provide Tier 3 support and end-user enablement, serving as the ultimate technical escalation point for procurement system issues. 2. System Development, Integrations & AI Initiatives - Act as the Subject-Matter Expert for integrations across the procurement lifecycle. - Ensure the seamless flow of data (e.g., syncing vendor intake data from Zip, passing contract metadata from Ironclad to Oracle Fusion, and managing purchase order syncs). - Design, build, and deploy custom system enhancements, automated workflows, template generation, and API integrations between our procurement platforms and core ERP. - Lead the evaluation, implementation, and governance of native AI features within the P2P stack (e.g., Ironclad AI for contract analysis and redlining, Zip AI for vendor onboarding/intake routing) to accelerate procurement cycles. - Proactively monitor vendors' quarterly updates and product roadmaps (especially for Zip and Ironclad). Lead impact assessments, manage versioning/upgrades, and educate Procurement stakeholders on new functionality and AI opportunities. 3. Process Management & Workflow Design - Partner directly with the Procurement organization, Legal, and Finance to deeply understand their operational processes and translate business requirements into sophisticated system solutions. - Own the design, configuration, and delivery of complex workflows (e.g., global Procure-to-Pay rules, dynamic intake routing, and automated contract approvals) to eliminate manual bottlenecks. - Support the strategic migration and sun-setting of legacy systems (e.g., Coupa), ensuring zero disruption to business continuity during the transition to our modernized stack. 4. Security, Compliance, & Data Governance - Partner closely with Internal Audit, Risk, and Compliance teams to maintain robust IT General Controls (ITGC) and strict enterprise-wide data governance for spend and vendor data. - Spearhead and execute Quarterly Access Reviews (UAR) for all Procurement and CLM applications, ensuring accurate access levels and enforcing strict Segregation of Duties (SoD) within the purchasing cycle. - Ensure newly implemented AI features and data-sharing protocols strictly adhere to SOX compliance, vendor risk policies, and maintain audit readiness for all financial and contract records. - Maintain comprehensive system architecture documentation, process maps, and business continuity/disaster recovery plans for critical procurement systems. We'll put each bullet as separate
      • ? The instruction: Use
        • for any list of duties/requirements/benefits. So we could make each bullet a separate
        • . That would be many items but okay. Or we could make each duty area a
        • containing sub-bullets? But sub-bullets not allowed? Could nest
          inside
          • . That's still a list. Probably acceptable. Simpler: each bullet as
          • . We'll preserve all details. Thus Responsibilities section will have a
            with many
            • items (maybe 4 groups each with multiple bullets). We'll just flatten all bullets. Now Requirements: we need to include Experience, Platform Expertise, Integration & Development Skills, AI & Innovation Acumen, Audit & Compliance Acumen, Process-Oriented. Could be list items. Let's extract each bullet: Experience: - Bachelor’s degree in MIS, Computer Science, Supply Chain, or a related field. - 5-7+ years of hands-on experience in enterprise systems development and administration, with a strong focus on Procurement/P2P systems. Platform Expertise: - Deep, proven experience configuring and developing in Zip, Ironclad, Oracle Fusion Cloud (Procurement modules), and Coupa. Integration & Development Skills: - Strong understanding of system integration logic (REST/SOAP APIs) and data flows across intake, CLM, and ERP ecosystems. - Experience with scripting and building complex conditional workflows. AI & Innovation Acumen: - Familiarity with deploying, testing, or administering AI and machine learning features within SaaS platforms, specifically tailored to contract lifecycle and spend management. Audit & Compliance Acumen: - Extensive experience working in a SOX-compliant environment. - Highly comfortable managing quarterly access reviews, defining SoD for procurement operations, and defending system controls to audit teams. Process-Oriented: - A deep understanding of core Procure-to-Pay (P2P), Source-to-Pay (S2P), and Contract Lifecycle Management (CLM) business processes. Communication (Skills): - Excellent communication skills, with a proven ability to partner effectively with Procurement leadership and bridge the gap between technical architecture and business outcomes. We'll treat Communication as Skills section. Thus Requirements section will contain list items for Experience, Platform Expertise, Integration & Development Skills, AI & Innovation Acumen, Audit & Compliance Acumen, Process-Oriented. Skills section will contain Communication. Benefits section: from "What Makes Cloudflare Special?" includes description of projects: Galileo, Athenian Project, 1.1.1.1, privacy commitment. Also maybe mention "We’re not just a highly ambitious, large-scale technology company. We’re a highly ambitious, large-scale technology