OSS Network Tester

JOB_DESCRIPTION

Client : Infosys/AT&T
Job Title : OSS Network Tester
Location : NJ (3 onsite 5 days/Week, 3 remotes but needs to be in EST or CST time zone - we can submit 2 candidates on H1 status for Remote)

This is what is required.

Looking for a candidate with Strong Telecom OSS domain expertise, who understands the wireline networks & topology (or even wireless n/w) with good communication skills. Should have sufficient hands on in testing of API's and automation using Python. SQL proficiency with good debugging skills. Knowledge on Temporal and Azure Kubernetes would be an added benefit.

1. Wireline and network domain knowledge as 1^st priority. He/she should know what to test and should be able to tell this is pass or a defect. By Network domain here we mean what is wireline topology, VLAN, Port , various entities such as captive office, OLT , and so on.
2. Should know the network OSS flow of wireline or wireless. Such as if a router is to be added to a new customer, how the flow will start with order placed, engineers/workflow checking inventory is that route has available equipment, and if port / slice is available to give internet connection to the new house. Here the tester should know how to test Inventory flow, configuration flow and so on.
3. We need "Network OSS” which is how the workflows will start process for a new device by checking inventory (equipment, Port etc.) , design the network, configuring the equipment, activating monitoring of the device and so on.
4. lastly the tester should know how to automate these testing by scripting in Playwright and Python. This part, though questions were very tough, but client said that if #1 and #2 are strong, the candidate can ramp up on automation while in project. But some basics on automation must be there.

Simulation / Internal Screening:

1. What do you know about wireline network topology
2. how have you tested OSS flows (network side).
3. what was inventory in your last project and how you tested
4. how do you make framework for test automation

Note: here OSS is NOT the flow of a customer selecting a iphone or samsung model on web page, then workflow takes to page to select plan, then next page to pay by credit card, and lastly activate SIM. This is NOT what is being asked