Infrastructure Architect, Infrastructure Operations & Development

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions (like apply by date, contact info, etc). Keep substantive info. Let's parse content: - Intro: "Shape resilient global IT infrastructure and security Are you motivated by designing and developing modern IT infrastructure in a global organisation? As Lead Architect, Infrastructure & Operations, you will play a key role in ensuring secure, resilient and scalable infrastructure services across NKT’s international footprint. Working across network architecture, cloud services, cybersecurity and datacentre environments, this is an opportunity to contribute to the green transition while supporting business-critical operations. Do you want to help shape the future infrastructure landscape of a global company?" This is about the role. Could be "About the role". - Then: "Design secure and resilient global infrastructure solutions As Lead Architect, Infrastructure & Operations, you will be responsible for the architecture and development of NKT’s global IT infrastructure environment, including LAN/WLAN, WAN, datacentres, cybersecurity protection tools and cloud IaaS/PaaS services. You will collaborate with IT leadership, project managers, cybersecurity teams and business stakeholders to ensure solutions align with business requirements, security standards and long-term technology plans. The role combines strategic architectural work with hands-on involvement when required, ensuring robust and reliable infrastructure operations across the organisation." This is responsibilities. - Then bullet list: "Your Responsibility Will Be To Develop and maintain infrastructure technology roadmapsDesign secure, scalable and resilient infrastructure solutionsCoordinate implementations, transitions and infrastructure improvementsParticipate in risk management activities and support mitigation actionsProduce and maintain architectural documentation and technical designs". Actually it's a list but missing commas. We'll treat each as list item. - Then: "The role reports to the VP, Infrastructure & Operations, Group IT. The position can be based in Kaunas or Kladno/Prague and includes approximately 10-20 travel days per year." This could be schedule? Travel days maybe schedule. But schedule section only if posting actually states schedule. It says includes approx 10-20 travel days per year. That's schedule info. Could be placed under Schedule heading. - Then: "Collaborative architect with a structured approach You enjoy working across teams and building constructive relationships with both technical and business stakeholders. You approach challenges in a structured and analytical way and communicate clearly using facts and data. As a person, you are proactive, organised and comfortable working within complex international environments. You value collaboration and are committed to delivering reliable solutions that balance business needs, operational requirements and security considerations." This is skills/qualities. - Then: "You Also Have Relevant academic degree in Business, Engineering or a related fieldCISSP certificationITIL Foundation, ISO 27001 or similar certification5-10 years of experience within IT infrastructure technologies and securityDeep understanding of network architecture, firewall implementation and security architecturePrince2 or similar project management certification (preferred)". This is qualifications/requirements. - Then: "For Kaunas applicants the compensation range for this position is 5.000EUR to 8.000EUR." That's pay. Note formatting: 5.000EUR (likely 5,000 EUR). We'll keep as is. - Then: "Build the digital foundation for a greener future We aim to create a workplace where people of all backgrounds are valued, supported, and able to do their best work. We are dedicated to increasing gender diversity at NKT and welcome applications from a wide range of candidates. We welcome varied backgrounds and career paths—even if you don’t meet every single requirement. We believe inclusive teams contribute to positive results and create a better everyday work environment. This position offers the opportunity to work with modern infrastructure technologies across a global organisation and contribute to the ongoing development of NKT’s IT landscape. You will collaborate with experienced colleagues across multiple countries, expand your professional capabilities in an international setting, and contribute to technology initiatives that support both business development and the green transition. “As a leader, I value people who combine a structured approach with curiosity and collaboration. In this role, you will have the opportunity to work across a complex global IT environment and contribute to infrastructure solutions that support our business and long-term ambitions,” says Hiring Manager, Bo Rydicher. Read more about our offer and listen to some voices of NKT Connectors here! We will review applications continuously, but we recommend you apply no later than the 11th of October of 2026. Be aware that personality and cognitive tests might be included in the recruitment process. If you have any questions about the role, you are very welcome to contact Hiring Manager Bo Rydicher bo.rydicher@nkt.com. For inquiries about the recruitment process, please reach out to Global HR Business Partner, Morten Sponholtz at morten.sponholtz@nkt.com. Please note that due to the GDPR regulations we cannot accept any applications via e-mail. We collect confidential candidate experience feedback to improve our recruitment process. Your responses are for quality development only and do not affect hiring decisions. Be a Connector of the green tomorrow! About NKT NKT connects a greener world with high-quality power cable technology and takes centre stage as the world moves towards green energy. NKT designs, manufactures and installs low-, medium- and high-voltage power cable solutions enabling sustainable energy transmission. Since 1891, NKT has innovated the power cable technology building the infrastructure for the first light bulbs to the megawatts created by renewable energy today. NKT is headquartered in Denmark and employs 6,500 people. NKT is listed on Nasdaq Copenhagen and realised a revenue of EUR 3.6 billion in 2025. We connect a greener world. www.nkt.com" We need to remove boilerplate: EEO, legal, application instructions, contact info, etc. So we should strip out: - "We will review applications continuously, but we recommend you apply no later than the 11th of October of 2026." (application instruction) - "Be aware that personality and cognitive tests might be included in the recruitment process." (maybe keep? It's part of process but could be considered boilerplate? It's not EEO but still process. Might be considered application instruction; safer to remove.) - Contact info lines: "If you have any questions about the role, you are very welcome to contact Hiring Manager Bo Rydicher bo.rydicher@nkt.com." etc. Remove. - "Please note that due to the GDPR regulations we cannot accept any applications via e-mail." Remove. - "We collect confidential candidate experience feedback to improve our recruitment process. Your responses are for quality development only and do not affect hiring decisions." Remove. - "Be a Connector of the green tomorrow!" maybe keep as tagline? It's marketing but not boilerplate; could keep as part of About NKT? Might be okay but it's a slogan. Probably fine to keep as part of About NKT section? But we have separate About NKT later. - The "About NKT" paragraph is substantive about company; we could include as a section maybe "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we may incorporate company info into About the role or maybe omit. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. We can include company info under About the role perhaps. - Also "Read more about our offer and listen to some voices of NKT Connectors here!" is promotional; could be omitted. - The quote from hiring manager: could be kept as part of About the role or maybe Skills? It's a quote about leadership; could be part of About the role. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details like responsibilities list, qualifications, pay range, travel days, location options, etc. We must not create sections with filler like "commensurate with experience". We have actual pay range, so we can create Pay section. Schedule: we have travel days approx 10-20 per year. That's schedule info. So we can create Schedule section. Benefits: not mentioned explicitly besides maybe "opportunity to work with modern infrastructure technologies", "contribute to green transition", "collaborate with experienced colleagues", "expand professional capabilities". Those are more like benefits but not explicit benefits like health insurance, pension, etc. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits: there is no explicit benefits like health, pension, etc. So we should not create Benefits section. Skills: we have collaborative architect with structured approach, proactive, organised, etc. That's skills/qualities. So we can create Skills section. Requirements vs Qualifications: The posting lists "You Also Have Relevant academic degree..." etc. That's qualifications. Could be under Requirements or Qualifications. We have both headings allowed. We need to decide which to use. The posting includes both "Requirements" and "Qualifications" maybe overlapping. We can combine into one section, maybe "Requirements". Or we could have both if we have distinct content. Let's see: The earlier bullet list under "Your Responsibility Will Be To" is responsibilities. Then later "You Also Have" list is qualifications. There's also earlier "Collaborative architect with a structured approach ..." which is skills/attributes. So we can have sections: Responsibilities, Requirements (or Qualifications), Skills, Pay, Schedule, About the role. We must not repeat job title as heading. So we avoid heading that duplicates title. We need to output only HTML fragment, no /, no markdown. Let's draft:

