Telecommunications Engineers
Plan, design, develop and monitor telecommunication systems, networks, devices and broadcasting equipment.
The storm and the missing link
You are a telecommunications engineer on call for a regional network, in the middle of a severe storm. It is 6pm. A fallen tree has cut a main link, and the town of Wirrinya has lost most of its phone and internet service. The town's only clinic and the local fire brigade rely on it.
Choose what you would do. Then see what happens. There are often good reasons for each choice.
We have lost the main link to Wirrinya. We have a backup that gives very limited capacity, and a lot of people want it. The clinic, the fire brigade and the pub all rang within ten minutes. Who gets priority?
Give it to whoever rang first, to keep it fair
It feels fair, but the first caller was the pub, and the clinic waits. Treating everyone equally is not always treating them well.
Give the clinic and the fire brigade the capacity first, and tell the others why they are waiting
Emergency services and the clinic stay connected through the night. The pub's owner is annoyed until you explain, and then says he understands. Prioritising on need, and saying so, is what the role demands.
Split the backup into equal shares so that no one is left out
Everyone gets a share, but a share this small is not enough for anyone. The clinic's calls drop and the fire brigade cannot reach its radio system. A weak signal for all can be worse than a strong one for a few.
I'm at the broken link. The tree is across the line, and the crew from the power company is nearby. I could start working now, but I'm not sure about the area. Do you want me to go ahead?
Tell him to go ahead, because the town needs the link as soon as possible and the tree is already down
He starts work close to equipment that has not been confirmed safe. The power crew stops him just in time. Speed matters, but never ahead of the safety of the person doing the job.
Tell him to wait and ring you in an hour to say how things look on site
He stays safe, but nobody has told him what to prepare in the meantime. An hour passes without progress and the town stays cut off.
Tell him to wait for the power crew's all-clear, get his gear ready and ring you when it comes
The all-clear comes in forty minutes. Ahmed is ready, and the link is repaired within the next two hours. Doing the preparation first meant the wait cost little.
People in Wirrinya are asking when their phones will come back. We can broadcast a message. What should I tell them? I don't want to promise something that isn't true.
Give her an exact time, so that people can plan their night and the clinic knows when to expect calls
People plan around it, but repairs run late and the time passes. The community loses patience with you. A range with honest caveats works better.
Tell her what has happened, what is being done and when the next update will come
The broadcast calms the town, and people check the radio at the time you said. Honest updates keep trust even when the news is bad.
Tell her to say nothing until it is fixed, to avoid confusion and false hope on air
Silence breeds rumours. By nine o'clock, the story going round is that the whole network is down for days, and the phones at the exchange are overwhelmed.
How it went
The link was repaired late that night. The clinic and the fire brigade stayed connected, and the town heard honest updates. Telecommunications engineers design, build and repair the networks people rely on without noticing, often under weather, distance and deadlines. Does being part of the unseen system appeal to you?
This is a simplified, fictional situation to help you explore. It is not professional instruction or a test of your ability.
Case study: The tower the town did not want
A fictional case set in a telecommunications design office, with regular trips to towers, exchanges and country sites.
The situation
Sione was a telecommunications engineer designing a new mobile tower for the small town of Gundooee, which had patchy coverage. The best site, on a low hill, was beside a popular walking track. At the first public meeting, residents were upset: they said the tower would spoil the view and worried about its effects. Sione's plan was technically sound, and the deadline from his employer was tight.
What they did
Sione listened to every concern and wrote them down. He showed photos of how tall the tower would look from the track and from the main street. He then tested two other sites, which gave weaker coverage but were less visible, and explained the trade-off honestly, including which streets would have a weaker signal. He gave the community a clear way to comment, and said when a decision would be made.
How it turned out
The town chose a site slightly lower on the hill, with a design that blended better with the trees. Some residents were still unhappy, and others said they were glad to have been asked. The project took longer than planned, and the coverage was good enough for most of the town.
What would you do?
- How would you weigh a better signal against what the community wants?
- What does it take to explain a technical decision so everyone can understand it?
- Would you be comfortable accepting that a good design is not always the one that gets built?