MNO Acceptance Test Manager

Position Overview 

The MNO Acceptance Test Manager is responsible for leading operator‑side service acceptance for satellite‑to‑mobile connectivity across both lab and field environments. This role ensures that standardized probe packs, acceptance criteria, and validation methodologies meet CIQ requirements, persistence expectations, and service‑level objectives (SLOs) required for pre‑launch, beta, and commercial activation milestones. 

Operating within the Service Acceptance organization, the MNO Acceptance Test Manager reports to Service Acceptance leadership and works closely with RAN acceptance teams, lab engineering, RF engineering, OSS groups, and Service Assurance/NOC teams to ensure acceptance outcomes are technically sound, operationally actionable, and scalable across markets.  

This role is critical to enabling operator confidence, launch quality, and market readiness for satellite‑to‑mobile services. By ensuring that services entering beta and commercial phases meet defined acceptance standards, the MNO Acceptance Test Manager helps drive smoother launches, fewer post‑launch issues, and reduced operational rework.  

Key Responsibilities 

Operator Acceptance Strategy & Planning 

• Define and manage MNO acceptance strategies aligned with market launch, beta, and regional activation plans.  

• Develop standardized acceptance test plans using approved probe packs, test cases, and operator‑defined acceptance criteria. 

• Ensure acceptance scope aligns with CIQs, contractual obligations, and regional regulatory requirements.  

Lab & Field Acceptance Execution 

• Lead execution of operator acceptance testing across lab, controlled field, and live network environments.  

• Validate end‑to‑end service behavior including attach success, session persistence, mobility, throughput, latency, and service continuity.  

• Ensure acceptance execution is repeatable, traceable, and comparable across markets. 

Defect Tracking & Resolution Alignment  

• Track acceptance defects, deviations, and gaps against defined acceptance thresholds. 

• Coordinate with Service Acceptance engineering, RF teams, platform teams, and Service Assurance counterparts to drive resolution. 

• Clearly distinguish acceptance blocking issues from post‑acceptance optimization items. 

KPI Validation & SLO Compliance 

• Validate acceptance KPIs against operator‑defined SLOs and CIQ thresholds. 

• Ensure KPI definitions, measurement methods, and thresholds are consistent with OSS instrumentation. 

• Confirm that acceptance KPIs can be monitored post‑launch through NOC and Service Assurance tooling. 

Artifacts, Reporting & Operator Sign‑Off 

• Produce acceptance artifacts including test plans, probe logs, KPI reports, defect summaries, and acceptance sign‑off packages. 

• Publish acceptance status and readiness reports for internal leadership and MNO stakeholders.  

• Ensure acceptance documentation supports governance, audits, and regulatory reviews. 

Operational Handover & Readiness Alignment 

• Align acceptance results with OSS hooks, alarm definitions, and monitoring dashboards.  

• Ensure NOC playbooks and operational runbooks reflect validated acceptance scenarios. 

• Reduce post‑launch incidents and rework by ensuring acceptance outputs are operationally actionable.  

Deliverables  

• Operator acceptance test strategies and execution plans. 

• Probe‑based acceptance results and KPI validation reports.  

• Defect logs, resolution tracking, and acceptance sign‑off artifacts.  

• OSS and NOC alignment inputs supporting operational readiness.  

• Acceptance documentation supporting pre‑launch, beta, and market activation milestones. 

Qualifications  

Education  

• Bachelor’s degree in Telecommunications, Electronics & Communication Engineering, Elect