Senior Infrastructure, Security & Operations Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse description. Title: Senior Infrastructure, Security & Operations Architect Location: New Albany, Ohio Job Type: Full Time Then description paragraphs. We need sections: - About the role: maybe summary paragraph(s) describing role. - Responsibilities: bullet list of duties. - Requirements: maybe education/experience baseline. - Qualifications: maybe preferred qualifications. - Skills: maybe technical skills. - Benefits: maybe not present? The posting mentions employee-owned, mission, etc. Not explicit benefits like health insurance, 401k. Might not have specific benefits. So we should not include Benefits unless explicit. - Pay: not mentioned. - Schedule: maybe full time, on-call rotation, travel. Could include schedule info: full-time, on-call escalation rotation, travel regularly. That could be schedule. We need to preserve all substantive info, not invent. Let's extract. About the role: The first paragraphs after title: "Make a Difference—And Own Your Future Join Wallick, a 100% employee-owned company...". That's about company. Then "Position Summary Wallick is seeking a senior, hands-on architect to connect enterprise infrastructure, cybersecurity, and daily operations. You will shape the network linking our communities to the corporate office, the hybrid data center and cloud environment, the platforms and devices associates depend on, and the identity and security controls that keep the environment trusted. This is not a strategy-only position. You will design and engineer major changes, share the operational load, and turn solutions into standards and procedures others can execute. You will also serve as the senior technical voice across infrastructure and security, command major and cross-domain incidents, integrate both domains into one technical view, and communicate with senior leadership, auditors, and insurers alongside the Sr. Infrastructure Manager." That's good for About the role. How The Role Works: description of two-architect model, primary domain, backup coverage, senior individual contributor, on-call escalation rotation, travel regularly to communities. Could be part of Responsibilities or About. What You Will Do: list of duties: Own architecture, standards, roadmap; Design and deliver major change; Lead In Your Primary Domain (infrastructure or security focus); Operate, troubleshoot, strengthen the team; Senior-level scope (incident command, integrate domains, represent team, raise standards). That's responsibilities. What You Bring: education, experience, expertise, etc. That's qualifications/requirements. What Will Help You Stand Out: extra qualifications. The environment: location, travel, physical demands. Wallick’s Mission & Values: maybe not needed. Join Us and Become an Employee-Owner!: call to action, but we should remove application instructions? It says "apply today!" but that's application instruction; we should remove application instructions. Also "Employment is contingent upon passing a pre-employment background check and drug screen" maybe considered boilerplate? It's a condition but could be kept? It's not exactly boilerplate but it's a condition. Might be considered minor metadata; we could fold into a short p or drop. Probably drop as it's not substantive about role. We need to avoid duplication. Let's craft sections:

About the role

Wallick is a 100% employee‑owned company with over 55 years of experience providing affordable housing and assisted living across the Midwest. The Senior Infrastructure, Security & Operations Architect will connect enterprise infrastructure, cybersecurity, and daily operations, shaping the network linking Wallick communities to the corporate office, hybrid data center and cloud environment, the platforms and devices associates rely on, and the identity and security controls that keep the environment trusted. This hands‑on role designs and engineers major changes, shares operational load, turns solutions into standards and procedures, and serves as the senior technical voice across infrastructure and security, leading major and cross‑domain incidents and communicating with senior leadership, auditors, and insurers.

That captures.

Responsibilities

• Own architecture, standards, and roadmap for your primary domain (infrastructure or security), maintaining an accurate view of the environment, its connections, and condition.
• Create practical standards and reference patterns for firewalls, devices, platforms, identity, and security controls.
• Build and sequence a roadmap balancing business needs, risk, technical health, and team capacity.
• Design and engineer major initiatives such as Azure migration, hybrid environment strategy, edge network standardization across ~162 firewalls, identity and email security modernization, platform upgrades, and workload transitions.
• Take solutions from design through production readiness, then complete handoff with documentation, operating procedures, and training.
• Partner across IT to create secure‑by‑default patterns practical for Wallick’s environment.
• Operate, troubleshoot, and strengthen the team by carrying a meaningful share of daily infrastructure and security operations (changes, alert triage, access requests, control upkeep).
• Serve as the top escalation tier in your primary domain, lead incident response within that domain, and take command of major or cross‑domain incidents.
• Convert recurring work, escalations, and designs into procedures, patterns, recorded walkthroughs, and working sessions so responsibilities can move closer to the front line.
• Take command of major and cross‑domain incidents, leading the technical response end‑to‑end and coordinating with forensics partners, breach counsel, and cyber insurers alongside the Sr. Infrastructure Manager.
• Integrate the work of both architecture domains into one sequenced technical view that informs the broader IT roadmap.
• Represent the team's technical position to senior leadership, auditors, and insurers through concise briefings and candid risk assessments.
• Raise standards of practice through review discipline, mentoring, teaching, and example, without formal supervisory authority.
• Participate in the on‑call escalation rotation and travel regularly to Wallick communities for hands‑on work.

