Modernization Chief (Modernization Management) #1686229

Network Designs Inc.

29d•Remote

About The Position

The Modernization Chief (Enterprise Architect IV) will lead the VESEE modernization portfolio, ensuring all modernization teams deliver cohesive, aligned outcomes. This role oversees the technical roadmap, architectural alignment, and modernization sequencing across legacy and modern platforms. The Modernization Chief coordinates dependencies across M1-M4 teams and legacy systems, ensuring interoperability, scalability, and delivery coherence.

Requirements

U.S Citizenship required.
Must be able to obtain and maintain a Public Trust clearance
This position is remote but may require occasional onsite meetings in McLean, VA.
You can be based out of following states: AZ, DC, FL, GA, OH, ME, MD, SC, TX, UT, VA, NC, OK, WV.
Bachelor's Degree in Computer Science, Information Technology, or a related field.
At least 10 years of experience in enterprise architecture, modernization leadership, or senior technical roles.
Demonstrated experience leading large-scale modernization initiatives across multiple delivery teams.
Strong experience with Kubernetes, Docker, and GitHub-based delivery models.
Experience with GitOps deployment using ArgoCD.
Experience architecting AWS-based platforms including Amazon EKS, Amazon Route 53, AWS NLB, and AWS ALB.
Experience with data and messaging platforms including Amazon RDS for Oracle, Oracle DB, Amazon MSK, Kafka, Redis, and Amazon ElastiCache for Redis.
Experience with service architectures using Java 17+, Spring Boot, and Spring WebFlux.
Experience coordinating architectures involving legacy platforms such as Oracle WebLogic, Hibernate, and HL7 integrations.
Strong leadership, communication, and cross-team coordination skills.
Ability to manage complex dependencies and drive architectural consensus.

Nice To Haves

Experience leading phased legacy-to-modern modernization programs.
Experience aligning architecture across platform, application, and integration domains.
Experience operating in large, multi-team enterprise delivery environments.

Responsibilities

Modernization Portfolio Leadership: Lead the end-to-end modernization portfolio, defining architectural direction and ensuring alignment across all delivery teams.
Ensure modernization outcomes are cohesive across M1-M4 teams and integrated with legacy systems.
Technical Roadmap and Sequencing: Define and maintain the technical roadmap, including modernization sequencing and dependency management.
Coordinate release sequencing to minimize risk and ensure continuity of operations.
Architecture Governance and Alignment: Establish and enforce architectural standards across platforms, services, and integrations.
Ensure consistency in service design, data flows, and operational patterns across teams.
Platform and Cloud Architecture Oversight: Oversee architecture and operations across Kubernetes-based platforms using Amazon EKS.
Guide use of Docker for containerized workloads and GitHub for source control and collaboration.
Ensure GitOps-based deployment alignment using ArgoCD.
Networking, Observability, and Resilience: Oversee architecture involving Amazon Route 53, AWS NLB, and AWS ALB for traffic management and resilience.
Ensure observability and operational insight using Grafana.
Guide service-to-service communication and resilience patterns using Consul Mesh.
Data, Messaging, and Integration Architecture: Oversee architectures leveraging Amazon RDS for Oracle, Oracle DB, and Amazon EFS.
Guide event-driven architectures using Amazon MSK and Kafka.
Ensure appropriate use of Redis and Amazon ElastiCache for Redis for caching and performance.
Application and Service Architecture: Provide architectural oversight for services built with Java 17+, Spring Boot, and Spring WebFlux.
Ensure alignment between modern services and legacy platforms including Oracle WebLogic, Hibernate, and HL7-based integrations.
Legacy-to-Modern Coordination: Coordinate dependencies between modernized services and legacy systems.
Ensure interoperability and phased transition strategies are followed.
Cross-Team Coordination and Leadership: Serve as the primary technical authority coordinating across M1-M4 teams.
Facilitate architectural decision-making and resolve cross-team technical conflicts.
Documentation and Communication: Maintain clear architectural documentation, roadmaps, and dependency mappings.
Communicate architectural direction and sequencing to technical and executive stakeholders.