Enterprise Architect Business Systems

We need to output HTML fragment with sections only if posting has real specific content. We need to include headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. Do not invent or summarize away detail. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines and application instructions. We need to parse the posting: It starts with Introduction (some prose). Then "Your Role And Responsibilities" then bullet-like paragraphs. Then "What You Will Do" list of responsibilities. Then "Preferred Education". Then "Required Technical And Professional Expertise" list. Then "Preferred Technical And Professional Experience" list. We need to map to sections: About the role (intro). Responsibilities (Your Role And Responsibilities + What You Will Do). Requirements (Required Technical And Professional Expertise). Qualifications (Preferred Education maybe). Skills (maybe combine technical expertise?). Benefits, Pay, Schedule: none present, so we should NOT include those sections. We must not create sections with filler like "not specified". So only include sections where we have content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills? The posting includes "Preferred Technical And Professional Experience" which could be Skills. Also "Preferred Education" could be Qualifications. "Required Technical And Professional Expertise" could be Requirements. We need to decide: Use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. Thus:

  About the role

  ...intro paragraph...

  Responsibilities

  • ...list items...

  Requirements

  • ...list items...

  Qualifications

  • ...Preferred Education...

  Skills

  • ...Preferred Technical And Professional Experience...
  We must not include Benefits, Pay, Schedule. We need to preserve all substantive info, not invent or summarize away detail. So we need to extract each bullet point as separate
