MNO Acceptance Test Manager

AST SpaceMobile

About The Position

AST SpaceMobile is building the first and only global cellular broadband network in space to operate directly with standard, unmodified mobile devices based on our extensive IP and patent portfolio and designed for both commercial and government applications. Our engineers and space scientists are on a mission to eliminate the connectivity gaps faced by today’s five billion mobile subscribers and finally bring broadband to the billions who remain unconnected. 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.

Requirements

Bachelor’s degree in Telecommunications, Electronics & Communication Engineering, Electrical Engineering, or a related technical field.
7–12 years of experience in telecom acceptance testing, network validation, service acceptance, or MNO integration roles.
Proven experience leading operator‑side acceptance for mobile, satellite, or hybrid telecom networks.
Experience supporting pre‑launch, beta, and commercial rollout phases across multiple markets.
Strong understanding of end‑to‑end telecom architecture, including RAN, core, transport, OSS, and satellite systems.
Hands‑on experience with probe‑based testing methodologies in lab and field environments.
Deep familiarity with CIQs, persistence testing, acceptance KPIs, and service SLO validation.
Ability to translate acceptance outcomes into operational readiness inputs.
Strong leadership and coordination skills across engineering, RF, lab, and operations teams.
Excellent communication skills for MNO‑facing discussions and internal alignment.
Highly structured, detail‑oriented approach to testing, documentation, and execution.
Ability to manage multiple acceptance cycles across regions and timelines.
Lab and field probe tools (TEMS, Nemo, Accuver, Keysight, Rohde & Schwarz, or equivalent).
OSS/NMS platforms and KPI dashboards.
Defect tracking and test management tools (Jira, TestRail, or equivalent).
Documentation and collaboration tools (PowerPoint, Excel, Confluence, SharePoint).
Willingness to support lab and field acceptance activities, including regional travel as required.
Ability to support extended testing windows during launch and beta milestones.
Ability to coordinate across global time zones.

Nice To Haves

Advanced telecom, RF, or testing certifications are a plus.

Responsibilities

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