CDR for Telecommunications Engineer, ANZSCO 263311: EA or ACS?

Three occupations share the 263 prefix and they do not share an assessing authority.

Applicants routinely get this wrong in both directions. The consequence is not a correction — it is a refund arriving several months later, by which time an English test may have expired or an age bracket closed.

Decide by duties. If your work is RF, transmission, optical, radio access or carrier network engineering, you are in 263311 or 263312 territory. If it is enterprise LAN, servers, virtualisation and identity, that is 263111 and the ACS.

Both go to Engineers Australia, so getting this one wrong is less costly, but it still matters.

263311 Telecommunications Engineer leans toward the physical and radio layers: RF planning, link budgets, antenna and microwave design, optical transmission, spectrum and ACMA compliance, and the equipment that carries the signal.

263312 Telecommunications Network Engineer leans toward the network layer: IP/MPLS architecture, capacity and traffic engineering, resilience design, OSS and network performance across a carrier or large enterprise estate.

Careers frequently span both. Pick the one your last several years actually sit in, and make sure your reference letters describe those duties.

The strongest telecom episodes contain an analysis you performed that changed a design.

• A link budget or coverage study. Path loss model chosen and justified, fade margin selected, the result compared with a measured drive test or OTDR trace.
• A capacity or performance investigation. KPI data showing degradation, a hypothesis, a measurement that confirmed or killed it, and an engineering change.
• A rollout or migration design. The constraints you worked within, the options you evaluated, and the rollback design — which is often the most engineering-heavy part and the most commonly omitted.

Weak: "I was responsible for the RF planning of the network expansion and ensured coverage requirements were met using the planning tool."

Strong: "I planned 14 sites for the regional expansion using a COST-231 Hata model calibrated against drive-test data from three existing sites, which showed the default model was optimistic by 6 dB in the local terrain. Applying the calibrated model moved two proposed sites and added one, because the original plan left a 4.2 km gap along the highway that the uncalibrated model had shown as covered."

• Vendor configuration as design. Commissioning a base station to a plan someone else produced is deployment. It becomes engineering when you produced or changed the plan.
• Certifications instead of analysis. Vendor certifications are training, not competency evidence. Assessors want what you calculated.
• No measurements. Telecom is a measured discipline. Claims without KPI data, drive tests, OTDR results or capacity figures read as assertions.
• Unexplained overlap with ACS occupations. If your CV reads like a network administrator's, explain in your CDR why the work is carrier-grade telecommunications engineering.

Occupation detail — salary band, visa pathways and episode angles — is on the ANZSCO 263311 page.

Fibre and transmission work produces some of the cleanest competency evidence available in this occupation, because the physics is unambiguous and the measurements are objective.

• An optical link budget — launch power, span loss from your own OTDR traces, connector and splice allowances, dispersion penalty, and the margin you carried. Where the measured loss exceeded the design budget and you found why, that is PE2.2.
• A DWDM or GPON design — channel plan, split ratio, reach calculation against the optical budget, and the constraint that governed the architecture.
• A microwave path design — path profile, Fresnel clearance, rain fade to ITU-R models, availability target, and the antenna or frequency choice that followed.
• A synchronisation or timing design, which is specialist enough to demonstrate PE1.3 convincingly.

In each case the pattern is the same: a requirement, a calculation, a measurement that tested it, and a decision.

Telecom applicants routinely omit regulatory work, treating it as administration. It is not — it is PE1.5 and PE1.6 evidence, and often PE3.1 as well.

Worth writing about: ACMA spectrum licensing and interference coordination, EMR compliance assessments against the relevant exposure standard, aviation obstacle clearance for tower siting, and the environmental or community constraints that moved a site.

A site you had to relocate because the EMR assessment showed a compliance boundary crossing a school boundary is a stronger PE1.6 and PE3.1 paragraph than any generic statement about valuing safety. It is a constraint you did not choose, that cost the project something, and that you engineered around.

Many telecom careers include work that looks like ICT on paper — routers, switches, network management platforms. Because 263111 goes to the ACS, an assessor at Engineers Australia may reasonably wonder whether your application arrived at the right authority.

Address it rather than hoping it passes. In your CV and in the background section of at least one career episode, make the nature of the work explicit: carrier-grade or large-scale telecommunications infrastructure, physical and transmission layer engineering, spectrum and regulatory frameworks, availability and capacity engineering at network scale.

Practical markers that signal telecommunications rather than enterprise ICT: link budgets and RF planning, transmission and optical design, carrier interconnect, ACMA compliance, and network dimensioning against traffic models. If your work has none of these and is really enterprise infrastructure, the honest conclusion is that you belong at the ACS — and finding that out now costs you nothing, while finding out in four months costs the fee and the time.

Because the authority question is the biggest risk in this occupation, the order of work matters more than usual.

1. Settle the authority first. Map your actual duties against the ANZSCO descriptions for 263311, 263312 and 263111 before anything else. Our eligibility checker takes two minutes and the consequence of getting it wrong is months.
2. Check the accord position on your degree. If your qualification is Washington Accord recognised within the coverage period, you may not need a CDR at all — see the skills assessment guide.
3. Gather technical records. Link budgets, drive-test reports, OTDR traces, KPI exports, design documents. Telecom evidence is measured evidence, and none of it is in your CV.
4. Request reference letters early, phrased in engineering terms rather than by job title.
5. Write, then have it checked before you pay a non-refundable assessment fee.

Telecommunications demand in Australia has been sustained by fibre rollout, mobile network densification and the communications layer of grid and transport projects — so the pathway after a positive outcome is generally a good one.

• Have you confirmed the authority — Engineers Australia for 263311 and 263312, ACS for 263111?
• Does at least one episode contain a calculation you performed: link budget, coverage prediction, capacity model, path analysis?
• Is there measured data somewhere — drive test, OTDR, KPI export — tested against a prediction?
• Have you shown a case where the measurement disagreed with the model and you resolved it?
• Have you addressed the ICT overlap explicitly, so the assessor is not left wondering?
• Do your reference letters name telecom engineering duties rather than generic network administration?
• Is there any regulatory or spectrum content for PE1.5 and PE1.6?
• Has the report been text-matched before submission?