• . Ensure we don't lose any detail. Let's extract content. Intro: "At IBM Finance & Operations, we are the backbone of IBM’s transformation driving efficiency, transparency, and smart decision-making across the business. Our teams provide the insight and discipline that guide strategy, ensure financial strength, and enable IBM to invest in innovation and growth. Working in Finance & Operations means combining analytical skills with collaboration and curiosity. You’ll partner with colleagues across functions and geographies, using data, technology, and process excellence to create solutions that improve performance and deliver measurable impact. IBM offers continuous learning, career development, and a culture that values diverse perspectives. Join us and be part of a global team that keeps IBM moving forward, while building your own future in a dynamic and evolving environment." That's the intro. Now responsibilities: There's "Your Role And Responsibilities" paragraph then "What You Will Do" list. We need to combine them into responsibilities list. First paragraph after "Your Role And Responsibilities": "IBM's Confluent Business Systems team is looking for an Enterprise Architect to define the end-to-end architecture and technology direction for our consumption-based business. This is a principal-level individual contributor role for a SaaS and integrations technical leader who can connect business strategy, enterprise applications, integration architecture, data platforms, and measurable outcomes. You will map and shape the architecture roadmap across the quote-to-cash value stream, including customer acquisition, quoting, contracting, provisioning, entitlements, usage metering, pricing, billing, invoicing, collections, renewals, and revenue accounting. You will design the target state for the applications, integrations, data flows, and transformations required to scale revenue-generating events with frictionless business processes and high-quality, trusted data. You will be a trusted technical and business advisor to leaders across Finance, Sales, Revenue Operations, Customer Success, Product, Engineering, Data, and Enterprise Architecture. Your influence will help Confluent improve customer acquisition and retention, increase revenue, improve customer satisfaction, strengthen billing accuracy, and ensure revenue accounting is accurate and complete. This role is not limited to reviewing project designs. You will establish enterprise-level direction, make complex tradeoffs clear, guide investment and sequencing decisions, and create reusable architecture patterns that enable teams to move faster with confidence. You will also serve as a role model and force multiplier for Business Systems Analysts and Business Systems Engineers." Then "What You Will Do" list: - Define and maintain the end-to-end enterprise architecture vision and multi-year roadmap for Confluent’s consumption-based quote-to-cash ecosystem including CRM, CPQ, contract lifecycle management, usage and billing platforms such as Metronome, ERP and revenue accounting systems, customer success platforms, and data platforms - Design scalable, resilient, and frictionless flows from customer acquisition through quoting, contracting, provisioning, usage capture, pricing, billing, invoicing, collections, renewals, and revenue accounting. - Develop architecture roadmaps that balance near-term delivery, customer and business value, platform reliability, technical debt, cost, security, compliance, and long-term scalability. - Partner with business and technical leaders to translate strategic objectives into coherent application, integration, and data investments with clear sequencing and measurable outcomes. - Coach and mentor BSAs, Business Systems Engineers, architects, and delivery partners; raise the quality of solution design, technical documentation, data thinking, and engineering practices across the organization. We need to include all these as
• items. Also include the earlier paragraph sentences as list items? The instruction: Use
  • for any list of duties/requirements/benefits. The earlier paragraph is prose, not a list. Could keep as

    under responsibilities. But we could also break into list items for clarity. However we must preserve all substantive info; we can keep the paragraph as

    and then the bullet list as

    . That seems fine. Thus responsibilities section:

    IBM's Confluent Business Systems team is looking for an Enterprise Architect to define the end-to-end architecture and technology direction for our consumption-based business. This is a principal-level individual contributor role for a SaaS and integrations technical leader who can connect business strategy, enterprise applications, integration architecture, data platforms, and measurable outcomes. You will map and shape the architecture roadmap across the quote-to-cash value stream, including customer acquisition, quoting, contracting, provisioning, entitlements, usage metering, pricing, billing, invoicing, collections, renewals, and revenue accounting. You will design the target state for the applications, integrations, data flows, and transformations required to scale revenue-generating events with frictionless business processes and high-quality, trusted data. You will be a trusted technical and business advisor to leaders across Finance, Sales, Revenue Operations, Customer Success, Product, Engineering, Data, and Enterprise Architecture. Your influence will help Confluent improve customer acquisition and retention, increase revenue, improve customer satisfaction, strengthen billing accuracy, and ensure revenue accounting is accurate and complete. This role is not limited to reviewing project designs. You will establish enterprise-level direction, make complex tradeoffs clear, guide investment and sequencing decisions, and create reusable architecture patterns that enable teams to move faster with confidence. You will also serve as a role model and force multiplier for Business Systems Analysts and Business Systems Engineers.

    then
    with the five items. Now Requirements: "Required Technical And Professional Expertise" list: - 10+ years of experience in enterprise architecture, solution architecture, business systems architecture, SaaS platform engineering, systems integration, or a related discipline; equivalent practical experience is welcome. - A demonstrated track record of designing and guiding complex end-to-end architectures across quote-to-cash, order-to-cash, revenue operations, or similarly integrated enterprise value streams. - Deep technical fluency in SaaS applications, enterprise integration patterns, APIs, event-driven architecture, data modeling, data pipelines, data transformations, observability, and cloud-based platforms. - Experience architecting consumption-based, usage-based, subscription, or other complex commercial models where accurate usage, pricing, billing, invoicing, and revenue accounting are business-critical. - Experience working across CRM, CPQ, contracting, provisioning, entitlements, metering, billing, ERP, revenue accounting, customer success, and data platforms. - Ability to connect business capabilities and customer journeys to application boundaries, integration patterns, data ownership, and measurable technical and business outcomes. We'll put each as
    • . Qualifications: "Preferred Education Master's Degree". That's it. So we can have
      • Master's Degree
      . Could also note that it's preferred, but we keep as is. Skills: "Preferred Technical And Professional Experience" list: - Deep hands-on experience with Metronome or another usage-based billing, consumption management, metering, subscription billing, or revenue operations platform. - Experience with Salesforce, CPQ, NetSuite or another ERP, contract lifecycle management, revenue recognition, customer success, data warehouse, or enterprise integration platforms. - Experience designing high-volume usage-event pipelines, product and pricing catalogs, entitlements, invoice flows, credits, collections, revenue schedules, or accounting reconciliations. - Experience in a public-company, IPO-readiness, or similarly controlled environment where SOX, auditability, data governance, and financial accuracy are essential. - Experience leading application rationalization, platform modernization, integration strategy, data transformation, or technical debt reduction across a growing SaaS company. - Familiarity with domain-driven design, data mesh or data product concepts, enterprise architecture methods, cloud-native architecture, and infrastructure-as-code. - Experience defining architecture and operating models for AI-enabled automation while maintaining appropriate data, security, governance, and human-review controls. - Experience building high-trust architecture communities, design forums, mentoring programs, or shared engineering standards across a distributed organization. We'll put each as
    • . We must not include any boilerplate like EEO etc. The posting didn't have that explicitly but we should avoid any. Now output HTML fragment only. Let's craft. Be careful to escape any HTML special characters? The text includes apostrophes, ampersands? There's "IBM’s" with a curly apostrophe. Should we keep as is? Probably fine. Use straight apostrophe? We'll keep as is. Now produce:

      About the role

      At IBM Finance & Operations, we are the backbone of IBM’s transformation driving efficiency, transparency, and smart decision-making across the business. Our teams provide the insight and discipline that guide strategy, ensure financial strength, and enable IBM to invest in innovation and growth. Working in Finance & Operations means combining analytical skills with collaboration and curiosity. You’ll partner with colleagues across functions and geographies, using data, technology, and process excellence to create solutions that improve performance and deliver measurable impact. IBM offers continuous learning, career development, and a culture that values diverse perspectives. Join us and be part of a global team that keeps IBM moving forward, while building your own future in a dynamic and evolving environment.

      Responsibilities

      IBM's Confluent Business Systems team is looking for an Enterprise Architect to define the end-to-end architecture and technology direction for our consumption-based business. This is a principal-level individual contributor role for a SaaS and integrations technical leader who can connect business strategy, enterprise applications, integration architecture, data platforms, and measurable outcomes. You will map and shape the architecture roadmap across the quote-to-cash value stream, including customer acquisition, quoting, contracting, provisioning, entitlements, usage metering, pricing, billing, invoicing, collections, renewals, and revenue accounting. You will design the target state for the applications, integrations, data flows, and transformations required to scale revenue-generating events with frictionless business processes and high-quality, trusted data. You will be a trusted technical and business advisor to leaders across