Technical Infrastructure

pJoining KEYES means giving purpose to your talent. /p pAre you looking for an environment where technology is not an end in itself, but a lever to build a sustainable future? At bKEYES /b, we are not just looking for technical expertise; we are looking for people who share our values. /p pDo you want to continue your career and grow within one of Belgium’s leading IT companies? /p pJoin bKEYES /b as a Technical Infrastructure Network Architect /p pbKEYES /b 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. /p pWe 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. /p pMore 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 lipTranslate business, application and solution requirements into technical architecture requirements covering hosting, connectivity, performance, availability, security, resilience, backup/recovery, monitoring and supportability. /p /li lipDefine target and reference architectures, reusable standards and technical patterns across sites. /p /li lipProduce HLDs and architecture documentation, and review LLDs and detailed technical designs. /p /li lipAnalyse impacts, dependencies, risks, architecture gaps, single points of failure and operational constraints. /p /li lipChallenge solutions proposed by projects, suppliers and engineering teams and assess alternative options. /p /li lipDocument key architecture decisions through Architecture Decision Records (ADRs). /p /li lipAssess deviations from architecture and technical standards and support the relevant governance and approval processes. /p /li lipDefine Build-to-Run requirements and support production readiness, operational handover and knowledge transfer. /p /li /ul h3Architecture practices /h3 pThe architect must be comfortable with structured architecture practices, including: /p ul lipArchiMate /p /li lipTOGAF or equivalent architecture methodology /p /li lipArchitecture principles and standards /p /li lipArchitecture Decision Records /p /li lipTarget-state architecture /p /li lipImpact and dependency analysis /p /li lipArchitecture governance /p /li /ul pThe architect must be capable of producing clear, concise and actionable HLDs, architecture diagrams, technical requirements and decision records. /p h3Technical scope /h3 h3Infrastructure Network /h3 pStrong expertise in: /p ul lipLAN/WAN, routing, switching, VLANs and subnets /p /li lipNetwork segmentation, firewalls, DMZs and security zoning /p /li lipWi-Fi and site/datacenter connectivity /p /li lipCompute and virtualization /p /li lipWindows/Linux infrastructure foundations /p /li lipStorage, backup and recovery /p /li lipHigh availability and disaster recovery /p /li lipHybrid infrastructure and resilience /p /li /ul h3Cloud Hybrid /h3 pGood working knowledge of AWS architecture and networking, including: /p ul lipVPC, subnets and route tables /p /li lipInternet / NAT Gateway /p /li lipTransit Gateway and VPC Peering /p /li lipPrivateLink /p /li lipSecurity Groups and Network ACLs /p /li lipRoute 53 /p /li lipAWS Direct Connect /p /li /ul pThe architect must be able to understand AWS Landing Zone constraint