That covers many duties. Now Requirements/Qualifications/Skills. We have "What You Bring" includes: - Bachelor's degree in computer science, information systems, engineering, or related field, or equivalent practical experience. - A track record typically built over eight or more years across infrastructure and security engineering, including authored designs, implemented controls, modernization work, and end-to-end incident response. - Deep expertise in either infrastructure or security, plus working fluency in the other. - Experience owning a technology or security function, program, service line, or practice with accountability for outcomes, not only individual projects. - Incident command experience leading response end to end, including coordination with forensics partners, breach counsel, and cyber insurers. - Clear, candid communication with senior leadership, including concise briefings and direct descriptions of technical risk. - Experience with enterprise networking and firewalls at multi-site scale, hybrid data centers and virtualization, cloud platforms, and end-user computing, or enterprise identity, layered security controls, and hands-on incident response. - Fluency in Microsoft 365, Azure, Entra ID, Intune, and Microsoft Defender is strongly preferred. Sentinel and Purview experience is a plus. - Experience designing backup and recovery, conducting disaster recovery exercises, and testing recovery objectives. - Scripting and infrastructure-as-code capability using PowerShell, Bicep, Terraform, or similar tools. - Advanced troubleshooting skills and the judgment to remain calm and methodical during complex incidents. - Working knowledge of a recognized controls framework such as NIST CSF or CIS Controls, with the ability to size controls appropriately for a mid-size operator. - Clear technical writing and the ability to create designs, standards, diagrams, and procedures others can follow. - A valid driver's license and reliable transportation for regular travel to Wallick communities. That's a lot. We could split into Requirements (education, years experience) and Qualifications (deep expertise, owning function, incident command, communication) and Skills (technical fluency, scripting, troubleshooting, frameworks, writing, driver's license). But we need to avoid too many thin sections; prefer few substantive sections. We could combine Requirements and Qualifications into one section "Requirements & Qualifications". But the instruction says use headings for sections like Requirements, Qualifications, Skills. We can decide to include all three if they have substantive content. Let's see if we can make three sections: - Requirements: education, years experience, maybe degree. - Qualifications: deep expertise, owning function, incident command, communication, experience with networking/firewalls etc. - Skills: technical fluency (Microsoft stack), scripting, troubleshooting, frameworks, technical writing, driver's license. But there is overlap. However we can still do. We must not create sections with filler like "not specified". All content we have is specific. Let's extract. Requirements: - Bachelor's degree in computer science, information systems, engineering, or related field, or equivalent practical experience. - A track record typically built over eight or more years across infrastructure and security engineering, including authored designs, implemented controls, modernization work, and end-to-end incident response. That's it. Qualifications: - Deep expertise in either infrastructure or security, plus working fluency in the other. - Experience owning a technology or security function, program, service line, or practice with accountability for outcomes, not only individual projects. - Incident command experience leading response end to end, including coordination with forensics partners, breach counsel, and cyber insurers. - Clear, candid communication with senior leadership, including concise briefings and direct descriptions of technical risk. - Experience with enterprise networking and firewalls at multi-site scale, hybrid data centers and virtualization, cloud platforms, and end-user computing, or enterprise identity, layered security controls, and hands-on incident response. Skills: - Fluency in Microsoft 365, Azure, Entra ID, Intune, and Microsoft Defender (strongly preferred); Sentinel and Purview experience a plus. - Experience designing backup and recovery, conducting disaster recovery exercises, and testing recovery objectives. - Scripting and infrastructure-as-code capability using PowerShell, Bicep, Terraform, or similar tools. - Advanced troubleshooting skills and the judgment to remain calm and methodical during complex incidents. - Working knowledge of a recognized controls framework such as NIST CSF or CIS Controls, with the ability to size controls appropriately for a mid-size operator. - Clear technical writing and the ability to create designs, standards, diagrams, and procedures others can follow. - A valid driver's license and reliable transportation for regular travel to Wallick communities. Now Benefits: Not mentioned explicitly. There's mention of employee-owned, mission, values, but not benefits like health insurance, retirement. So we should not include Benefits. Pay: Not mentioned. Schedule: We have full-time, on-call escalation rotation, travel regularly. Could be schedule. We could include a Schedule section with that info. But we already included travel and on-call in Responsibilities. However schedule could be separate: full-time, on-call rotation, travel. We could add a Schedule section:

Schedule

Full‑time position with participation in an on‑call escalation rotation and regular travel to Wallick communities for hands‑on work.

That's specific. Now we need to ensure we don't duplicate content. We have travel mentioned in Responsibilities already; but it's okay to mention again in Schedule? Might be duplication but acceptable? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but we should avoid unnecessary duplication. However we could keep travel in Responsibilities and not repeat in Schedule; but schedule also includes full-time and on-call. On-call is also in Responsibilities. So maybe we should not duplicate. Instead we could put schedule info in Responsibilities? But we already have on-call and travel in Responsibilities. So maybe we don't need a separate Schedule section. However the instruction says include a section ONLY when posting has real specific content for it. It does not forbid duplication but better to avoid thin sections