Technical Architect

Overview

Required Skills –

• Domain knowledge in applying distributed transaction solutions to billing use and problem cases, preferably in a Telecomm environment on an AMDOCS-derived platform • Deep technical knowledge and practical experience with designing and building systems based on APIs and distributed transaction patterns • Applied knowledge in Service-Oriented and Microservice-based architecture patterns and their use in enterprise distributed systems • Capable of analyzing and understanding complex distributed systems in a very short time frame with minimal documentation or disrupting system subject matter experts • Ability to take an existing system and design & effectively propose a modernization path based on realistic expectations which maximizes business and technical value • Ability to collaborate effectively with technical, semi-technical, and non-technical stakeholders across multiple levels of seniority and responsibility • Can communicate and express technical matters crisply and clearly to nontechnical executive and non-executive business clients

Responsibilities

Required Technical Experience –

Must be able to speak in a fluent, practical manner on : • AMDOCS with preference to those with experience with the derivative product SAMSON • Oracle Tuxedo (including proper use of client libraries and use of enabling add-ons like SALT, CICS App Runtime, TMA, and JCA) • Legacy distributed transaction technology like CORBA and XA • SOAP, REST, GraphQL and other API Patterns • Enterprise API Management technology like Mulesoft or Oracle service bus • In-depth knowledge of the TM Forum Open APIs and Document standards • Practical experience with telecom-specific concepts such as CDR processing, roaming data handling, taxation logic, accounts receivable (AR), and RFS/provisioning integration

Qualifications

Preferred Skills and Experience –

Those who can also speak fluently to any or all the following are preferred: • Recent experience in modernizing and improving an Enterprise-level billing system, especially if the system featured one or more of the following: o Extensive layer of integration with other Enterprise and third-party systems o Service-based integrations using more than just RESTful APIs o Direct connection to or operated on behalf of a telecom related business • Practical experience with Java, Springboot, and relational databases like Oracle for the building of Enterprise distributed transaction systems • Knowledge of networking and container-based operation of a distributed transaction system either on-prem or in the cloud