Enterprise Architect

1. Mature the Enterprise Architecture Practice

• Define, communicate and control Enterprise Architecture principles, standards, engagement model, and governance processes to ensure consistent architectural decision‑making across projects and teams.
• Create and maintain foundational EA artifacts: architecture blueprints, domain and capability models, solution option assessments, high‑level solution designs, integration and data flow models, technology standards and reference architectures, roadmaps, and architecture review deliverables.
• Institutionalize architectural thinking by driving awareness, facilitating engagement, and promoting consistent practices.
• Build and refine processes for solution reviews, standards adoption, and architectural decision-making.

1. Lead Architecture Governance & the Architecture Review Board (ARB)

• Lead and animate the ARB, including agenda preparation, facilitation, documentation, decision tracking, and exception handling.
• Ensure solutions align with EA principles, security requirements, and target-state direction.
• Maintain architectural decision records and ensure clear communication with stakeholders.
• Promote consistency across applications, integrations, data flows, and platforms.
• In collaboration with ARB members, drive the decision process to award “pass/fail/exception” decision after each ARB. Document rationale and next steps.

1. Define Target-State Architectures & Multi-Year Roadmaps

• Document the As‑Is technology landscape, including systems, integrations, and architectural patterns.
• Develop Future‑State architectures across key domains (application, integration, data, security, cloud).
• Build multi-year, capability-aligned technology roadmaps that guide modernization and simplification.
• Identify opportunities to reduce redundancy, streamline platforms, and improve interoperability.

1. Provide Architecture Guidance

• Provide conceptual and logical architecture guidance to technical teams and specialists through structured design reviews, facilitated solution‑shaping workshops, early engagement during the planning lifecycle, and ongoing coaching to ensure alignment with enterprise architecture principles.
• Offer patterns and guardrails for integrations, data exchanges, and cloud architectures.
• Conduct light POCs or validations when needed to de-risk approaches or test patterns.
• Collaborate with domain specialists for detailed solution design, engineering, and implementation.

5. Drive Standardization, Simplification & Technology Alignment

• Develop reusable reference patterns (API, event-driven, data, security, cloud usage, integration).
• Promote standard platforms, shared services, and architectural coherence across regions.
• Identify technical debt and propose strategies for remediation and modernization.
• Support decision-making that improves maintainability, scalability, and long‑term sustainability.
• Document and maintain technology standards, guardrails, and design guidelines to ensure consistent implementation across teams and regions.
• Create and update authoritative reference architecture documentation capturing approved platforms, integration approaches, and technology usage patterns.

6. Foster Collaboration, Influence & Stakeholder Alignment

• Engage IT and non-IT stakeholders to connect architecture decisions with strategic goals.
• Facilitate design discussions, architecture workshops, and cross-regional alignment sessions.
• Communicate trade-offs and architectural impacts clearly to both technical and non‑technical audiences.
• Build trust through practical, value-driven architectural outcomes and early wins.
• Advocate for the adoption of EA standards and practices across delivery and product teams.
• Influence teams and leaders to embrace architecture principles as part of the delivery culture.

7. Collaborate with HOYA Corporate Enterprise Architecture Group

• Partner with the HOYA Corporate Enterprise Architecture Group to ensure alignment with global strategy and practices.
• Contribute to cost assessments, technology spend analysis, and vendor evaluations.
• Participate in infrastructure capability assessments and contribute local/regional insights.
• Support the development of global infrastructure strategies and ensure alignment with enterprise standards.
• Co-develop and refine the global transformation roadmap and synchronize local architectural plans.
• Share local architectural lessons learned to improve global governance and architectural harmonization.

Competencies

1. Strategic Thinking & Systems View

• Looks beyond one project or system and considers how decisions affect other teams and processes.
• Spots patterns, risks, and knock‑on effects early so teams can avoid rework or surprises.
• Helps shape direction by connecting the dots between business goals, technology choices, and long‑term impact.

1. Business Acumen & Value Realization

• Understands how the business works and uses that knowledge when giving architectural advice.
• Explains design options in terms of cost, effort, customer impact, and business benefit.
• Identifies ways technology decisions can improve operations, reduce waste, or support new opportunities.

