Skip to main content

SpaceX

RAN Validation Engineer (Starlink Mobile)

Palo Alto, CAmidAdded yesterday

About this role

SpaceX seeks a RAN Validation Engineer to validate and optimize the 4G/5G protocol stack for Starlink Mobile's satellite-to-cellular network. You'll develop automated tests, perform lab and field testing, analyze network performance, and collaborate with developers to resolve complex RAN issues.

What you'll do

  • Develop and maintain automated test frameworks for eNB/gNB feature validation (functional, performance, interoperability, regression)
  • Analyze UE and base station logs to debug RAN issues and drive developer fixes
  • Lead field testing and UE log collection to support feature development
  • Build software tools and database queries to analyze performance and optimize network parameters
  • Manage network issues and coordinate resolution with development teams
  • Maintain RAN lab infrastructure in collaboration with partner teams

What they're looking for

  • RAN parameter configuration and optimization
  • LTE/5G-NR protocol knowledge
  • Python for test automation and data analysis
  • Linux and Git
  • Test case development and management
  • Log analysis and debugging
  • Network performance analysis
  • SQL or database queries
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

SpaceX

SpaceX develops advanced spacecraft and satellite systems, including the Starshield government satellite constellation and Starfall re-entry cargo capsule for global delivery. The company is hiring engineers in avionics integration, software test automation, mechanical design, and hardware reliability to validate flight-critical systems and ensure mission success.

Website
spacex.com
View all jobs at SpaceX

Likely interview questions

  • Describe your experience optimizing RAN parameters—what metrics did you focus on and what methods did you use?
  • Walk us through how you've debugged a complex RAN issue from logs; what was your approach?