Sr.Manager, Information Security Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit boilerplate besides maybe the link to benefits portal; we can keep that as part of benefits.
We must include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Here we have salary range and benefits info, so we can include Pay and Benefits sections.
We need to decide which sections to include: About the role? Not present as heading but we have "Who We Are", "What It’s Like To Work Here", "What You’ll Do", "How You’ll Make An Impact", "What You Can Expect", "What You’ll Bring", "Leadership Expectations", "Success Measures". Also maybe "Benefits" and "Pay". Also maybe "Schedule"? Not mentioned except remote days allocation; could be part of Benefits or maybe "Work Schedule". But we should not create Schedule unless posting actually states schedule details. It mentions collaborative, in-office operating model, remote days allocation. That's about work arrangement, not schedule. Could be part of "What It’s Like To Work Here". We'll keep that in that section.
We must not repeat job title. So no heading for Senior Manager, Information Security Engineering.
We need to output only HTML fragment.
Let's structure:
Who We Are
... content ...
What It’s Like To Work Here
... content ... maybe include bullet list for benefits? Actually benefits list is separate: Retirement program (401k and Pension), Medical, dental and vision insurance, Lifestyle Spending Account, Competitive PTO plan, 11 paid holidays per year. Also collaborative, in-office operating model, remote days allocation. Could be part of this section as bullet list.
But we also have a Benefits section maybe separate. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine benefits into What It’s Like To Work Here. But we also have Salary Range separate; we could make Pay section.
We need to include all substantive info. Let's decide sections:
- Who We Are
- What It’s Like To Work Here (includes work model, benefits, remote days)
- What You’ll Do
- How You’ll Make An Impact
- What You Can Expect
- What You’ll Bring
- Leadership Expectations
- Success Measures
- Pay (Salary Range)
- Benefits (maybe separate if we didn't include earlier). But we already included benefits in What It’s Like To Work Here; but we might still need a Benefits section if we want to follow typical headings. However we must not create sections with filler. If we already covered benefits in What It’s Like To Work Here, we could omit a separate Benefits section. But the instruction: "Prefer a few substantive sections over many thin ones." So combining is okay.
But we also have "Retirement program (401k and Pension)" etc. Those are benefits. So we can put them under What It’s Like To Work Here as a list.
We also have "collaborative, in-office operating model" and "remote days allocation". Could be bullet points.
Thus What It’s Like To Work Here will have a paragraph describing culture, buddy program, professional development, etc., plus a bullet list of benefits and work arrangement.
Now we need to ensure we don't repeat any content inadvertently.
Let's extract the relevant prose:
Who We Are:
"Our mission at FHLBank Chicago: To partner with our members in Illinois and Wisconsin to provide them competitively priced funding, a reasonable return on their investment, and support for their community investment activities. Simply said, we're a bank for banks and other financial institutions, focused on being a strategic partner for our members and working together to reinvest in our communities, from urban centers to rural areas. Created by Congress in 1932, FHLBank Chicago is one of 11 Federal Home Loan Banks, government sponsored in support of mortgage lending and community investment."
What It’s Like To Work Here:
"At FHLBank Chicago, we bring people together. We are committed to a high performing, engaged workforce, and to supporting the communities we serve across Illinois and Wisconsin. Our Buddy Program pairs new hires with tenured employees to guide their onboarding. Our professional development and training opportunities through upskilling, mentorship programs, and tuition reimbursement allow employees to grow their career with us. Our collaborative, in-office operating model brings teams together to foster innovation, connection, and shared success. To support balance and flexibility, employees are provided an allocation of remote days to use as needed throughout the year."
Then benefits list: Retirement program (401k and Pension), Medical, dental and vision insurance, Lifestyle Spending Account, Competitive PTO plan, 11 paid holidays per year.
We could incorporate that list after the paragraph.
What You’ll Do:
"The Senior Manager, Information Security Engineering leads the design, engineering, implementation, and lifecycle management of technical security controls that protect the Bank’s systems, identities, applications, data, cloud services, and customer-facing capabilities. The role reports to the Chief Information Security Officer, and manages a blended team of employees and contractors, establishes engineering priorities and standards, and translates security requirements into scalable, supportable, and measurable technology solutions. The position aligns the security tool portfolio and engineering roadmap to the NIST Cybersecurity Framework (CSF), Bank policy, risk appetite, architecture standards, and applicable regulatory expectations."
How You’ll Make An Impact:
List of bullet points (multiple sentences). We'll need to convert each sentence into
- items.
What You Can Expect:
Paragraph: "Lead, coach, and develop security engineering employees and contractors. Set clear objectives, allocate work, manage capacity, provide feedback, support performance and career development, and promote an inclusive, accountable, and collaborative culture.Own the security engineering strategy, operating model, multi-year roadmap, backlog, budget inputs, workforce plan, vendor relationships, and delivery commitments. Balance strategic initiatives, control maintenance, technical debt, and urgent risk reduction.Align security engineering capabilities, tools, and technical controls to the NIST CSF functions and categories. Maintain traceability from risks and requirements to control design, implementation, evidence, ownership, and measurement. Partner with Security Architecture, Security Operations, Threat and Incident Response, Identity and Access Management, Security Advisory and Analytics, IT Risk and Compliance, Enterprise Architecture, Infrastructure, Cloud, Network, and Application teams to design and implement effective controls. Assist control owners and engineering teams with the development, documentation, implementation, testing, and continuous improvement of preventive, detective, responsive, and recovery-oriented technical controls. Provide engineering leadership for security technologies supporting endpoint and workload protection, identity and privileged access, cloud security, network security, security monitoring and logging, data protection, vulnerability management, application security, certificate and secrets management, email and collaboration security, and security automation.Direct security engineering for AWS and Microsoft Azure environments, including secure configuration baselines, native security services, identity and access controls, logging and monitoring, encryption and key management, network segmentation, workload protection, and automated policy enforcement. Establish standards for security tool selection, architecture, configuration, integration, lifecycle management, resilience, supportability, and decommissioning. Identify tool overlap, coverage gaps, operational dependencies, and opportunities for consolidation or automation. Define engineering quality practices, including peer review, change control, infrastructure as code, testing, documentation, secure configuration, release readiness, rollback planning, and handoff to operational support teams.Develop and maintain technical standards, baseline security configurations, reference architectures, procedures, engineering runbooks, control narratives, and evidence required for governance, risk, audit, and regulatory review.Develop meaningful metrics and dashboards that measure control coverage, control health and effectiveness, engineering delivery, reliability, automation, technical debt, risk reduction, and service performance. Use results to prioritize investment and drive continuous improvement. Provide concise reporting to security and technology leadership on roadmap progress, material risks, exceptions, dependencies, resource constraints, control performance, and recommended decisions. Support security incidents, investigations, vulnerability remediation, audit findings, risk acceptances, penetration testing, and threat-driven improvements by coordinating engineering analysis and sustainable corrective actions. Participate in technology planning and design reviews to ensure security requirements are incorporated early and implemented in a manner that supports business objectives and customer needs.Provide technical escalation and decision support for complex security control and tooling issues. Coordinate off-hours support when required for critical incidents or significant production changes. Perform other duties as assigned."
What You’ll Bring:
Paragraph with bullet list of qualifications.
Leadership Expectations:
Paragraph with bullet list.
Success Measures:
Paragraph with bullet list.
Pay:
Salary Range: "$151,025.00 - $265,525.00". Also note: "The above represents the expected salary range for this job requisition. Ultimately, in determining your pay, we may also consider your experience, and other job-related factors." Could be included in paragraph.
Benefits: Already covered.
We must not include application instructions or link to benefits portal? The link is part of benefits: "In addition to the base salary, we offer a comprehensive benefits package which can be found here: https://hrportal.ehr.com/fhlbc". That's substantive; we can keep as a sentence.
Now we need to format with
headings,
for prose,
- for lists.
We need to decide which content is list vs prose.
For "What You’ll Do": It's a paragraph; could be left as
.
For "How You’ll Make An Impact": multiple sentences each starting with a verb; could be list.
Similarly "What You Can Expect": many sentences; could be list.
"What You’ll Bring": list of qualifications.
"Leadership Expectations": list.
"Success Measures": list.
Benefits list: we already have bullet list.
Now we need to ensure we don't lose any detail.
Let's extract each piece precisely.
Who We Are paragraph: exactly as above.
What It’s Like To Work Here paragraph: we have two sentences? Actually it's: "At FHLBank Chicago, we bring people together. We are committed to a high performing, engaged workforce, and to supporting the communities we serve across Illinois and Wisconsin. Our Buddy Program pairs new hires with tenured employees to guide their onboarding. Our professional development and training opportunities through upskilling, mentorship programs, and tuition reimbursement allow employees to grow their career with us. Our collaborative, in-office operating model brings teams together to foster innovation, connection, and shared success. To support balance and flexibility, employees are provided an allocation of remote days to use as needed throughout the year."
We'll keep as paragraph.
Then benefits list: Retirement program (401k and Pension), Medical, dental and vision insurance, Lifestyle Spending Account, Competitive PTO plan, 11 paid holidays per year.
We'll make
- for each.
Now What You’ll Do paragraph: as above.
How You’ll Make An Impact: list items:
-
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit boilerplate besides maybe the link to benefits portal; we can keep that as part of benefits. We must include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Here we have salary range and benefits info, so we can include Pay and Benefits sections. We need to decide which sections to include: About the role? Not present as heading but we have "Who We Are", "What It’s Like To Work Here", "What You’ll Do", "How You’ll Make An Impact", "What You Can Expect", "What You’ll Bring", "Leadership Expectations", "Success Measures". Also maybe "Benefits" and "Pay". Also maybe "Schedule"? Not mentioned except remote days allocation; could be part of Benefits or maybe "Work Schedule". But we should not create Schedule unless posting actually states schedule details. It mentions collaborative, in-office operating model, remote days allocation. That's about work arrangement, not schedule. Could be part of "What It’s Like To Work Here". We'll keep that in that section. We must not repeat job title. So no heading for Senior Manager, Information Security Engineering. We need to output only HTML fragment. Let's structure:
Who We Are
... content ...
What It’s Like To Work Here
... content ... maybe include bullet list for benefits? Actually benefits list is separate: Retirement program (401k and Pension), Medical, dental and vision insurance, Lifestyle Spending Account, Competitive PTO plan, 11 paid holidays per year. Also collaborative, in-office operating model, remote days allocation. Could be part of this section as bullet list. But we also have a Benefits section maybe separate. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine benefits into What It’s Like To Work Here. But we also have Salary Range separate; we could make Pay section. We need to include all substantive info. Let's decide sections: - Who We Are - What It’s Like To Work Here (includes work model, benefits, remote days) - What You’ll Do - How You’ll Make An Impact - What You Can Expect - What You’ll Bring - Leadership Expectations - Success Measures - Pay (Salary Range) - Benefits (maybe separate if we didn't include earlier). But we already included benefits in What It’s Like To Work Here; but we might still need a Benefits section if we want to follow typical headings. However we must not create sections with filler. If we already covered benefits in What It’s Like To Work Here, we could omit a separate Benefits section. But the instruction: "Prefer a few substantive sections over many thin ones." So combining is okay. But we also have "Retirement program (401k and Pension)" etc. Those are benefits. So we can put them under What It’s Like To Work Here as a list. We also have "collaborative, in-office operating model" and "remote days allocation". Could be bullet points. Thus What It’s Like To Work Here will have a paragraph describing culture, buddy program, professional development, etc., plus a bullet list of benefits and work arrangement. Now we need to ensure we don't repeat any content inadvertently. Let's extract the relevant prose: Who We Are: "Our mission at FHLBank Chicago: To partner with our members in Illinois and Wisconsin to provide them competitively priced funding, a reasonable return on their investment, and support for their community investment activities. Simply said, we're a bank for banks and other financial institutions, focused on being a strategic partner for our members and working together to reinvest in our communities, from urban centers to rural areas. Created by Congress in 1932, FHLBank Chicago is one of 11 Federal Home Loan Banks, government sponsored in support of mortgage lending and community investment." What It’s Like To Work Here: "At FHLBank Chicago, we bring people together. We are committed to a high performing, engaged workforce, and to supporting the communities we serve across Illinois and Wisconsin. Our Buddy Program pairs new hires with tenured employees to guide their onboarding. Our professional development and training opportunities through upskilling, mentorship programs, and tuition reimbursement allow employees to grow their career with us. Our collaborative, in-office operating model brings teams together to foster innovation, connection, and shared success. To support balance and flexibility, employees are provided an allocation of remote days to use as needed throughout the year." Then benefits list: Retirement program (401k and Pension), Medical, dental and vision insurance, Lifestyle Spending Account, Competitive PTO plan, 11 paid holidays per year. We could incorporate that list after the paragraph. What You’ll Do: "The Senior Manager, Information Security Engineering leads the design, engineering, implementation, and lifecycle management of technical security controls that protect the Bank’s systems, identities, applications, data, cloud services, and customer-facing capabilities. The role reports to the Chief Information Security Officer, and manages a blended team of employees and contractors, establishes engineering priorities and standards, and translates security requirements into scalable, supportable, and measurable technology solutions. The position aligns the security tool portfolio and engineering roadmap to the NIST Cybersecurity Framework (CSF), Bank policy, risk appetite, architecture standards, and applicable regulatory expectations." How You’ll Make An Impact: List of bullet points (multiple sentences). We'll need to convert each sentence into
headings,
for prose,
- for lists.
We need to decide which content is list vs prose.
For "What You’ll Do": It's a paragraph; could be left as
. For "How You’ll Make An Impact": multiple sentences each starting with a verb; could be list. Similarly "What You Can Expect": many sentences; could be list. "What You’ll Bring": list of qualifications. "Leadership Expectations": list. "Success Measures": list. Benefits list: we already have bullet list. Now we need to ensure we don't lose any detail. Let's extract each piece precisely. Who We Are paragraph: exactly as above. What It’s Like To Work Here paragraph: we have two sentences? Actually it's: "At FHLBank Chicago, we bring people together. We are committed to a high performing, engaged workforce, and to supporting the communities we serve across Illinois and Wisconsin. Our Buddy Program pairs new hires with tenured employees to guide their onboarding. Our professional development and training opportunities through upskilling, mentorship programs, and tuition reimbursement allow employees to grow their career with us. Our collaborative, in-office operating model brings teams together to foster innovation, connection, and shared success. To support balance and flexibility, employees are provided an allocation of remote days to use as needed throughout the year." We'll keep as paragraph. Then benefits list: Retirement program (401k and Pension), Medical, dental and vision insurance, Lifestyle Spending Account, Competitive PTO plan, 11 paid holidays per year. We'll make
- for each. Now What You’ll Do paragraph: as above. How You’ll Make An Impact: list items: -