Location: US, Florida, Hybrid
Company: City National Bank
The Lead Technology Resiliency Engineer is an information technology (IT)-based technical individual contributor who engineers and validates the availability, recoverability, and resilience of technology supporting critical banking services. The role translates approved business recovery time objectives (RTOs), recovery point objectives (RPOs), and service requirements into technical recovery designs, dependency sequencing, data protection, automated procedures, and measurable test outcomes. It leads assigned engineering improvements with IT owners while partnering with operational resilience and business continuity teams on business priorities and validation.
Job role:
Critical-service and technology dependency mapping
- Identify and maintain applications, infrastructure, data stores, integrations, identity services, networks, cloud platforms, hosting facilities, communications, support personnel, and third-party technology dependencies.
- Develop and validate business-to-technology dependency maps, upstream and downstream relationships, data flows, authentication and connectivity paths, recovery prerequisites, and sequencing.
- Define ServiceNow Configuration Management Database (CMDB) and Common Service Data Model (CSDM) resiliency data and relationship requirements; work with platform and data owners to validate accuracy and lifecycle maintenance.
Recovery objectives and technical feasibility
- Translate approved RTOs and RPOs into component-level requirements, recovery time budgets, data protection, and end-to-end sequencing; validate backup restoration, replication, database consistency, connectivity, and authentication.
- Measure achieved recovery times and recoverable data points in tests; document variances and coordinate corrective action with accountable IT owners.
- Document vendor commitments, integration constraints, escalation paths, and cloud or managed-service shared responsibilities; provide relevant findings to operational resilience and third-party risk teams.
- Escalate feasibility and capability gaps for prioritization and authorized risk disposition. Do not independently approve or revise business recovery objectives or disruption tolerances.
Resiliency engineering and failure analysis
- Assess service architecture for single points of failure, hidden dependencies, capacity constraints, and recovery gaps; perform failure-mode and impact analysis.
- Design and implement assigned redundancy, fault-tolerance, recovery automation, failover/failback, and graceful-degradation improvements with platform and application owners.
- Develop and technically validate runbooks, scripts, restoration prerequisites, orchestration procedures, recovery-environment capacity, and configuration consistency.
- Validate recovery approaches for outages, data corruption, and cyber-related disruption with cyber security and IT teams; recommend technical recovery triggers and actions under established incident procedures.
Monitoring and observability requirements
- Define telemetry, health and synthetic checks, capacity measures, service thresholds, alerts, and escalation triggers for critical technology dependencies.
- Identify coverage gaps and work with engineering and operations teams to implement and validate observability; accountable operations teams retain day-to-day monitoring.
Assessment, testing, and reporting
- Assess new or materially changed applications, cloud services, platforms, and integrations for availability, recoverability, supportability, and approved recovery objectives.
- Lead technical planning, execution coordination, and evidence for disaster recovery (DR), backup restoration, failover/failback, and integrated recovery tests; validate sequencing, achieved RTO/RPO, data integrity, and service functionality.
- Coordinate business validation with operational resilience and business continuity teams and business owners; document technical defects, coordinate assignment of corrective actions through established IT processes, and validate remediation through retesting.
- Maintain technical resiliency standards, recovery patterns, procedures, and metrics; report posture, dependency risk, gaps, remediation, and investment priorities, and support audit or regulatory requests.
Operational resilience alignment
- Connect critical business services and priorities to technology dependencies, shared infrastructure, and third-party arrangements; contribute technical scenarios, constraints, and results to exercises.
- Identify where component recovery fails to restore the complete business service and coordinate corrective action with technology and business owners.