IT Business Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes description, minimum qualifications, experience, must have experience, intermediate familiarity, minimum skills, principal activities and duties. Also mentions hybrid requiring in office hours (schedule). No explicit pay or benefits. So we should not include Pay or Benefits sections. Also maybe no explicit Benefits. So we can have sections: About the role (intro paragraph), Responsibilities (principal activities and duties), Requirements (minimum qualifications + experience?), Qualifications (maybe combine?), Skills (minimum skills). But we need to avoid duplication. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need to decide which sections have content. We have: - About the role: The first paragraph(s) describing role: "Do you enjoy partnering...". That's about the role. So we can have About the role. - Responsibilities: The "Principal Activities and Duties" list. That's responsibilities. - Requirements: Minimum qualifications (Bachelor's degree, 5 years experience) plus maybe "Must have experience with:" and "Must have intermediate familiarity with:" could be considered requirements. But we also have Skills section separate. Could split: Requirements = education + years experience; Qualifications = maybe the must have experience and intermediate familiarity? But the instruction says prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they are separate headings allowed. We need to decide. We have content for: - Requirements: education, years experience. - Qualifications: maybe the "Must have experience with:" and "Must have intermediate familiarity with:" could be qualifications. - Skills: "Minimum skills include:" list. - Schedule: "This position is hybrid requiring in office hours." That's schedule info. - Benefits: none. - Pay: none. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. We must not repeat job title as heading. No Job ID etc. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. So we need to include all details from the posting within those sections. We need to be careful not to include boilerplate like EEO etc. The posting ends with risk management paragraph. That's substantive? It's about risk management responsibilities. Should we include that? It's part of duties maybe. It's not boilerplate; it's a specific responsibility. So we should include it under Responsibilities. We must not include duplicated lines. Ensure we don't repeat same content. Let's extract content. First paragraph: "Do you enjoy partnering with business and IT leaders to evaluate technology options, and develop practical recommendations for strategic investments? If so, this is the position for you! This role blends business architecture, business analysis, and IT architecture practices to help the Bank develop decision-ready business cases, perform technology due diligence, evaluate costs, benefits, risks, dependencies, and implementation considerations, and support informed decision-making before significant technology commitments are made. The IT Business Architect turns complex business and technology needs into clear recommendations, investment rationale, due diligence outcomes, and visual decision aids that help leaders understand options, compare tradeoffs, and move forward with confidence. This position is hybrid requiring in office hours." We can put that in About the role (maybe also schedule line). But schedule line is separate: "This position is hybrid requiring in office hours." Could be placed in Schedule section. However About the role could include the rest, and schedule line moved to Schedule. Thus About the role: first two sentences? Actually we can include all except the schedule line. Let's split: About the role: "Do you enjoy partnering with business and IT leaders to evaluate technology options, and develop practical recommendations for strategic investments? If so, this is the position for you! This role blends business architecture, business analysis, and IT architecture practices to help the Bank develop decision-ready business cases, perform technology due diligence, evaluate costs, benefits, risks, dependencies, and implementation considerations, and support informed decision-making before significant technology commitments are made. The IT Business Architect turns complex business and technology needs into clear recommendations, investment rationale, due diligence outcomes, and visual decision aids that help leaders understand options, compare tradeoffs, and move forward with confidence." Schedule: "This position is hybrid requiring in office hours." Now Responsibilities: Principal Activities and Duties list (many bullet points). We need to convert each line into

• . Ensure we keep all details. Let's list them: - Develop, present, and maintain comprehensive business cases for strategic business and technology investments, including multi-year Total Cost of Ownership (TCO) analyses, financial modeling, cost-benefit and ROI assessments, vendor comparisons, implementation considerations, resource impacts, and value realization strategies. - Chair the Architecture Working Group (AWG), facilitate collaborative review of proposed technology solutions, coordinate input from business, architecture, security, infrastructure, application, data, and operational stakeholders, and prepare recommendations for escalation to the Architecture Review Committee (ARC) when appropriate. - Mature the ARC Technology Due Diligence process as part of the AWG by developing, documenting, maintaining, and continuously improving intake, assessment, scoring, decisioning, exception, and approval processes that support consistent and transparent evaluation of technology initiatives. - Develop, document, maintain, and improve repeatable business architecture, business analysis, and solution review processes, templates, artifacts, and standards that help IT practitioners consistently evaluate business needs, technology options, implementation impacts, and alignment to enterprise architecture expectations. - Serve as a liaison between business units and Information Technology by translating business needs, process challenges, capability gaps, and technology opportunities into clear problem statements, requirements, solution options, target-state recommendations, and decision-ready materials. - Assist IT practitioners by creating, contributing to, and improving architecture diagrams, integration views, data-flow diagrams, capability maps, process diagrams, and technology dependency diagrams that clarify system relationships, support solution design, and inform governance reviews. - Partner with business, application, infrastructure, security, data, and analytics stakeholders to identify key data entities, data ownership considerations, authoritative sources, integration points, reporting needs, data quality concerns, and downstream impacts associated with proposed solutions. - Develop and review conceptual data models, data-flow diagrams, integration views, information lifecycle considerations, and high-level data architecture artifacts that support technology due diligence, solution evaluation, implementation planning, and architecture governance decisions. - Apply business architecture, business analysis, and solution architecture practices to evaluate proposed solutions for strategic alignment, business value, operational impact, implementation readiness, technology fit, dependencies, and contribution to organizational maturity. - Bridge business and IT perspectives during planning, discovery, technology due diligence, and delivery discussions by helping stakeholders understand tradeoffs, risks, dependencies, costs, benefits, operational impacts, and decision points before significant technology commitments are made. - Evaluate proposed technology initiatives for data architecture alignment, including data reuse, data movement, system-of-record considerations, data protection needs, regulatory or risk considerations, reporting dependencies, and opportunities to reduce data duplication or unnecessary complexity. - Contribute to IT governance through the ARC Technology Due Diligence process by ensuring technology recommendations are well documented, appropriately reviewed, aligned to architecture standards, and supported by clear business rationale. - All employees have the responsibility and the accountability to serve as risk managers for their businesses by understanding, reporting, responding to, managing, and monitoring the risk they encounter daily as required by Dollar Bank’s risk management program. Compliance with regulatory laws and company procedures is a required component of all position descriptions. That's the responsibilities. Now Requirements: Minimum Qualifications: Bachelor's Degree in Computer Science, Information Systems, Business Administration, or related degree required. Will consider commensurate experience. Minimum of 5 years’ experience: o A combination of experience in business architecture, business analysis, solution design, systems analysis, process mapping, technology evaluation, vendor evaluation, road mapping, project or program support, and business case development. o Creating, contributing to, and maintaining high-level business, technology, integration, data-flow, capability, and dependency diagrams that help stakeholders understand proposed solutions and related impacts. We need to preserve all details. The "Will consider commensurate experience." is a phrase; we should keep it. We'll put Requirements section with maybe two paragraphs: education and experience. Use
  • for the list items. Now Qualifications: Must have experience with: list (multiple bullet points). Must have intermediate familiarity with: list. We'll combine them maybe as two sublists under Qualifications. We need to preserve all details. Let's extract Must have experience with: - Developing and presenting comprehensive business cases for strategic business and technology investments, including multi-year Total Cost of Ownership (TCO) analyses, financial modeling, cost-benefit and ROI assessments, vendor comparisons, implementation considerations, resource impacts, and value realization strategies. Ability to quantify business value, operational impacts, resource requirements, and long-term costs to support decision-making, procurement activities, and architecture governance approvals. - Developing and using diagram-based representations that can be adjusted as required to collect, organize, aggregate, or disaggregate complex and conflicting information about business processes, technology systems, integrations, data flows, and dependencies. - Supporting business and IT initiatives through discovery, requirements clarification, option analysis, solution evaluation, decision documentation, and implementation readiness activities. - Creating process and technology diagrams using a variety of tools and techniques. - Diagramming tools such as Microsoft Visio, Draw.io, or similar visual documentation tools. - Data architecture concepts, including data modeling, data flow analysis, data integration patterns, data lineage, metadata, reference data, master data, reporting and analytics dependencies, and the relationship between business capabilities, applications, and enterprise data assets. Now Must have intermediate familiarity with: - IT architectural concepts and information system design - IT architectural components like networks, applications, databases, firewalls, etc. - Business architecture, business analysis, solution architecture, and business-outcome-driven enterprise architecture concepts. - Architecture governance processes, technology due diligence practices, and enterprise architecture domains. - Architecture frameworks and structured evaluation methods such as TOGAF or comparable approaches. - Diagramming notation and related visual documentation approaches such as Business Process Model and Notation (BPMN), flowcharts, data-flow diagrams, and dependency diagrams. - Core data architecture practices, including conceptual and logical data modeling, entity relationships, data domains, canonical data definitions, data governance considerations, data quality concepts, data integration approaches, and reporting or analytical data consumption patterns. Now Skills: Minimum skills include: list. - Exceptional communication, facilitation, and presentation skills, including the ability to communicate appropriately at all levels of the organization through written materials, verbal discussion, executive-ready presentations, and clear visual diagrams. - Strong sense of individual accountability and the ability to work independently with minimal supervision. Demonstrated self-motivation, initiative, and ownership in driving complex business and technology initiatives to successful outcomes. - Ability to diagnose business process gaps, functional and non-functional interdependencies, cross-silo redundancies, and capability maturity gaps; identify root causes and operational impacts; and develop practical recommendations to improve processes, clarify responsibilities, reduce duplication, and strengthen business outcomes. - Ability to assimilate and correlate disconnected documentation and drawings and articulate their collective relevance to the organization and to high-priority business or technology issues. - Ability to act as a liaison between business units and Information Technology by translating needs, constraints, business rules, process considerations, requirements, architecture impacts, and operational considerations into clear diagrams, documentation, and recommendations. - Ability to translate complex technical concepts, architecture considerations, dependencies, and solution impacts into clear business terms that non-technical stakeholders can understand and use to make informed decisions. - Ability to develop a broad, enterprise-wide view of business capabilities, enabling technologies, dependencies, and architecture considerations to support decision-making and architecture review processes. - Ability to assess how data is created, transformed, shared, stored, protected, and consumed across business processes and technology solutions, and to communicate data-related impacts, risks, dependencies, and opportunities to both technical and non-technical stakeholders. - Proficient with Microsoft Office and related productivity tools