Telecom OSS Mainframes Architect

Gstate Consulting Llc
Atlanta, United States of America
yesterday

Role details

Contract type
Permanent contract
Employment type
Full-time (> 32 hours)
Working hours
Regular working hours
Languages
English

Job location

Remote
Atlanta, United States of America

Tech stack

Java
API
Amazon Web Services (AWS)
Business Logic
Azure
Customer Information Control System (CICS)
Cloud Computing
Cloud Engineering
COBOL
Databases
IBM DB2
Distributed Data Store
Job Control Language (JCL)
IBM Mainframe
IBM Information Management System
Intrusion Detection Systems
Python
PostgreSQL
MongoDB
Cloud Services
Pl/i
Swagger
Z/OS
Openapi
Google Cloud Platform
Cloud Platform System
Istio
Spring-boot
HybridCloud
Change Data Capture
Event Driven Architecture
Containerization
Kubernetes
Information Technology
Apache Flink
Kafka
Linkerd (Service Mesh)
Api Design
Api Gateway
REST
Stream Processing
Domain Driven Design
gRPC
Data Pipelines
Docker
Go
Microservices

Job description

  • 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.

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

Requirements

  • 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.

Apply for this position