Cloud Tech

Job Description : Cloud Tech

Location : Remote

8+ Years hands-on experience in product development, particularly in design and coding using C++ and Python for cloud-based technologies.

Experience in NMS (Network Management Systems) and telecommunications or networking domain is highly desirable.

Experience in Kubernetes ecosystem & Cloud-native application design

Experience with cloud platforms and networking on cloud and Kubernetes services (logging, resource sharing, etc.)

Experience in Scalable system architecture design and Microservices architecture

Experience in Information modelling aligned with standards (SysML, UML)

Experience with at least one of the databases : PostgreSQL, NoSQL (MongoDB), TimescaleDB, CortexDB

Experience in Elastic Search and Visualization tools : Kibana, Grafana

Experience in Languages : C++, Python, Java, JavaScript, SQL

Experience in API design : REST, gRPC, GraphQL

Key Responsibilities

• build an information model, aligned with element management standards and specifications, that represents the system functionality via which an operator shall be able to manage and control his network.
• build a scalable system architecture of the Network Management System using cloud native components and micro services architecture.
• collaborate with specialists and architects covering different technology domains.
• contribute to an NMS application architecture for configuration management of the network elements and functions
• contribute to an NMS application architecture for receiving events, notifications, statistics collection from the different network elements and functions.
• collaborate with the development teams to ensure the defined system architecture is implementable, inclusive of effort estimation and test strategy.
• collaborate with other system architects and development teams to work on proof of concepts and early evaluation.

Other key responsibilities and job functions include :

What are the Optional skills and skill proficiencies for this position?

You hold a master's degree in engineering or computer science with 5+ years of experience in most of the areas below. You have experience with the Web Application Architectures and distributed system design.

As a Network Management Architect, you have the following expertise :

o Knowledge of modeling languages like UML, SysML is an asset

o Experience with software development methodologies and associated programming languages is important

o Experience in designing for scale and high availability.

o Knowledge and thorough understanding of programming languages like Python, Java, Javascript, C++, SQL is an asset

o Thorough understanding of databases like Timescale DB (or any Time Series DB), PostgreSQL, NoSQL (like MongoDB), Cortex DB.

o Experience and understanding of Cloud Native application development best practices, knowledge of micro-services.

o Experience in Kubernetes, Cloud platforms, networking on cloud platforms and Kubernetes ecosystem.

o Experience in data collection pipeline- data extraction, transformation, and integration.

o Experience in log collection systems like Loki, Logstash and visualization systems like Kibana, Grafana.

o Experience is designing using REST, gRPC and GraphQL.

o Understanding of network management protocols or generic communication protocols like SNMP / MIB, NetConf / YANG, REST (OpenAPI) or GraphQL is an asset

o Knowledge of telecom management standards provided by TM-Forum, ITU-T, O-RAN, 3gPP or ONF is a plus

o Understanding of security concepts is key (Authentication, Authorization- Role Based Access Control)

o Experience with open source or commercial management systems is a plus

CONIDERATIONS FOR SCREENING

Client primarily focuses on three areas :

The NMS encompasses OAM (Operations, Administration, and Maintenance), which broadly includes the following functionalities :

These functionalities are implemented using a cloud-native design, deployed on a cloud platform, and leverage technologies such as :

Additionally, OAM functions are designed using data modeling principles and standards-compliant messaging formats for faults, statistics, and events. Awareness of OAM in mobile telecommunication standards (e.g., NETCONF / YANG) is helpful in designing OAM solutions for Satcom. The design principles are similar.

The NMS is used to manage the Satcom data path and ground system. A parallel in mobile telecom would be the EMS (Element Management System) for 5G / LTE RAN. So, someone who has worked in EMS is a viable candidate. Awareness to 5g / LTE helps in understanding Satcom and hence the reference.

Client team's future development focus is on building a data analytics platform.

All the above reflects what Client is currently focusing on. Client current architecture aligns with this 1 : 1.

Key Clarification Areas from client :

[Client]

1. Designing and deploying cloud-native applications

2. OAM knowledge

[Client]

Tooling is used to realize the OAM / NMS solution.

[Client]

It aligns with what I've described above. This is our area of focus.

Deeper Dive Questions

1. What is the primary business problem this role is solving?

[Client] Designing an NMS and data analytics platform for our Satcom solution.

2. What percentage of the role is architecture vs. hands-on development?

[Client] 90% architecture / 10% hands-on. Hands-on work is limited to proof-of-concept development or tooling as needed.

3. Is the focus on building new systems or enhancing existing ones?

[Client] New systems.

4. Can you prioritize the listed technologies (Top 3 and Next 3)?

[Client]

o Top 3 : Cloud-native application design, cloud platforms, tooling

o Next 3 : Awareness of OAM / NMS / EMS

5. Is C++ required for daily development, or is familiarity sufficient?

[Client]

Familiarity is sufficient. I mentioned C++ because candidates with a software development background in C++ typically understand object-oriented design and the architectural challenges involved.

6. Is data modeling a core function, or could UML / SysML experience be acceptable?

[Client]

Great question! Either would be acceptable.