You can spend fifteen years designing 11kV feeders and coordinating protection relays and still receive a negative outcome from Engineers Australia. A CDR for electrical engineer applicants under ANZSCO 233311 almost never fails on engineering merit. It fails because the report credits a team for decisions that needed to be attributed to you, or because the applicant chose the wrong occupation code before writing a single sentence.
EA assesses three career episodes of 1,000 to 2,500 words each, one summary statement that maps those episodes against its competency standard, and a continuing professional development (CPD) log. This guide assumes you know the CDR scaffolding and links out where you need the mechanics: start with the career episode format and structure and the full 2026 CDR guide. What follows is built specifically for power engineers: which of your projects qualify, how to frame HV/LV and protection work in EA's language, and where 233311 applicants lose marks.
What ANZSCO 233311 Covers and Who Qualifies
The scope EA assesses across generation and control of power
ANZSCO 2022 defines 233311 Electrical Engineer as an occupation that "designs, develops and supervises the manufacture, installation, operation and maintenance of equipment, machines and systems for the generation, distribution, utilisation and control of electric power." The classification lists three specialisations under it: Electrical Design Engineer, Railway Signalling Engineer, and Signalling and Communications Engineer.
Read that scope as a filter. Power at the centre of your career, generating it, moving it, protecting it, controlling it, or using it at scale, puts you in the right unit group. High-voltage substation design, distribution network planning, protection and control, motor and drive systems, and grid connection all sit comfortably inside it.
233311 vs 233411: the code mix-up that costs months
There is no ANZSCO 233312. Several guides invent it, but ABS ANZSCO 2022 unit group 2333 holds exactly one occupation, 233311. The code that actually trips people up is 233411 Electronics Engineer, which lives in a different unit group and covers work that "designs, develops, adapts, installs, tests and maintains electronic components, circuits and systems."
The line is discipline, not job title. Design an 11kV switchboard, a feeder protection scheme, or a grid-connection layout, and you are 233311. Design a printed circuit board, an embedded controller, or an RF communications module, and you are 233411. Pick the wrong one, and EA measures you against mismatched competency expectations, which usually means a negative outcome, a fresh fee, and several months lost. If your work straddles both, choose the code that matches the majority of the engineering decisions you can evidence, then confirm your choice against our ANZSCO code selection guide before you commit.
Which Projects Work as Career Episodes Under 233311
The projects you choose for a CDR for electrical engineer submission matter more than how well you write them. A polished episode about a job where you observed or coordinated will still fail. A plainly written one about a design you owned will pass. Pick projects where you made engineering decisions and can name them.
Power system design: load flow, fault levels, and switchgear
This is the strongest evidence base for 233311. Load flow studies, fault level calculations, protection grading, HV/LV switchgear selection and sizing, cable sizing to AS/NZS 3000, and single-line diagram development all put your individual judgement on the page. An assessor can see the problem, your method, and the number you committed to. Running a short-circuit study in ETAP or DIgSILENT and setting equipment ratings off the result gives you a career episode waiting to be written.
Protection, relay coordination, and SCADA/PLC automation
Protection work carries dense, defensible decisions: choosing IDMT or definite-time curves, setting pickup and time-multiplier values, grading feeder relays with upstream protection, specifying CT ratios. SCADA and PLC automation projects qualify when you designed the control philosophy, the I/O architecture, or the interlocking logic, rather than wiring to someone else's schematic. The test is always the same: did you decide, or did you follow?
Renewable and grid-connection work: solar, wind, storage
Solar farms, wind connections, and battery storage integration are excellent 233311 material, and they carry a freshness advantage few competitor pages currently exploit. If your episode involves inverter-based grid connection, cite AS/NZS 4777.1:2024, the September 2024 edition that replaced the 2016 standard. It changed things a protection engineer must know: systems under 200 kVA no longer require interface protection unless the local Distribution Network Service Provider specifies it, single-phase installations are capped at 30 kVA, and Vehicle-to-Grid provisions now appear in the standard. An episode referencing the current edition signals you practise to today's rules.
What EA will not count toward 233311
Four categories sink applications more often than weak writing does. Pure electrical installation and wiring is trades scope, not professional engineering. Observer roles and project-management-only positions, where you scheduled and coordinated but made no engineering decisions, give the assessor nothing individual to credit, and they will not qualify. Circuit-board and embedded work belongs under 233411. A project where the design was fixed before you arrived leaves you describing someone else's engineering. When in doubt, ask whether you could defend a specific technical choice under questioning.
How to Write a CDR for Electrical Engineer: Step by Step
Setting project context in CE1.1 to CE1.3
Open with just enough context to make your decisions legible, then stop. The background paragraphs, numbered CE1.1, CE1.2 and so on following the CE[episode].[paragraph] convention, should establish the project, your position, and the engineering objective in roughly 150 to 250 words. Assessors read to locate you in the org chart and the technical problem, not to learn the company's history. For the full three-part background, activity, and summary shape, use our career episode structure guide rather than padding this one.
Writing I-statements that name your own decisions
This is where most 233311 episodes are won or lost. Consider two versions of the same protection work.
Team voice, which fails: "The protection settings for the incoming 11kV feeder were determined and the relays were configured to grade with the upstream protection."
I-statement voice, which passes: "I calculated the fault levels at the 11kV busbar, selected IDMT curves for the feeder relays, and set the time multiplier to 0.3 to grade with the upstream 33kV protection, which I verified with a coordination study I ran in ETAP."
Same project, completely different evidentiary value. The second version names a decision, a method, and a number the assessor can weigh. Write every Personal Engineering Activity paragraph this way. Our I-statements guide and personal engineering contribution guide go deeper on converting passive descriptions.
Citing AS/NZS 3000, AS 61000, and AS/NZS 4777.1
Standards are seasoning, not the meal. Reference AS/NZS 3000 (the Wiring Rules) where your cable sizing or protection derives from it, the AS 61000 series where electromagnetic compatibility genuinely shaped a design choice, and AS/NZS 4777.1:2024 for inverter grid connection. Name the standard at the point of the decision it governed, once, and move on. Five standards listed without any tied to a decision read as padding and earn nothing.
Worked Example: An 11kV Substation Design Career Episode
The outline below is a model CDR Engineers Australia built from EA's published guidelines to show the shape of a qualifying power-systems episode. Illustrative, not a case study of a real client. Use it as a skeleton and fill it with your own project.
The engineering problem this episode solves
Context (CE1.1 to CE1.3): a new 11kV/415V zone substation feeding an industrial load, where you were the responsible design engineer. The engineering problem is concrete, sizing the transformer and switchgear for the projected load, calculating fault levels, designing the protection scheme, and confirming LV distribution compliance with AS/NZS 3000. That is a single-line problem an assessor can follow end to end.
Framing design choices as individual evidence
The Personal Engineering Activity (CE1.4 onward) walks through your decisions in sequence: the load flow study you ran and the transformer rating you chose from it; the fault level calculation and the switchgear breaking capacity you specified from it; the protection grading you set; the earthing design you produced. Each paragraph states what you did, why, and the standard or calculation behind it. Where the work was collaborative, write only your part in the first person and say so plainly.
Mapping the episode to the four hardest 233311 elements
A design-led episode feeds the competency elements power engineers usually struggle to evidence. Your fault study and transformer selection demonstrate PE1.2, in-depth technical competence. Because you framed and solved the sizing and protection problem yourself, the same episode covers PE2.1, problem identification, formulation and solution. PE2.4, proficiency in engineering design, follows from the single-line diagram, switchgear specification, and protection settings you produced. Document the compliance reasoning, the safety-in-design decisions, and the limits of your own analysis, and PE3.4, professional and ethical responsibilities, is covered too. One substation project can carry all four.
Summary Statement Mapping for 233311 Applicants
The summary statement is a three-column table: the competency element code, a short statement of how you demonstrated it, and the career episode reference. It is the document EA's assessors read alongside your episodes, and it is where careless applicants unravel a strong CDR. For the packaging and cross-checks, see our submission checklist.
The four elements electrical engineers score weak on
Engineers Australia's competency standard for Professional Engineers is organised into three groups. PE1 Knowledge and Skill Base covers elements PE1.1 through PE1.4. PE2 Engineering Application Ability covers PE2.1 through PE2.6. PE3 Professional and Personal Attributes covers PE3.1 through PE3.6.
For 233311 applicants, four consistently come back thin: PE1.2, PE2.1, PE2.4, and PE3.4. Power engineers evidence PE1.1 and PE1.3 almost by reflex, then under-serve the elements requiring independent design judgement and ethical reasoning. Build at least one episode deliberately to feed those four, the way the substation example above does.
Writing paragraph citations assessors can verify
Every entry in the summary statement points to a specific paragraph, and that paragraph must actually contain the evidence. A valid citation reads: PE1.3, "I selected protection relay settings independently and verified grading through a coordination study," CE2.4. An assessor opens Career Episode 2, paragraph 4, and finds exactly that. A mismatch, where CE2.4 turns out to describe commissioning you witnessed rather than settings you chose, is a hard failure even when the underlying work was real. Cite the paragraph that proves the claim, not the paragraph you wish had proved it. Cross-check every reference before you submit.
CPD and Documents for a 233311 CDR Submission
CPD that counts for electrical engineering practice
Your CPD log is one A4 page in a table with four fields: date, activity, duration in hours, and learning outcome. Cover roughly the past three years and lean toward electrical practice: protection and coordination courses, AS/NZS standards updates (AS/NZS 4777.1:2024 is a timely one), power-system software training, and IEEE or Engineers Australia technical sessions. Generic management webinars fill the page but say nothing about your discipline. Keep one paragraph on format here and use the CPD format and examples guide for the full template.
The document and file-format checklist
Submit each career episode and the summary statement as PDF, set in Times New Roman or Arial at 11 or 12 point, with numbered pages and a consistent file-naming convention as set out in EA's Migration Skills Assessment booklet. Attach your CV, qualifications, English test result, and CPD log. Engineers Australia's current standard CDR assessment fee is AUD 1,034 including GST as of 1 July 2026, with a fast-track surcharge of AUD 396 including GST; our 2026 fee breakdown itemises the rest. Verify the fee in EA's portal before you pay, since it is reviewed annually.
Four Reasons Electrical Engineer CDRs Fail EA Assessment
A CDR for electrical engineer applicants tends to fail for four reasons, roughly in order of frequency.
Summary statement citations that do not match their paragraphs are the most common technical rejection. An entry pointing to a paragraph that does not support the claimed element fails on the spot, regardless of what the underlying project achieved.
Team voice instead of I-statements is a close second. When the assessor cannot isolate your individual contribution, there is nothing to assess, however impressive the project was.
The wrong code is the third trap. Applicants who should have filed under 233411, or who chased a non-existent 233312, get measured against expectations their evidence was never going to meet.
Consensus-only content rounds out the four. An episode that restates textbook theory and standard procedure, with no decision you personally made, reads as generic. For a deeper catalogue of these pitfalls, see our career episode mistakes guide.
EA Assessment Timeline for 233311 Applicants
Once you submit your CDR for electrical engineer, a standard assessment takes several months. Treat any fixed week-count you read on competitor pages with suspicion: EA publishes current processing times in its own portal, and they move. Two things extend the timeline. A request for further information (RFI) pauses the clock until you respond. The fast-track option is widely misunderstood: it gets your file to an assessor sooner, not a guaranteed decision by a fixed date.
One structural change is worth checking before you assume you even need a CDR. Engineers Australia tightened its accredited-qualification pathway in September 2024, which affects some advanced diploma and associate degree holders and can push applicants onto the CDR route. Confirm your pathway against EA's current Migration Skills Assessment guidance rather than an older summary.
FAQs
Does a project management role on an electrical infrastructure project qualify as a career episode for ANZSCO 233311?
Only if you made engineering decisions within it. A role that scheduled, coordinated, and managed budgets without design or analysis work gives an assessor no individual engineering contribution to credit, and it will not qualify. If you also sized equipment, set protection, or resolved a technical design problem, write the episode around that engineering, not the management.
Can I use a solar farm or wind energy project as one of my three career episodes under 233311?
Yes, and it is strong material. Grid-connection and renewable integration work maps cleanly to 233311 when you owned design decisions such as inverter selection, protection, or connection compliance. Cite AS/NZS 4777.1:2024 for inverter connection, and frame the episode around the calculations and choices you personally made.
What is the difference between ANZSCO 233311 (Electrical Engineer) and 233411 (Electronics Engineer) for EA CDR purposes?
233311 covers power: generation, distribution, and control of electric power, such as substation and protection design. 233411 covers electronic components, circuits, and systems, such as PCB and embedded design. Note there is no ANZSCO 233312; that code does not exist in the classification. Choose the code that matches the majority of your evidenced engineering.
Do I need to reference Australian electrical standards like AS/NZS 3000 if my overseas project used different national codes?
No, you write about the standards you actually applied on the project. Use the codes that governed your real work, and where useful, note the Australian equivalent to show you understand the local framework. Do not retrofit AS/NZS references onto overseas work you did not perform to those standards; assessors can tell.
How long should each career episode be for an electrical engineering CDR submission?
Each career episode must be 1,000 to 2,500 words. Aim for the middle of that band: enough room to develop your individual engineering decisions in detail, without padding that dilutes the evidence. Three episodes at that length, plus the summary statement and CPD, form the complete report.
Browse electrical engineer CDR samples to see qualifying episodes in full, or get a no-obligation draft review from CDR Engineers Australia so a specialist can flag code, citation, and I-statement issues before EA does.