Technology Lead | Telecom | Telecom-Online

Experience-1Description: POC: RajuJob Details:Job title: Telecom OSS Modernization Architect – Legacy Mainframe to Cloud-Native SpecialistWork Location with Zip code: Plano, TX 75075Duration of the project: 6 Months· This role requires any travel (Yes/No): NO· Please confirm if this would be onsite from day one OR Initial remote for 2-3 months, and then expect the candidate to work from the office OR 100% Remote: Onsite from day one· Is this a 100% remote role? NO· Vendor rate range: *** · Minimum years of experience required: 7-10 Years· Would you require the candidates to meet you for an in-person interview?: Video/Virtual Interview· Education Qualification required: BEJob Title: Telecom OSS Modernization Architect – Legacy Mainframe to Cloud-Native SpecialistRequired 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).• Education: Bachelor’s or Master’s degree in Telecommunications, Computer Science, or Network Engineering.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.Custom Fields: Name: Intake Call CompletedValue: trueName: Intake Call RequestedValue: true