Technical Infrastructure
Il y a 2 heures
Liège, Walloon Region, Belgique
NRB
Temps plein
Gratuit avec email ou Google
Enregistrez cette offre et organisez votre recherche
Créez un compte gratuit pour enregistrer des offres d'emploi, créer des alertes et revenir à cette liste depuis votre tableau de bord.
Gratuit avec email ou Google
En continuant, vous acceptez nos Conditions d’utilisation & Politique de confidentialité.
h3Job Description /h3 pJoining KEYES means giving purpose to your talent. Are you looking for an environment where technology is not an end in itself, but a lever to build a sustainable future? At /p pJoining KEYES means giving purpose to your talent. Are you looking for an environment where technology is not an end in itself, but a lever to build a sustainable future? At KEYES, we are not just looking for technical expertise; we are looking for people who share our values. Do you want to continue your career and grow within one of Belgium’s leading IT companies? Join KEYES as a Technical Infrastructure Network Architect KEYES supports private and public organizations in Belgium and across Europe in their digital transformation by combining business expertise, technological mastery, and a long-term vision. We support large enterprises, the public sector, healthcare organizations, and SMEs in all their digital challenges: Infrastructure Cloud Solutions, Cybersecurity Solutions, Business Software Solutions, Mainframe Solutions, Data AI Solutions, Advisory Solutions, and Staffing Solutions. More information: /p h3YOUR MISSION /h3 pProvide technical architecture leadership across infrastructure, network, cloud and hybrid environments, supporting transformation, modernization and operational initiatives across multiple projects and sites, including industrial/OT environments. /p pThe role is to define coherent, secure, resilient and operable technical architectures and support their delivery from design through implementation and transition to operations. /p pThe architect must be able to reason beyond individual infrastructure components and understand the broader architecture context: applications, data flows, trust zones, integration mechanisms, cloud connectivity, security and operational constraints. /p h3Positioning within the Architecture Organization /h3 pThe Technical Infrastructure Network Architect works closely with Enterprise, Solution, Application, Data, Cloud and Security Architects, as well as Infrastructure, Network, DevOps and project teams. /p pThe role is accountable for the technical infrastructure architecture required to host, connect, secure, operate and recover solutions, including network, compute, storage, backup, cloud/hybrid infrastructure, container foundations and observability. /p pEnd-to-end architecture is developed jointly. The architect must actively contribute to cross-domain architecture decisions and challenge proposed solutions when required. /p pNetwork and infrastructure architecture are considered part of the overall solution architecture, not isolated technical domains. /p h3Key Responsibilities /h3 ul liTranslate business, application and solution requirements into technical architecture requirements covering hosting, connectivity, performance, availability, security, resilience, backup/recovery, monitoring and supportability. /li liDefine target and reference architectures, reusable standards and technical patterns across sites. /li liProduce HLDs and architecture documentation, and review LLDs and detailed technical designs. /li liAnalyse impacts, dependencies, risks, architecture gaps, single points of failure and operational constraints. /li liChallenge solutions proposed by projects, suppliers and engineering teams and assess alternative options. /li liDocument key architecture decisions through Architecture Decision Records (ADRs). /li liAssess deviations from architecture and technical standards and support the relevant governance and approval processes. /li liDefine Build-to-Run requirements and support production readiness, operational handover and knowledge transfer. /li /ul h3Architecture practices /h3 pThe architect must be comfortable with structured architecture practices, including: /p ul liArchiMate /li liTOGAF or equivalent architecture methodology /li liArchitecture principles and standards /li liArchitecture Decision Records /li liTarget-state architecture /li liImpact and dependency analysis /li liArchitecture governance /li /ul h3Technical scope /h3 h3Infrastructure Network /h3 h3Strong Expertise In /h3 ul liLAN/WAN, routing, switching, VLANs and subnets /li liNetwork segmentation, firewalls, DMZs and security zoning /li liWi-Fi and site/datacenter connectivity /li liCompute and virtualization /li liWindows/Linux infrastructure foundations /li liStorage, backup and recovery /li liHigh availability and disaster recovery /li liHybrid infrastructure and resilience /li /ul h3Cloud Hybrid /h3 h3Good Working Knowledge Of AWS Architecture And Networking, Including /h3 ul liVPC, subnets and route tables /li liInternet / NAT Gateway /li liTransit Gateway and VPC Peering /li liPrivateLink /li liSecurity Groups and Network ACLs /li liRoute 53 /li liAWS Direct Connect /li /ul h3API Integration /h3 pSufficient understanding of modern integration patterns to assess their infrastructure, network and security implications, including: /p ul liREST API