VP, Head of Cloud Solutions

We need to output HTML fragment with sections: About the role? Actually we have sections: Job Summary (but we shouldn't repeat job title). We need to include headings for sections present: About the role? The posting includes "Job Summary" which is like overview. Could treat as "About the role". Also "Responsibilities", "Knowledge, Skills, And Abilities", "Education, Training, And Experience", "About Community Federal Savings Bank (CFSB)". Also maybe "Pay, Schedule, Benefits" not present, so omit. We must not include boilerplate like EEO etc. Remove equal opportunity line. Also remove "Applicants must be permanently authorized..." that's a requirement; we should keep that as part of Requirements? It is a requirement about work authorization. Could be placed under Requirements or maybe under Knowledge, Skills... but better to put under Requirements (though we don't have a separate Requirements heading; we have Knowledge, Skills, And Abilities and Education, Training, And Experience). The work authorization could be part of Knowledge, Skills, And Abilities? Might be better to create a "Requirements" section if we have content. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Requirements if we have content. The posting includes work authorization requirement and hybrid/remote location details. Those could go under Requirements or maybe under About the role. Let's treat them as Requirements. We also have "About Community Federal Savings Bank (CFSB)" as About the company; could be under "About the role"? Actually "About the role" is for role description; we have Job Summary which is about role. So we can use "About the role" heading for the Job Summary paragraph(s). Then "About Community Federal Savings Bank (CFSB)" could be under "About the company" but not in list; maybe we can omit or put under "About the role"? Better to keep as separate section "About the company" but not in allowed headings list; but we could still use

with any heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we can use other headings if needed? Safer to stick to those. We could incorporate company info into "About the role" or maybe under a separate "About the company" but risk deviating. I'd include it under "About the role" as additional paragraph. We must not repeat job title. No Job ID. We must preserve all substantive information. So we need to include all bullet points from Responsibilities, Knowledge, Skills..., Education..., etc. We need to use

• for any list of duties/requirements/benefits. So each bullet list becomes
  • . For prose, use

    . We must not include filler like "commensurate with experience". Not present. We need to exclude boilerplate: EEO line, maybe also "We are an equal opportunity employer...". Remove. Also remove "This role is hybrid (2x per week) for those located in the NYC Metro Area, or fully-remote in 23 select states*". That's substantive (schedule/location). Since we don't have Schedule section unless posting states schedule; it does state hybrid/remote. So we should include a Schedule section. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can create Schedule section with that info. Similarly, Benefits not stated, so omit. Pay not stated, omit. Thus sections: About the role (Job Summary), Responsibilities, Requirements (work auth + location?), Knowledge, Skills, And Abilities, Education, Training, And Experience, Schedule (hybrid/remote), About the company (CFSB). But About the company may not be in allowed headings; maybe we can put under "About the role" as a paragraph. However the instruction: "Prefer a few substantive sections over many thin ones." Could combine company info into About the role. But we also have "About Community Federal Savings Bank (CFSB)" which is a description of the company. Could be considered "About the company". Not in list but maybe acceptable. I'd include as a separate section "About the company" using

    . The instruction didn't forbid other headings, just gave examples. It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use other headings as long as they are

    . I'll include About the company. Now we need to ensure we don't include duplicated lines. Remove any duplicate sentences. Let's extract content. Job Summary paragraph(s): "We are seeking a senior technology leader to own CFSB's cloud strategy, platform engineering, and cloud operating model. Reporting to the [CIO/CTO], this role owns the multi-year cloud roadmap and leads the team that builds and runs the bank's cloud platform — the landing zones, automation, networking, and controls that every other technology team builds on. This is a hands-on leadership role in a regulated environment. You should be equally comfortable presenting a cloud investment case to executive leadership, reviewing an infrastructure-as-code pull request with an engineer, and explaining to an examiner how cloud controls are designed and evidenced. We expect recommendations and tradeoffs, not problems to be assigned. The role manages five to eight cloud engineers and partners closely with Information Security, Risk, Compliance, Enterprise Architecture, and the product squads. You are the accountable technology owner for how security and regulatory requirements are implemented and evidenced in the cloud. The team participates in a shared on-call rotation and provides after-hours support to the business; this role serves as its senior escalation point." That's the summary. Now Responsibilities (multiple bullet points). Let's list them: - Cloud Strategy and Roadmap - Own and maintain the multi-year cloud strategy and migration roadmap, sequenced against business priorities, risk appetite, and budget cycles. - Translate strategy into executive-ready business cases and committee-level materials, and secure funding and alignment for cloud investments. - Set cloud target architecture and standards with Enterprise Architecture — reference patterns, approved services, and guardrails for what teams may build. - Define and report program metrics — migration progress, platform reliability, control coverage, and unit cost trends — and advise leaders on build-versus-buy and cloud-versus-on-premises decisions. - Platform and Infrastructure Engineering - Lead the design, build, and operation of the cloud platform: multi-account landing zones, identity and access, network architecture and hybrid connectivity, observability, backup, and resilience. - Establish infrastructure-as-code and pipeline-based delivery as the default provisioning mechanism, and eliminate manual, undocumented change. - Own the cloud CI/CD, container, and DevOps tooling that squads consume, and enforce engineering standards for code review, environment promotion, change management, and documentation. - Ensure environments meet availability and recovery objectives; lead resilience testing and serve as senior escalation point for major incidents through to permanent corrective action. - Cloud Security, Risk, and Regulatory Compliance - Own the implementation and evidencing of cloud technical controls that satisfy policies and standards set by Information Security, Risk, and Compliance, and escalate gaps where cloud reality and policy diverge. - Serve as the cloud subject matter expert in internal audit, external audit, and regulatory examinations, including FFIEC and GLBA obligations, and produce control evidence and remediation plans. - Embed guardrails as code — configuration baselines, encryption and key management, privileged access controls, and continuous compliance monitoring — and remediate findings and drift to agreed timelines. - Contribute cloud expertise to risk assessments, third-party technology reviews, and change and exception review boards; provide input to cloud policies as a reviewer, with ownership, approval, and risk acceptance resting with the second-line functions. - Cost Management and Vendor Relationship - Own the cloud budget: forecast spend, cost savings plan, and explain variances to Finance and the [CIO/CTO]. - Manage the AWS relationship, including account team engagement, support tier decisions, and technical escalation; provide technical input to procurement and renewals, with commercial negotiation led by Procurement and Vendor Management. - Leadership and Team Development - Recruit, develop, and retain cloud engineers; set goals, coach, conduct performance reviews, and create clear technical development paths so no critical capability rests on a single person. - Balance squad-embedded assignments against core platform work as priorities shift, and represent cloud engineering in technology leadership forums. Now Knowledge, Skills, And Abilities (two sub-sections: Technical and Professional). Let's list bullet points: Technical: - Deep hands-on AWS expertise across IAM, networking, compute, storage, database, and cost management. - Strong cloud networking: VPC and subnet design, Transit Gateway, CloudWAN, segmentation, and hybrid connectivity. - Proven infrastructure-as-code experience, Terraform preferred — modules, state, and refactoring into code. - Experience with Git-based workflows, CI/CD, and container platforms such as ECS or EKS at production scale. - Cloud security and multi-account governance: least-privilege IAM, encryption, secrets, and Control Tower. - Capable of leading complex, multi-step, large scale infrastructure related activities like data-center exit migrations, VPN cutovers, Database migrations, among others. Professional: - Sound judgment under constraint, balancing delivery speed against risk, cost, and regulatory obligation. - Technical credibility with engineers and fluency in front of executives, auditors, and examiners. - Succeeds through Security, Risk, and delivery teams, with a strong hiring and development record. - Proven track record leading teams towards successful and timely execution of commitments to executive leadership and board of directors. Now Education, Training, And Experience: - Bachelor's degree in Information Technology, Computer Science, or equivalent experience. - 10+ years in technology infrastructure, platform, or cloud engineering, including 3+ years leading technical teams. - Demonstrated ownership of a production cloud environment at enterprise scale, not solely advisory, architecture-only, or program-management exposure. - Experience in a regulated industry with formal audit, control, and change-management discipline, including direct support of audits or examinations; financial services experience and familiarity with FFIEC guidance and GLBA preferred. Now Requirements (work auth + location): - Applicants must be permanently authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of any temporary employment visa (e.g. OPT-STEM, H-1B, CPT, etc.) now or in the future. - This role is hybrid (2x per week) for those located in the NYC Metro Area, or fully-remote in 23 select states*. Now About Community Federal Savings Bank (CFSB): - Community Federal Savings Bank (CFSB) is a federally chartered bank founded in 2001 and headquartered in New York City. CFSB has focused on providing superior service and added value to clients though a solid understanding of relationship banking. We offer a full range of services, including loans, bill payments, card services, internet banking, and merchant processing. We should also keep the equal opportunity line? It's boilerplate; remove. Now we need to output HTML fragment with

    headings and

    or

    • . We'll structure:

      About the role

      Job summary paragraphs...

      Responsibilities

      • ... (maybe we need subheadings? But we can just list all bullet points as
      • . However we have categories; we could keep them as
      • with the category as part of text. That's fine. But we might want to keep readability: maybe include for category? Not required. We'll just list each bullet as
      • . Similarly for Knowledge, Skills, And Abilities: we can list each bullet. Education, Training, And Experience: list each. Requirements: list each. Schedule: we could put location/hybrid info