1

Internship Ran Engineer Jobs (NOW HIRING)

Wireless Network Lab Intern

Chandler, AZ · On-site

$14.75 - $19.75/hr

Collaborate with cross-functional engineers (RF, RAN, security, software) to translate domain ... Prior industry research internship experience. If you have what it takes to push boundaries and ...

Jr. Software Developer

Coppell, TX · On-site

$66K - $86K/yr

... RAN, Cloud and Core products for our customers operating in NTN. NTN project is Nokia co-operation ... Previous Nokia or Infinera co-op or internship experience. * Work on prototyping and product ...

Lead UX Designer

Santa Monica, CA · On-site

$123K - $161K/yr

As a leading worldwide developer, publisher and distributor of interactive entertainment and ... and interns with the Company. You can learn more by visiting In the U.S., the standard base pay ...

next page

Showing results 1-20

Internship Ran Engineer information

See salary details

$11

$19

$29

How much do internship ran engineer jobs pay per hour?

As of Jun 28, 2026, the average hourly pay for internship ran engineer in the United States is $19.31, according to ZipRecruiter salary data. Most workers in this role earn between $16.11 and $20.91 per hour, depending on experience, location, and employer.

What is the difference between Internship Ran Engineer vs Network Operations Intern?

AspectInternship Ran EngineerNetwork Operations Intern
CredentialsRelevant coursework, basic certifications (e.g., CCNA), technical skillsSimilar certifications, focus on network fundamentals
Work EnvironmentTelecom or network service provider, field and office settingsNetwork operations centers, office environment
Industry UsageTelecommunications, IT service providersTelecom, IT companies, network service providers
Job FocusSupporting Radio Access Network (RAN) systems, network deploymentMonitoring, troubleshooting, and maintaining network systems

Internship Ran Engineer and Network Operations Intern roles share a focus on network systems and require similar foundational certifications. However, the Internship Ran Engineer typically emphasizes RAN systems and telecom-specific tasks, while the Network Operations Intern concentrates on network monitoring and troubleshooting. Both roles serve as entry points into the telecom and network industry, providing valuable hands-on experience.

More about Internship Ran Engineer jobs
What cities are hiring for Internship Ran Engineer jobs? Cities with the most Internship Ran Engineer job openings:
What are the most commonly searched types of Ran Engineer jobs? The most popular types of Ran Engineer jobs are:
What states have the most Internship Ran Engineer jobs? States with the most job openings for Internship Ran Engineer jobs include:
Infographic showing various Internship Ran Engineer job openings in the United States as of June 2026, with employment types broken down into 99% Full Time, and 1% Part Time. Highlights an 90% Physical, 1% Hybrid, and 9% Remote job distribution, with an average salary of $40,174 per year, or $19.3 per hour.

General Interest - Talent Network

Aurelius Systems

San Francisco, CA • On-site

Full-time

Posted 6 days ago


Job description

This Isn't a Catch-All Application:
If your background fits one of our open roles... apply there. Those postings exist for a reason and you'll get evaluated faster through the right pipeline.
This page is for people who don't see their exact role listed but belong at Aurelius. We're building a short list of people we want to pull from when new roles open, when we spin up internships, or when the right person shows up before the req does.
We review every submission. If you're not a fit, you'll know. If you are, you'll hear from us - maybe this month, maybe in six.
Who We're Looking For
You probably fall into one of these lanes:
1. Engineers Who Build Things
You're an ME, integration engineer, systems engineer, controls engineer, or something adjacent - and you've actually built software, or hardware that went into the real world. Maybe you worked on power systems at a FSAE Electric team and went pro. Maybe you've been at a defense startup or eVTOL company where you owned a subsystem end to end. Maybe you're still in school but you've built more in your garage or lab than most people build in their first three years of work.
We care about what you've built, not where you went to school.
2. Veterans With Technical or Operational Depth
You served and you're looking to stay in the fight from the builder side. Maybe you were a combat engineer, Special Operations, EOD, fire controlman, or had a technical MOS/rate. Maybe you ran operations or logistics in environments where things had to work the first time. We value military discipline and bias for action, but we're not collecting DD-214s - we need people who can contribute technically or operationally from day one.
3. Defense Business Operations
Proposal managers, capture managers, contract administrators, or BD professionals who have actually won contracts with Army, Navy, Marines, or MDA. Not people who worked at a prime and attended reviews. People who wrote the winning sections, managed the compliance matrix, or ran a capture from qualification to award. IDIQ and OTA experience is a plus. If you've only worked commercial or big-company BD where a team of 40 touches a single proposal, we're probably not the right fit.
4. Technical Operators
Growth, strategy, talent, mission operations - whatever you call it, you're the person who makes a small team punch way above its weight. Maybe you've scaled hiring at a defense startup and actually know the difference between a power electronics engineer and a semiconductor process engineer. Maybe you've run field operations, managed test campaigns, or built the operational backbone that lets engineers focus on engineering. Maybe you're a strategy or growth person who's worked in deep tech and understands long DoD sales cycles, IDIQ task orders, and what it takes to go from prototype to program of record. We don't need generalists who "wear many hats." We need people who've operated in high-output, resource-constrained environments and made things move faster than they had any right to.
What's True Across All of These
  • U.S. citizenship required. We work on classified programs and every role requires the ability to obtain a security clearance.
  • You'll be in San Francisco or Detroit. We're not remote. The hardware is here and so are you.
  • Bias for action over credentials. We've hired people without degrees who outperform PhDs. We've also hired PhDs who get their hands dirty. What matters is whether you build things or talk about building things.
  • Startup pace is real. Core hours are Monday through Friday, 9 to 6. When we sprint toward a demo or field test, the team goes hard - nights, weekends, whatever it takes. When the sprint lands, we recover. If that sounds like a warning, this isn't for you. If it sounds like home, keep reading.
What to Include in Your Application
Don't send a generic resume and cover letter. We read these and generic applications go to the bottom.
Instead, tell us:
  1. Which lane above fits you best and why you think you'd be a fit at Aurelius specifically - not just any defense startup.
  2. The hardest thing you've built or shipped. What was it, what was your role, and what made it hard?
  3. Your resume or LinkedIn - but only after #1 and #2. Those matter more.

If you're not sure whether to apply here or to a specific role, apply to the specific role. This page is for the people who know they belong here but don't see their exact seat yet.