1. Technology Breadth & Architectural Depth

• Has a solid understanding of how the main technology areas (cloud, data, integration, security, applications) fit together and impact each other.
• Can dig deep enough into a design to spot risks, ask the right questions, and guide teams toward a sound approach—without needing to be the hands‑on expert in every area.
• Keeps up with useful technology trends and knows when a new idea is worth considering — and when it isn’t.

1. Governance & Standards Leadership

• Promotes consistent adoption of architectural principles, guardrails, and standards.
• Evaluates solutions for compliance with reference architectures and technology strategy.
• Provides clear, unbiased recommendations in architecture boards and review forums.

1. Communication & Influence

• Translates complex architectural topics into clear, audience‑appropriate messages.
• Communicates trade‑offs, risks, and design impacts in a balanced, transparent manner.
• Influences without authority by building credibility and aligning decisions with shared goals.
• Tailors communication style to executives, product teams, engineers, and non‑technical stakeholders.

1. Problem Solving & Simplification

• Breaks down complex problems into manageable components while maintaining holistic understanding.
• Identifies areas of unnecessary complexity and proposes simplified, practical alternatives.
• Applies structured thinking to evaluate solution options and guide rational decision‑making.
• Uses data, evidence, and architectural analysis to resolve ambiguity and drive clarity.

1. Collaboration & Relationship Building

• Builds strong working relationships across IT, business, regions, and delivery teams.
• Encourages open dialogue and inclusive decision‑making.
• Works across organizational boundaries to align goals and remove friction points.
• Demonstrates empathy, listening skills, and a constructive approach in difficult conversations.

1. Adaptability & Continuous Learning

• Adjusts quickly to changing priorities, technologies, and organizational needs.
• Seeks out new trends and incorporates relevant insights into architectural recommendations.
• Shifts thinking when presented with new information or constraints.
• Demonstrates curiosity and a growth mindset, sharing learnings with peers and teams.

1. Delivery Orientation & Value Creation

• Focuses architectural work on business value, outcomes, and measurable impact.
• Balances conceptual rigor with delivery constraints, ensuring architecture supports execution.
• Drives decisions that improve maintainability, scalability, and long‑term sustainability.
• Follows through on commitments and ensures timely support to delivery teams.

1. Hands‑On Delivery & Proactive Ownership

• Engages directly with teams to clarify designs, shape solutions, and remove blockers.
• Demonstrates a practical, hands‑on approach when needed (e.g., reviewing payload designs, data flows, integration patterns).
• Takes initiative without needing direction, independently driving tasks to completion.

• Shows personal accountability for outcomes and maintains momentum even in ambiguous situations.

   

Qualifications 

To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.

Required

• Bachelor’s degree in Computer Science, Engineering, Information Technology, or related field.
• 8+ years in Enterprise, Solution, or Integration Architecture roles.
• Experience defining As‑Is and Future‑State architectures and producing roadmaps.
• Strong understanding of integration patterns (APIs, events, services), data architecture basics, and cloud/hybrid concepts.
• Demonstrated experience leading or facilitating architecture governance or ARB processes.
• Excellent communication and stakeholder management skills.
• Ability to influence without direct authority.

Preferred

• Experience building or maturing an EA practice or ARB.
• Experience in manufacturing, supply chain, or large-scale global environments.
• Certifications such as TOGAF, cloud architecture certifications, or equivalent.

• Familiarity with EA tools (LeanIX, BiZZdesign, Abacus) and diagramming tools (Visio, Lucidchart, draw.io).

   

Language Skills 

Ability to read, analyze, and interpret general business periodicals, professional journals, technical procedures, or governmental regulations.  Ability to write reports, business correspondence, and procedure manuals. Ability to effectively present information and respond to questions from groups of managers, clients, customers, and the general public.

Work Environment

• Global, cross-regional collaboration with distributed teams.
• Occasional travel for workshops or alignment sessions.
• Responsibilities may evolve as the EA discipline matures.

The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job. The noise level in the work environment is usually low.

Not Exclusive 

The duties outlined in this document are not limited to what is presented and are not exclusive. You may be asked from time to time to perform additional duties by your supervisor.