Technology Lead | Telecom | Telecom-Online

Telecom Oss Modernization Architect – Legacy Mainframe To Cloud-Native Specialist

This role requires travel:
No.

Work location:

Plano, TX 75075. Duration of the project: 6 months. This role is not 100% remote. Vendor rate range:
Not disclosed. Minimum years of experience required: 7-10 years. Education qualification required:
Bachelor's or Master's degree in Telecommunications, Computer Science, or Network Engineering.

Required skills:

• Legacy decoupling:
  Proven track record of decomposing IBM mainframe systems (z/OS, IMS DB/DC, DB2) using patterns like the Strangler Fig pattern.
• Cloud & containerization:
  Expert-level mastery of Kubernetes, Docker, and enterprise cloud architecture patterns.
• API & service mesh:
  Extensive experience with API gateways, service mesh (Istio/Linkerd), and schema protocols (OpenAPI/Swagger).
• Modern development:
  Proficiency in Java (Spring Boot), Go, or Python for building highly resilient, distributed microservices.
• Data pipelines:
  Experience with real-time data streaming (Kafka, Flink) and modern distributed databases (PostgreSQL, MongoDB).

Core responsibilities:

• Architecture transformation:
  Define end-to-end functional architecture to transition legacy, monolithic TIRKS mainframe systems (z/OS, IMS, DB2) into modern midrange, cloud, or service-based platforms.
• Monolith decomposition:
  Deconstruct legacy TIRKS PL/I or COBOL business logic, IMS databases, and JCL paths into modern, decoupled microservices.
• API-first design:
  Architect and enforce the implementation of high-performance RESTful or gRPC APIs to expose circuit design, inventory, and provisioning capabilities.
• Domain-driven design (DDD):
  Translate historical TIRKS concepts like Connecting Facility Assignments (CFAs), circuit IDs, and trunk layouts into modern domain models.
• Cloud-native migration:
  Direct the containerization (Kubernetes) and migration of core functionality into cloud environments (AWS, Azure, or GCP).
• Event-driven integration:
  Replace legacy batch jobs and CICS transactions with real-time, event-driven pipelines using Apache Kafka.
• Dual-run strategy:
  Implement data-sync strategies (like Change Data Capture) to run TIRKS and new cloud services in parallel during transition phases.