About the role

Shape resilient global IT infrastructure and security. As Lead Architect, Infrastructure & Operations, you will play a key role in ensuring secure, resilient and scalable infrastructure services across NKT’s international footprint, working across network architecture, cloud services, cybersecurity and datacentre environments. This is an opportunity to contribute to the green transition while supporting business‑critical operations. You will help shape the future infrastructure landscape of a global company.

Design secure and resilient global infrastructure solutions. As Lead Architect, Infrastructure & Operations, you will be responsible for the architecture and development of NKT’s global IT infrastructure environment, including LAN/WLAN, WAN, datacentres, cybersecurity protection tools and cloud IaaS/PaaS services. You will collaborate with IT leadership, project managers, cybersecurity teams and business stakeholders to ensure solutions align with business requirements, security standards and long‑term technology plans. The role combines strategic architectural work with hands‑on involvement when required, ensuring robust and reliable infrastructure operations across the organisation. The role reports to the VP, Infrastructure & Operations, Group IT. The position can be based in Kaunas or Kladno/Prague and includes approximately 10‑20 travel days per year.

As a leader, I value people who combine a structured approach with curiosity and collaboration. In this role, you will have the opportunity to work across a complex global IT environment and contribute to infrastructure solutions that support our business and long‑term ambitions.

But we need to avoid duplication; maybe keep concise. Better to separate About the role (general description) and then Responsibilities list. Let's extract responsibilities list items: - Develop and maintain infrastructure technology roadmaps - Design secure, scalable and resilient infrastructure solutions - Coordinate implementations, transitions and infrastructure improvements - Participate in risk management activities and support mitigation actions - Produce and maintain architectural documentation and technical designs We'll put those in

• . Now Skills section: from "Collaborative architect with a structured approach ..." paragraph. We can extract: - Enjoy working across