Enterprise Architect
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse content:
- About the role: The initial paragraph describing role: "Enterprise Architect Are you a strategic thinker ..." plus "This is a unique opportunity...". Could be About the role.
- Responsibilities: The bullet list under "As the Enterprise Architect, you will:" includes many items. Also later "Job Functions" percentages with details. Those are responsibilities.
- Requirements: Possibly "What You Need" section: Associate's degree, 5+ years, 3+ years, equivalent education.
- Qualifications: Might be "Minimum Qualifications" and "Required Knowledge and Skills". Could be combined.
- Skills: Could be part of Required Knowledge and Skills.
- Benefits: "Why Join FCS Financial?" includes purpose-driven work, professional growth, collaborative culture, competitive total rewards. Also "Competitive Total Rewards: Enjoy a comprehensive compensation package, incentive opportunities, and benefits designed to support your overall well-being." That's benefits.
- Pay: "Based on experience the base pay for this position is $88,000 – $135,000." So Pay section.
- Schedule: Not mentioned. No schedule info. So omit.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive info, not invent. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Requirements and Qualifications? But we can separate.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Let's extract content.
About the role: The first paragraph(s) before "The Opportunity". Let's capture:
"Enterprise Architect Are you a strategic thinker who enjoys designing enterprise technology solutions, shaping architectural direction, and driving innovation across the organization? FCS Financial is seeking an Enterprise Architect to join our Information Services team. This is a unique opportunity for a strategic technology professional to influence the future direction of organizational technology solutions, establish architectural governance, and drive innovation across the organization while supporting Missouri agriculture and rural communities. In this role, you'll serve as the driver of enterprise architecture, developing technology roadmaps, architectural standards, and governance frameworks that ensure systems, infrastructure, and technology investments align with organizational goals. You'll work across teams to drive strategic technology decisions, improve system health, and support sustainable long-term growth."
We can put that in
.
Responsibilities: The list under "As the Enterprise Architect, you will:" plus the Job Functions breakdown.
We need to combine into a list. Let's extract bullet points:
- Define and maintain enterprise architecture standards.
- Create architecture documentation, roadmaps, and decision records.
- Guide enterprise technology and platform decisions.
- Develop cloud and hybrid architecture strategies.
- Translate business needs into technical solutions.
- Evaluate emerging technologies and industry trends.
- Identify and reduce technical debt across enterprise systems.
- Promote scalable, secure, and reliable technology solutions.
Then Job Functions percentages with details: Could be considered responsibilities as well. We could include them as sub-bullets or separate list. Since we need to preserve all substantive info, we should include them. Could format as list items under Responsibilities.
Let's extract Job Functions:
40% Architectural Documentation and Governance:
- Develops and maintains comprehensive architectural documentation including system design specifications, technology reference architectures, and decision records.
- Develops, recommends and communicates architectural standards, frameworks, and governance policies to guide enterprise technology decisions across all IS teams.
- Creates technology selection criteria and approval processes; documents rationale for architectural decisions and technology recommendations.
- Develops architectural reference models and best practices documentation to support consistent technology adoption across the organization.
- Maintains current-state and target-state architecture documentation to support strategic planning and roadmap development.
- Ensures scalability, reliability, and security of systems within budget.
35% Strategic Planning & Architecture Roadmaps:
- Develops multi-year architecture roadmaps and transition plans that guide implementation teams toward operational excellence.
- Documents architectural vision and long-term technical direction; communicates strategic implications of technology decisions.
- Analyzes business requirements and translates them into architectural specifications and design principles for cross-functional stakeholders.
- Evaluates emerging platforms, tools, practices, and methodologies; documents analysis findings and recommends integration frameworks to enhance organizational architecture.
- Develops cloud adoption plans and tactics and hybrid integration frameworks; designs cloud-based architectural solutions.
- Develops proof-of-concepts using cloud platforms and integration tools; documents findings to evaluate suitability and recommend adoption strategies.
- Maintains expertise in emerging technologies, platforms, and industry trends; documents strategic implications and provides recommendations for architectural evolution.
- Provides thought leadership on emerging architectural patterns and technology trends relevant to enterprise strategy.
25% Technical Debt & System Health Management:
- Identifies, documents, and prioritizes technical debt across enterprise systems; develops remediation tactics and frameworks.
- Creates visibility into technical debt impact through documented assessments and risk analysis that inform strategic planning and resource allocation.
- Develops frameworks that balance new feature delivery with technical health and long-term system sustainability.
- Evaluates existing solutions and system architectures; documents findings and recommend architectural improvements.
- Provides guidance on technical problem resolution and systemic improvements across internal, cloud, and third-party systems.
- Other duties assigned to meet the needs of the organization.
We can include these as list items.
Requirements: "What You Need" section:
- Associate's degree in Information Technology, Computer Science, or a related field.
- 5+ years of enterprise architecture, systems design, or technical operations experience.
- 3+ years developing architecture standards, frameworks, or governance practices.
- Equivalent education and experience will be considered.
Qualifications: Minimum Qualifications and Required Knowledge and Skills.
Minimum Qualifications:
- Associate’s degree in information technology, computer science, or a related field
- 5+ years of experience in enterprise architecture, systems design, or technical operations
- 3+ years of experience developing architectural frameworks, governance policies, or standards in enterprise environments
- Or an equivalent combination of education and experience sufficient to perform the essential functions of the job
Required Knowledge and Skills: a long list. We could treat as Skills section.
But we already have Skills section maybe separate.
We need to avoid duplication. The "What You Need" overlaps with Minimum Qualifications. Could combine into Requirements. Qualifications could be the Required Knowledge and Skills.
Let's decide:
- About the role: prose.
- Responsibilities: list (combine both bullet lists).
- Requirements: list (Associate's degree, 5+ years, 3+ years, equivalent education).
- Qualifications: list (Minimum Qualifications maybe same as Requirements? Might be redundant). Could treat Qualifications as the Required Knowledge and Skills list.
- Skills: maybe not needed if we put Required Knowledge and Skills under Qualifications.
But the instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Skills if we have content.
We have Required Knowledge and Skills list; that is skills.
Thus:
Qualifications: maybe Minimum Qualifications (education/experience). Skills: Required Knowledge and Skills.
Let's extract Required Knowledge and Skills bullet points (they are sentences separated by line breaks). We'll convert each to
- .
List:
- Expert knowledge in enterprise architecture frameworks (TOGAF, Zachman, or similar) and ability to tailor frameworks for organizational context
- Expert knowledge of cloud platforms (AWS, Azure, GCP), on-premises infrastructure, and hybrid environments
- Expert knowledge in identifying, categorizing, and prioritizing technical debt across enterprise systems
- Expert knowledge in creating and maintaining comprehensive architectural documentation including design specifications and decision records
- Expert knowledge of cloud adoption strategies and hybrid integration frameworks
- Expert knowledge in evaluating emerging technologies and assessing architectural implications
- Working knowledge of strategic planning and architecture roadmap development
- Working knowledge of multi-year technology transition frameworks and migration strategies
- Working knowledge of product-based development models and cross-product dependencies
- Working knowledge of business objective translation into architectural principles
- Skill in exceptional written and verbal communication for diverse audiences
- Skill in cross-functional collaboration without direct authority
- Skill in balancing short-term product needs with long-term architectural health
- Skill in guiding organizations through technological transitions
- Skill in analyzing complex technical requirements and designing appropriate solutions
- Skill in evaluating technology viability and communicating findings to stakeholders
- Responsible for protecting the confidentiality, security, and integrity of the organization's systems and data
Now Benefits: from "Why Join FCS Financial?" and "Competitive Total Rewards". Let's extract:
- Purpose-Driven Work: Help support Missouri agriculture and rural communities.
- Professional Growth: Work with leadership teams on transformational initiatives while continuing to expand your technical and strategic expertise.
- Collaborative Culture: Partner with talented professionals who are committed to innovation, excellence, and delivering value to our member-owners.
- Competitive Total Rewards: Enjoy a comprehensive compensation package, incentive opportunities, and benefits designed to support your overall well-being.
We can make list items.
Pay: "Based on experience the base pay for this position is $88,000 – $135,000." So a
.
Schedule: none, omit.
Now ensure we don't repeat content. The Responsibilities list includes both the earlier bullet list and the Job Functions details. We'll combine them into one
.
We need to avoid duplicate items: The earlier bullet list items are similar to some in Job Functions but we can keep both; they are not exact duplicates but overlapping. It's okay to keep both as they are distinct statements.
Now produce HTML fragment:
About the role
...
Responsibilities
- Define and maintain enterprise architecture standards.
...
Requirements
- Associate's degree in Information Technology, Computer Science, or a related field.
- 5+ years of enterprise architecture, systems design, or technical operations experience.
- 3+ years developing architecture standards, frameworks, or governance practices.
- Equivalent education and experience will be considered.
Qualifications
- Associate’s degree in information technology, computer science, or a related field.
- 5+ years of experience in enterprise architecture, systems design, or technical operations.
- 3+ years of experience developing architectural frameworks, governance policies, or standards in enterprise environments.
- Or an equivalent combination of education and experience sufficient to perform the essential functions of the job.
Skills
- Expert knowledge in enterprise architecture frameworks (TOGAF, Zachman, or similar) and ability to tailor frameworks for organizational context.
...
Benefits
- Purpose-Driven Work: Help support Missouri agriculture and rural communities.
- Professional Growth: Work with leadership teams on transformational initiatives while continuing to expand your technical and strategic expertise.
- Collaborative Culture: Partner with talented professionals who are committed to innovation, excellence, and delivering value to our member-owners.
- Competitive Total Rewards: Enjoy a comprehensive compensation package, incentive opportunities, and benefits designed to support your overall well-being.
Pay
Based on experience the base pay for this position is $88,000 – $135,000.
Check for any boilerplate: No EEO etc. Good.
Make sure not to include any extra text. Output only HTML.
Let's craft the About the role paragraph exactly as we captured.
Paragraph: "Enterprise Architect Are you a strategic thinker who enjoys designing enterprise technology solutions, shaping architectural direction, and driving innovation across the organization? FCS Financial is seeking an Enterprise Architect to join our Information Services team
for prose. We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Requirements and Qualifications? But we can separate. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Let's extract content. About the role: The first paragraph(s) before "The Opportunity". Let's capture: "Enterprise Architect Are you a strategic thinker who enjoys designing enterprise technology solutions, shaping architectural direction, and driving innovation across the organization? FCS Financial is seeking an Enterprise Architect to join our Information Services team. This is a unique opportunity for a strategic technology professional to influence the future direction of organizational technology solutions, establish architectural governance, and drive innovation across the organization while supporting Missouri agriculture and rural communities. In this role, you'll serve as the driver of enterprise architecture, developing technology roadmaps, architectural standards, and governance frameworks that ensure systems, infrastructure, and technology investments align with organizational goals. You'll work across teams to drive strategic technology decisions, improve system health, and support sustainable long-term growth." We can put that in
. Responsibilities: The list under "As the Enterprise Architect, you will:" plus the Job Functions breakdown. We need to combine into a list. Let's extract bullet points: - Define and maintain enterprise architecture standards. - Create architecture documentation, roadmaps, and decision records. - Guide enterprise technology and platform decisions. - Develop cloud and hybrid architecture strategies. - Translate business needs into technical solutions. - Evaluate emerging technologies and industry trends. - Identify and reduce technical debt across enterprise systems. - Promote scalable, secure, and reliable technology solutions. Then Job Functions percentages with details: Could be considered responsibilities as well. We could include them as sub-bullets or separate list. Since we need to preserve all substantive info, we should include them. Could format as list items under Responsibilities. Let's extract Job Functions: 40% Architectural Documentation and Governance: - Develops and maintains comprehensive architectural documentation including system design specifications, technology reference architectures, and decision records. - Develops, recommends and communicates architectural standards, frameworks, and governance policies to guide enterprise technology decisions across all IS teams. - Creates technology selection criteria and approval processes; documents rationale for architectural decisions and technology recommendations. - Develops architectural reference models and best practices documentation to support consistent technology adoption across the organization. - Maintains current-state and target-state architecture documentation to support strategic planning and roadmap development. - Ensures scalability, reliability, and security of systems within budget. 35% Strategic Planning & Architecture Roadmaps: - Develops multi-year architecture roadmaps and transition plans that guide implementation teams toward operational excellence. - Documents architectural vision and long-term technical direction; communicates strategic implications of technology decisions. - Analyzes business requirements and translates them into architectural specifications and design principles for cross-functional stakeholders. - Evaluates emerging platforms, tools, practices, and methodologies; documents analysis findings and recommends integration frameworks to enhance organizational architecture. - Develops cloud adoption plans and tactics and hybrid integration frameworks; designs cloud-based architectural solutions. - Develops proof-of-concepts using cloud platforms and integration tools; documents findings to evaluate suitability and recommend adoption strategies. - Maintains expertise in emerging technologies, platforms, and industry trends; documents strategic implications and provides recommendations for architectural evolution. - Provides thought leadership on emerging architectural patterns and technology trends relevant to enterprise strategy. 25% Technical Debt & System Health Management: - Identifies, documents, and prioritizes technical debt across enterprise systems; develops remediation tactics and frameworks. - Creates visibility into technical debt impact through documented assessments and risk analysis that inform strategic planning and resource allocation. - Develops frameworks that balance new feature delivery with technical health and long-term system sustainability. - Evaluates existing solutions and system architectures; documents findings and recommend architectural improvements. - Provides guidance on technical problem resolution and systemic improvements across internal, cloud, and third-party systems. - Other duties assigned to meet the needs of the organization. We can include these as list items. Requirements: "What You Need" section: - Associate's degree in Information Technology, Computer Science, or a related field. - 5+ years of enterprise architecture, systems design, or technical operations experience. - 3+ years developing architecture standards, frameworks, or governance practices. - Equivalent education and experience will be considered. Qualifications: Minimum Qualifications and Required Knowledge and Skills. Minimum Qualifications: - Associate’s degree in information technology, computer science, or a related field - 5+ years of experience in enterprise architecture, systems design, or technical operations - 3+ years of experience developing architectural frameworks, governance policies, or standards in enterprise environments - Or an equivalent combination of education and experience sufficient to perform the essential functions of the job Required Knowledge and Skills: a long list. We could treat as Skills section. But we already have Skills section maybe separate. We need to avoid duplication. The "What You Need" overlaps with Minimum Qualifications. Could combine into Requirements. Qualifications could be the Required Knowledge and Skills. Let's decide: - About the role: prose. - Responsibilities: list (combine both bullet lists). - Requirements: list (Associate's degree, 5+ years, 3+ years, equivalent education). - Qualifications: list (Minimum Qualifications maybe same as Requirements? Might be redundant). Could treat Qualifications as the Required Knowledge and Skills list. - Skills: maybe not needed if we put Required Knowledge and Skills under Qualifications. But the instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Skills if we have content. We have Required Knowledge and Skills list; that is skills. Thus: Qualifications: maybe Minimum Qualifications (education/experience). Skills: Required Knowledge and Skills. Let's extract Required Knowledge and Skills bullet points (they are sentences separated by line breaks). We'll convert each to
. Schedule: none, omit. Now ensure we don't repeat content. The Responsibilities list includes both the earlier bullet list and the Job Functions details. We'll combine them into one
- .
We need to avoid duplicate items: The earlier bullet list items are similar to some in Job Functions but we can keep both; they are not exact duplicates but overlapping. It's okay to keep both as they are distinct statements.
Now produce HTML fragment:
- Define and maintain enterprise architecture standards. ...
- Associate's degree in Information Technology, Computer Science, or a related field.
- 5+ years of enterprise architecture, systems design, or technical operations experience.
- 3+ years developing architecture standards, frameworks, or governance practices.
- Equivalent education and experience will be considered.
- Associate’s degree in information technology, computer science, or a related field.
- 5+ years of experience in enterprise architecture, systems design, or technical operations.
- 3+ years of experience developing architectural frameworks, governance policies, or standards in enterprise environments.
- Or an equivalent combination of education and experience sufficient to perform the essential functions of the job.
- Expert knowledge in enterprise architecture frameworks (TOGAF, Zachman, or similar) and ability to tailor frameworks for organizational context. ...
- Purpose-Driven Work: Help support Missouri agriculture and rural communities.
- Professional Growth: Work with leadership teams on transformational initiatives while continuing to expand your technical and strategic expertise.
- Collaborative Culture: Partner with talented professionals who are committed to innovation, excellence, and delivering value to our member-owners.
- Competitive Total Rewards: Enjoy a comprehensive compensation package, incentive opportunities, and benefits designed to support your overall well-being.
About the role
...
Responsibilities
Requirements
Qualifications
Skills
Benefits
Pay
Based on experience the base pay for this position is $88,000 – $135,000.
Check for any boilerplate: No EEO etc. Good. Make sure not to include any extra text. Output only HTML. Let's craft the About the role paragraph exactly as we captured. Paragraph: "Enterprise Architect Are you a strategic thinker who enjoys designing enterprise technology solutions, shaping architectural direction, and driving innovation across the organization? FCS Financial is seeking an Enterprise Architect to join our Information Services team