Senior Resiliency Engineer-2

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove Exempt Status? That's metadata; maybe fold into short p or drop. Workplace Type info: we can include maybe as a short p under About the role? But we need to decide sections. We have description: "We are currently seeking a seasoned Senior Resiliency Architect/Engineer to support an expanding and maturing its enterprise resiliency program. This individual will play a critical role in helping design, evaluate, and enhance resilient technology solutions across the organization. The ideal candidate will possess deep technical expertise, a strong understanding of the software development lifecycle, and the ability to think strategically about how systems are designed, built, deployed, and maintained." That's about the role. Could be About the role section. Responsibilities: list bullet points. Basic Qualifications: list bullet points? It says Basic Qualifications: Bachelor's Degree, A minimum of 10 years of related experience in either Software Development (Java, Terraform), Resiliency, Application and/or Data Architecture and API based architectures, or other related skills. Preferred Competencies: list bullet points. Additional Skills: list bullet points. Compensation Range: we have Pay section: $93,000 - $189,000 USD Annual. Also mention incentive compensation plan and benefits. Benefits: list: health insurance coverage, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO). Workplace Type: Office, flexible work arrangement description. Could be included under About the role or maybe a separate section? There's no explicit heading for Workplace Type in the list of allowed headings; but we could fold into About the role as prose. Schedule: Not specified; we should not create Schedule section unless posting actually states them. It does not mention schedule, so omit. Pay: we have compensation range, so include Pay section. Benefits: we have benefits, include Benefits section. Requirements vs Qualifications: The posting has Basic Qualifications and Preferred Competencies and Additional Skills. We could map Basic Qualifications to Requirements, Preferred Competencies to Qualifications, Additional Skills to Skills. Or we could combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which to include based on content. We have: - About the role: description paragraph. - Responsibilities: list. - Requirements: Basic Qualifications (Bachelor's degree, 10 years experience). - Qualifications: Preferred Competencies (list). - Skills: Additional Skills (list). - Benefits: list. - Pay: compensation range. We should not include Schedule. We must not repeat job title. Must not include Exempt Status etc. Could fold Exempt Status into a short p maybe under About the role? But it's minor metadata; we could drop it as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Exempt Status is minor metadata; we could drop it or include as short p. Probably drop to keep concise. Workplace Type: also minor metadata; could fold into About the role as a short p. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given, not summarizing. Must not omit any substantive detail. So we need to include each bullet point from Responsibilities, Basic Qualifications, Preferred Competencies, Additional Skills, Benefits, Pay. We must not add any extra content not in posting. We must not include boilerplate like "Huntington is an Equal Opportunity Employer." etc. Remove those lines. We must not include duplicated lines. Let's extract the content. Description paragraph: "We are currently seeking a seasoned Senior Resiliency Architect/Engineer to support an expanding and maturing its enterprise resiliency program. This individual will play a critical role in helping design, evaluate, and enhance resilient technology solutions across the organization. The ideal candidate will possess deep technical expertise, a strong understanding of the software development lifecycle, and the ability to think strategically about how systems are designed, built, deployed, and maintained." Note: there is a grammatical error "expanding and maturing its" but we keep as is. Responsibilities bullet list: - Partner with engineering, architecture, infrastructure, and business teams to strengthen enterprise resiliency capabilities. - Evaluate existing applications and platforms for resiliency, recoverability, and operational readiness. - Provide architectural guidance across the full software development lifecycle, including requirements analysis, solution design, development, testing, deployment, and production support. - Assess and recommend approaches for backup, recovery, restoration, and disaster recovery processes. - Identify resiliency gaps and develop strategic roadmaps for improvement. - Contribute to cloud and infrastructure architecture decisions with a focus on reliability and recoverability. - Support the implementation of resilient application and data architecture across distributed environments. - Collaborate with development teams to ensure resiliency considerations are embedded into software delivery practices and establish appropriate governance and controls to mitigate risks related to application vulnerabilities, performance, and overall system resiliency. Basic Qualifications: - Bachelor's Degree - A minimum of 10 years of related experience in either Software Development (Java, Terraform), Resiliency, Application and/or Data Architecture and API based architectures, or other related skills. Preferred Competencies (list): - Proven experience as an Architect, Principal Engineer, Lead Engineer, or similar senior technical role. - Strong understanding of the complete software development lifecycle (SDLC), including gathering requirements, architecture and design, coding, testing, deployment, and production operations. - Hands-on experience developing applications using Java and containerized via delivery pipeline. - Experience with Terraform and infrastructure-as-code practices. - Experience working with cloud platforms such as AWS or GCP. - Strong understanding of relational databases and data modeling concepts. - Understanding of NoSQL technologies and distributed data architectures. - Knowledge of structured and unstructured data and the considerations for each. - Ability to evaluate technology solutions from both a strategic and technical perspective. - Knowledge of resilient API-based integration architectures, including RESTful services, microservices communication patterns, throttling, retry mechanisms, and secure API management across distributed environments. - Experience with application performance monitoring (APM) and observability platforms (e.g., Dynatrace, Datadog), including telemetry, distributed tracing, and centralized logging to support proactive monitoring, incident response, and system resiliency. Additional Skills: - Previous experience supporting enterprise resiliency, ransomware recovery, or business continuity program. - Experience working within the banking or financial services industry. - Understanding of backup and recovery strategies, including data restoration and recovery testing processes. - Familiarity with application recovery, infrastructure recovery, and operational resiliency best practices. - Experience working in complex, highly regulated environments. - Familiarity with Generative AI to improve system resiliency and operations, including intelligent automation, incident analysis, and knowledge-driven support solutions. Benefits: - health insurance coverage - wellness program - life and disability insurance - retirement savings plan - paid leave programs - paid holidays and paid time off (PTO) Pay: - Compensation Range $93,000.00 - $189,000.00 USD Annual - The compensation range represents the anticipated low and high end of the base compensation range for this position. Actual compensation will vary based on various factors including but not limited to location, experience, and education. - Colleagues in this position are also eligible to participate in an applicable incentive compensation plan. We should keep the sentences as is, maybe as

for prose and

• for lists. We need to decide which content goes into which section. About the role: include the description paragraph plus maybe workplace type? We could add a short p about workplace type: "Workplace Type: Office. Our approach enables flexible work arrangement..." but that's from the posting. It's substantive? It's about workplace type. It's not boilerplate. It's specific content. We could include it in About the role as a paragraph. But we must not invent or summarize away detail. So we need to include that info exactly. Let's extract that part: "Exempt Status: (Yes = not eligible for overtime pay) (No = eligible for overtime pay) Yes Workplace Type Office Our Approach to Office Workplace Type Certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team." We need to decide whether to keep Exempt Status. It's metadata but maybe we can drop as minor. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Exempt Status is minor metadata; we could drop it. Workplace Type description is more substantive; we could keep as a short p. Thus About the role section could have two paragraphs: the description paragraph and the workplace type paragraph. But we must not repeat the job title as a heading. Already not. Now Responsibilities: we have list. Requirements: Basic Qualifications (two bullet points). We'll put as

  • . Qualifications: Preferred Competencies (list). Skills: Additional Skills (list). Benefits: list. Pay: we have compensation range and incentive plan note. Could be a

    with the range and then another

    for incentive plan. Or combine. We must not include Schedule. Now ensure we don't include any boilerplate like "Huntington is an Equal Opportunity Employer." etc. Remove those lines. Also remove "Note to Agency Recruiters:" etc. Now produce HTML fragment. Let's craft. We'll start with maybe not required; just headings and content. We'll use

    for each section heading. We'll output:

    About the role

    We are currently seeking a seasoned Senior Resiliency Architect/Engineer to support an expanding and maturing its enterprise resiliency program. This individual will play a critical role in helping design, evaluate, and enhance resilient technology solutions across the organization. The ideal candidate will possess deep technical expertise, a strong understanding of the software development lifecycle, and the ability to think strategically about how systems are designed, built, deployed, and maintained.

    Workplace Type: Office. Our approach enables flexible work arrangement: certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team.

    But we need to preserve exact wording; we must not paraphrase. The original text: "Workplace Type Office Our Approach to Office Workplace Type Certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team." We need to keep that exactly. However there is a missing punctuation; we should keep as is. Let's copy exactly: "Workplace Type Office Our Approach to Office Workplace Type Certain positions outside our branch network may be eligible for a flexible