Entry Level: 6G Developer

About this opportunity

Forty percent of the world's mobile traffic is carried over Ericsson networks.

Nobody thinks about that until it stops. A mobile network is how people call an ambulance, pay for lunch, and find each other. When it works it is invisible. When it fails it is national news. That is the scale a single line of baseband code operates at.

We are entering the 6G program now and forming the teams that will carry it. That is why we are hiring. Join in three years and you inherit the decisions — join now and you make some of them.

We are looking for newly graduated engineers at the start of their career to build the first 6G product with us.

What you will do

You will join a cross-functional team working in baseband software development — in the physical layer, where radio energy becomes data, or in the uplink and downlink processing chains that schedule and move user data. We will not pretend there is a long 6G delivery history to join. There is not. That is the point, and it is what makes this different from maintaining something finished.

The difficulty is real, and it is specific. Real-time C and C++ under microsecond deadlines, against 3GPP specifications, on multi-core DSPs, is unforgiving work — and it is exactly where a confident wrong answer from an LLM looks identical to a correct one. So we treat working with AI as an engineering skill to be learned rather than a tool to be handed out, and the scarce part of that skill is judgment: knowing which answers to trust, which to verify, and which to throw away.

The craft itself is classic baseband engineering, and it looks like this:

Take a feature from a question to shipped code — studies, systemization, design, implementation, test. Rework parts of a 5G baseband that has shipped to hundreds of networks so that it carries 6G, without breaking what runs today. Work against a standard that is still moving, and feed what you learn back into it. Read code you have never seen before, in a codebase far larger than anything at university, and find the three lines that matter.

The skills you bring

An MSc in computer science, electrical engineering, engineering physics, wireless communication or similar. C or C++ close to the hardware, and enough mathematics to be unafraid of a signal. Something you have built because you wanted to build it, not because it was assigned. Comfort working where the answer is not known yet. Much of this has not been done before, by anyone.