Senior Enterprise Architect, Military Engines (Remote)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Learn More & Apply Now:" etc. Also remove role type description? The role type description is about remote; maybe part of About the role? It's not a heading but could be included in About the role paragraph. We need to parse the posting. Let's extract content: Date Posted: 2026-09-11 (metadata, can be folded into short p or drop). Country: United States of America. Location: US-CT-REMOTE. Position Role Type: Remote U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. Security Clearance Type: None/Not Required Security Clearance Status: Not Required Then description: At RTX, the world's largest aerospace and defense company... (company overview). Then "We have an exciting remote opportunity for a Senior Enterprise Architect, Military Engines." Then "What You Will Do:" followed by bullet-like paragraphs (actually sentences). We need to turn those into

• list. Let's list responsibilities: - Enterprise Strategy & Target-State Architecture: Own and develop enterprise strategy, enterprise-level target-state architectures, and create multi‑year (3–5 year) modernization roadmaps across applications, data/analytics, integration/API, cloud/platform, and business architecture domains. - Translate functional and business strategies into operational architecture plans for major enterprise platforms (ERP, CRM, PLM, MES, Contract Lifecycle Management, Customer Data Platform, and related systems). - Guide cross‑functional transformation initiatives, ensuring alignment with long‑term enterprise technology direction. - Architecture Methodologies, Governance & Standards: Define, enhance, and implement enterprise architecture methodologies, standards, and patterns—driving consistency, interoperability, system resilience, and effective lifecycle management. - Contribute to Architecture Review Board (ARB) processes, including governance for technology selection, API standards, cloud patterns, domain models, and architectural compliance. - API-First, Event-Driven & Modern Architecture Patterns: Architect and promote adoption of API-first, event-driven, and cloud-native patterns across the enterprise to improve interoperability, capability reuse, integration velocity, and system robustness. - Define integration frameworks that support secure, scalable, and high‑throughput digital ecosystems. - Enterprise Data Architecture & Semantic/Ontology Development: Support enterprise data architecture strategy including the development and use of ontologies, semantic models, knowledge graphs, and standardized data structures. These enhance data interoperability, lineage clarity, analytics readiness, and AI‑enablement across P&W. - Leadership, Mentorship & Community of Practice Development: Mentor architects, strengthening architectural capability and advancing architecture maturity across the organization. Build and lead communities of practice, reinforcing shared learning, modern patterns adoption, and cross‑team architectural alignment. Champion product-centric and platform engineering operating models that increase digital delivery velocity and overall architecture quality. - Cross-Functional Problem Solving: Solve undefined and complex enterprise-wide architecture challenges spanning legacy and modern ecosystems—leveraging investigation, root-cause analysis, and multi-dimensional tradeoff evaluation (security, performance, cost, technical debt, risk, and business outcomes). - Executive Communication & Influence: Brief and advise executive leadership on architecture decisions, investment options, risks, standards, and transformation strategies using clear, business-oriented communication. Now qualifications: "Qualifications You Must Have:" then bullet-like paragraphs: - Bachelor’s degree in Engineering, Computer Science, Information Technology, or Information Systems and 10+ years of IT experience, including 7+ years as a senior solution architect or enterprise architect; OR advanced degree with 7+ years as a senior solution architect or enterprise architect. - Demonstrated experience in enterprise architecture thought leadership. - Demonstrated experience creating long‑term enterprise architecture roadmaps and leading large-scale digital transformation programs. - Knowledge of digital engineering as modern model-based technologies such as model-based systems engineering (MBSE), or model-based design (MBD), model-based definition, manufacturing and inspection (MBDMI), model-based services and MRO. - Experience implementing global architecture processes, governance, and standards. - Deep expertise with modern architecture frameworks, cloud-native designs, and product-aligned delivery and operating models. - Strong experience in API governance, integration design patterns, and enterprise interoperability. - Ability to provide strategic technical leadership and lead by influence the creation of long-term strategies (e.g., more than 3 years) roadmaps in a virtual environment. - Possess exceptional written and oral communication skills, can develop clear, concise, and logically written business communications, as well as deliver recommendations. "Qualifications We Prefer:" then bullet-like: - Demonstrated effectiveness working in a complex, service-intensive, deadline-driven environment. - Ability to build strong relationships to leverage information and insights across key groups. - Strong personal leadership, organizational, relationship-building, and negotiation skills. - Outstanding formal and informal presentation skills. - Knowledge and experience working in Agile teams. - Demonstrated expertise in API strategy and governance, including understanding of API architectural patterns, ability to define API standards and integration frameworks across the enterprise, and skill in articulating their benefits for business capability reuse, system interoperability, and data exchange optimization. - Self-starter with self-confidence, enthusiasm, and strong customer service orientation. Now benefits: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement." Also mention: "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance." Thus we have benefits content. Pay: "The salary range for this role is 132,400 USD - 251,600 USD. The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills." Thus we have pay. Schedule: Not explicitly mentioned. There's mention of flexible work schedules in benefits, but schedule not given. So we should not create a Schedule section because no specific schedule info. Also we have "Role Type: Remote" info. Could be part of About the role or a short p. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically About the role includes company overview and role summary. Responsibilities is the "What You Will Do". Requirements could be the citizenship and security clearance? Or maybe "Requirements" includes mandatory qualifications? But we have Qualifications sections separate. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to map content. We have "Qualifications You Must Have" and "Qualifications We Prefer". Those could go under Qualifications heading (maybe split into Required and Preferred). Could also separate Requirements (citizenship, security clearance) and Qualifications (education/experience). Skills could be separate list of skills like API governance, etc. But we have many skill-like items in qualifications. Might be better to put all qualification items under Qualifications, and maybe Skills could be empty? But we must only include sections with real specific content. If we put Skills heading but no content, that's not allowed. So we should either omit Skills if no distinct skill list, or we could extract skills from qualifications (like API governance, integration design patterns, enterprise interoperability, etc.) and put them under Skills. However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one Qualifications section, and omit Skills. But we need to follow the allowed headings list; we can omit any heading if no content. So we can omit Skills. Similarly Requirements: we have citizenship requirement and security clearance (none). That's specific content. So we can have a Requirements section with those. About the role: company overview and role summary. Responsibilities: the "What You Will Do" list. Qualifications: combine mandatory and preferred qualifications. Benefits: benefits description. Pay: salary range. Schedule: none -> omit. Now we need to ensure we preserve all substantive information. Let's extract all substantive info and place appropriately. About the role: Should include company overview (At RTX...), the remote opportunity description, role type remote, maybe mention that it's a Senior Enterprise Architect, Military Engines. Also mention that it's remote, U.S. citizenship required (but that's more Requirements). We'll keep About the role focusing on role description and company overview. Let's craft About the role paragraph(s): - At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Pratt & Whitney is a world leader in the design, manufacture and service of aircraft engines and auxiliary power systems and has been revolutionizing modern flight for over 100 years. Join us and help shape the future of aerospace and defense. We have an exciting remote opportunity for a Senior Enterprise Architect, Military Engines. - This role is remote (employees work primarily offsite). U.S. citizenship is required (but maybe move to Requirements). We'll keep citizenship in Requirements. We'll keep About the role as above without citizenship. Now Responsibilities: list as
  • each bullet. We need to preserve the bold headings? Not needed; just list items. We'll create list items with the content as sentences. Now Requirements: include: - U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. - Security Clearance Type: None/Not Required - Security Clearance Status: Not Required We could phrase as: U.S. citizenship required; no security clearance required. Now Qualifications: combine mandatory and preferred. We'll create two sub-lists? Could just list all items under Qualifications. But we might separate Required and Preferred using

    headings? Not allowed to create extra headings beyond the allowed list? We could use

    with bold? But better to just list all items; the distinction is not crucial. However we need to preserve all info; we can include both sets. We'll create

    • for each qualification item. Mandatory items list: - Bachelor’s degree in Engineering, Computer Science, Information Technology, or Information Systems and 10+ years of IT experience, including 7+ years as a senior solution architect or enterprise architect; OR advanced degree with 7+ years as a senior solution architect or enterprise architect. - Demonstrated experience in enterprise architecture thought leadership. - Demonstrated experience creating long‑term enterprise architecture roadmaps and leading large-scale digital transformation programs. - Knowledge of digital engineering as modern model-based technologies such as model-based systems engineering (MBSE), or model-based design (MBD), model-based definition, manufacturing and inspection (MBDMI), model-based services and MRO. - Experience implementing global architecture processes, governance, and standards. - Deep expertise