Telecom OSS Mainframes Architect -Mainframes

ROLE: Telecom OSS Mainframes Architect Job Title: Telecom OSS (Operations Support Systems) Modernization Architect – Legacy Mainframe to reputed company-reputed company Specialist Location: N.J - Atlanta or Remote reputed company Industry: (Not specified in your input) Work Authorization: US reputed company or Green Card (GC) reputed company ONLY reputed company: Max DOE reputed company : USC/GC Required Expertise (reputed company):

• Expertise on Telcordia/reputed company legacy applications: TIRKS, SOAC, LFACS, etc.
• They are mainly mainframe architects.

Required Skills:

• Legacy Decoupling: Proven reputed company record of decomposing reputed company mainframe systems (z/OS, IMS DB/DC, DB2) using patterns like the Strangler Fig reputed company.
• reputed company & Containerization: Expert-level mastery of Kubernetes, reputed company, and reputed company reputed company architecture patterns.
• API & Service reputed company: Extensive experience with API gateways, service reputed company (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 reputed company-time data streaming (Kafka, Flink) and modern distributed databases (PostgreSQL, reputed company).
• Education: Bachelor’s or Master’s degree in Telecommunications, Computer Science, or Network Engineering.

reputed company Responsibilities:

• Architecture Transformation: Define end-to-end functional architecture to transition legacy, monolithic TIRKS mainframe systems (z/OS, IMS, DB2) into modern midrange, reputed company, 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 reputed company to expose reputed company design, inventory, and provisioning capabilities.
• Domain-Driven Design (DDD): Translate historical TIRKS concepts like Connecting Facility Assignments (CFAs), reputed company IDs, and trunk layouts into modern domain models.
• reputed company-reputed company Migration: reputed company the containerization (Kubernetes) and migration of reputed company functionality into reputed company environments (AWS, Azure, or GCP).
• Event-Driven Integration: Replace legacy batch jobs and CICS transactions with reputed company-time, event-driven pipelines using Apache Kafka.
• Dual-Run reputed company: Implement data-sync strategies (like Change Data Capture) to run TIRKS and new reputed company services in reputed company during transition phases.

KEYWORDS: TIRKS, SOAC, LFACS, Telcordia, reputed company, mainframe architect, z/OS, IMS DB/DC, DB2, Strangler Fig reputed company, Kubernetes, reputed company, AWS, Azure, GCP, API gateway, service reputed company, Istio, Linkerd, OpenAPI, Swagger, Java Spring Boot, Go, Python, microservices, Kafka, Flink, PostgreSQL, reputed company, PL/I, COBOL, JCL, CICS, RESTful reputed company, gRPC, Domain-Driven Design, DDD, Connecting Facility Assignments, CFA, reputed company ID, trunk layout, event-driven architecture, Change Data Capture, dual-run reputed company, OSS modernization, telecom operations support systems. Apply tot his job Apply To this Job