Most Engineering Technologist CDR rejections do not come from weak English or thin projects. They come from claiming Professional Engineer competency in a report that Engineers Australia (EA) assesses against a lower and differently scoped standard. An applicant writes a career episode about solving a complex engineering problem from first principles; the assessor reads it against the Technologist benchmark, and the gap between what was claimed and what the standard asks for sends the file back for review.
This guide reads the EA Engineering Technologist competency standard sub-element by sub-element, shows where the Technologist scope line sits relative to Professional Engineer, and names the exact places applicants over-reach. It assumes you have already read the EA website and want the working interpretation of the standard, not another format walkthrough. For document formatting, page order, and file structure, see our CDR report format guide for Engineering Technologist. For the fundamentals shared across every EA category, the complete 2026 CDR guide covers the common ground so this page can stay on competency strategy.
What ANZSCO 233914 Engineering Technologist Actually Covers
ANZSCO 233914 is the Engineering Technologist occupation code, and Engineers Australia is the assessing authority for it under the migration skills assessment. The code covers engineers who apply established methods, published codes, and proven technologies to practical problems: control and instrumentation, manufacturing and production, building services, materials, and similar applied fields. Applied competence with known solutions defines the category, not the origination of new engineering knowledge.
Disciplines and Tasks EA Maps to Occupation Code 233914
The occupation sits between associate-level roles and the Professional Engineer codes. EA does not place you in 233914 by your job title. It reads the competency evidence in your report. A candidate carrying a "design engineer" business card whose actual contribution is configuring standard PLC libraries and applying vendor design tables is, in competency terms, a Technologist, and the assessment treats the work that way regardless of the title on the payslip. For the full mapping of codes to disciplines, see our ANZSCO codes applicant guide.
Technologist, Associate, and Professional Engineer: Three Standards
Three occupational categories produce three separate Stage 1 competency standards. The Associate standard sits below, typically tied to a two-year advanced diploma. The Professional Engineer standard sits above, typically a four-year Washington Accord degree. Engineering Technologist sits in the middle and aligns with the Sydney Accord. According to Engineers Australia, the organisation has been a Sydney Accord signatory since 2001, and that accord defines Technologist graduate competency as broadly-defined problem solving, distinct from the Washington Accord's complex problem solving for Professional Engineers. That single contrast, broadly-defined versus complex, is the hinge the entire assessment turns on. If you are still deciding which category fits, our skills assessment pathways guide walks through the entry points.
The EA Competency Standard at Technologist Scope
The Engineering Technologist Stage 1 standard contains 16 elements grouped into three clusters. The prefix matters: EA labels Technologist sub-elements ET1, ET2, and ET3, not the PE prefix used for Professional Engineer. Several competitor pages reuse PE labels for every category. That is wrong for 233914, and copying it into your Summary Statement signals you worked from the wrong standard. Verify the exact descriptive wording of each sub-element against the current EA competency standard booklet before you quote it. The numbering below is stable across sources; the precise phrasing is EA's to define, so treat the descriptions here as the working scope, not a substitute for the booklet.
ET1: Knowledge and Skill Base
ET1 runs six sub-elements from ET1.1 to ET1.6, each with a distinct scope.
ET1.1 covers the underpinning sciences and engineering fundamentals relevant to your specialist field. Demonstrating this means showing that your decisions rest on sound physical or mathematical principles, not just on habit or vendor guidance.
ET1.2 addresses the supporting mathematics and computation methods. At Technologist level, competence means applying appropriate analytical techniques, selecting the right method for a given calculation, and interpreting the result correctly.
ET1.3 requires in-depth command of an established specialist body of knowledge. The operative word is command, not creation. You show that you understand and can apply the knowledge that already exists in your field. This is the sub-element applicants most often inflate, rewriting textbook application as original synthesis.
ET1.4 covers awareness of how your specialist field develops and the directions it is moving. A brief account of a standard update you tracked, a technology shift you responded to, or an industry change you planned around satisfies this at Technologist scope.
ET1.5 addresses your understanding of the engineering design context: how a component or sub-system fits into a broader engineering system and the constraints that shape design decisions.
ET1.6 covers the norms, principles, and practices of responsible and professional engineering, including safety, environmental considerations, and legal obligations relevant to your work.
ET2: Engineering Application Ability
ET2 has four sub-elements, ET2.1 to ET2.4, and this is where the assessment is won or lost.
ET2.1 covers applying established engineering methods to broadly-defined problems. The scope line lives here: a Technologist selects and applies a known method to a problem that is well framed by existing codes and practice, rather than deriving a novel approach for a problem with no established solution.
ET2.2 concerns fluent use of engineering tools, techniques, and resources. Hands-on command of the instruments, software, and test equipment your field relies on is the evidence; familiarity alone is not enough.
ET2.3 addresses engineering synthesis and design. At Technologist scope, this means component and sub-system implementation within an existing design framework, not system-wide design authority.
Under ET2.4, the focus is the systematic conduct of engineering projects: planning, monitoring, managing risk, and delivering outcomes to specification.
A worked example makes the scope concrete. Suppose you commissioned an industrial control system for a water treatment plant. You configured the PLC using standard ladder logic and function blocks, wired the I/O to the P&ID, tuned the loops against the vendor's recommended ranges, and validated the sequence against the site's operating specification. When you map the work to the standard, selecting and applying the established PLC programming method and the P&ID convention is ET2.1 evidence. The fluent, hands-on use of the programming environment, the loop-tuning tools, and the commissioning test set is ET2.2 evidence. That is a clean Technologist claim. It becomes an over-claim the moment you describe the same work as originating a novel control architecture, because designing the plant's overall control philosophy would be ET2.3 authority you did not hold.
ET3: Professional and Personal Attributes
Six sub-elements, ET3.1 to ET3.6, span the professional conduct cluster. Applicants routinely under-serve these, treating ET3 as filler. Assessors do not.
ET3.1 covers ethical conduct: recognising professional obligations and acting on them, including disclosing conflicts and upholding public safety.
ET3.2 addresses professional communication. Written reports, oral briefings, and technical documentation directed at both engineering and non-engineering audiences all serve as evidence.
ET3.3 requires a proactive and confident professional demeanour: showing initiative, accepting responsibility, and demonstrating sound professional judgment.
ET3.4 covers disciplined use of information: identifying what you need, sourcing it reliably, and applying it systematically rather than selecting sources casually.
ET3.5 addresses self-management: organising your own workload, tracking commitments, and delivering to schedule and quality expectations.
ET3.6 covers effective work within a team, including awareness of each member's contribution, clear communication of your own role, and the ability to manage or contribute to a professional team context.
A career episode that never shows you weighing a safety trade-off, documenting a decision, or handling a disagreement leaves several ET3 rows unsupported, and unsupported rows fail.
The Three Documents in an Engineering Technologist CDR
Every 233914 submission carries three components: three career episodes, one Summary Statement, and a CPD list. The episodes supply the evidence, the Summary Statement indexes it against the 16 elements, and the CPD log shows continuing learning. Break any link and the assessment stalls.
Career Episode Length and Personal Contribution
Each of the three career episodes runs 1,000 to 2,500 words in first-person narrative. Length is not the point; personal contribution is. An assessor reads the episode looking for what you did, decided, calculated, and delivered. That is why the numbered paragraph structure and the discipline of writing in the first person matter so much. A focused 1,600-word episode with clear I-statements is more useful than a padded 2,400-word one. Our career episode format guide and the broader career episode guide cover paragraph numbering and narrative flow.
Summary Statement Mapping Across All 16 ET Elements
The Summary Statement is a three-column table: the ET sub-element number, the exact career episode paragraph where you demonstrated it, and a short description of how. Every one of the 16 ET sub-elements gets its own row, and every row must point to a specific numbered paragraph in one of your episodes. A blank row is a structural failure, not a minor omission. If ET2.4 has no paragraph reference, ET2.4 was not demonstrated, and the assessor cannot credit it. Our Summary Statement service goes deeper on the mechanics of building each row correctly.
The CPD Log and the 150-Hour Myth
The CPD list for Stage 1 CDR assessment has no minimum hour count. EA expects a genuine, varied record of continuing learning: formal training, industry seminars, professional reading, and structured on-the-job learning all count. The 150-hours-over-three-years figure repeated across CDR service sites is the Chartered and NER membership CPD requirement, a completely separate process that has nothing to do with a Stage 1 skills assessment. For the CDR submission itself, format is what matters: a single A4 page in a table with at least four columns covering the activity, its date, its duration, and the organising body.
Choosing and Framing Career Episodes at Technologist Level
Which Projects Count as Applied Engineering Evidence
The strongest Technologist episodes describe applied engineering with a clear technical spine: commissioning equipment, implementing a design to an established standard, troubleshooting a plant fault, or delivering a defined component of a larger system.
Pure coordination, procurement, or supervision rarely carries an episode. The assessor needs engineering decisions to credit, and "I managed the subcontractors" produces none. Pick projects where you can point to a calculation you ran, a standard you applied, or a fault you diagnosed and fixed.
I-Statements and Why Vague Team Contributions Fail
"The team designed the pumping station" tells an assessor nothing about your competency. "I sized the pump against the system head curve and selected the impeller from the manufacturer's chart" identifies the sub-elements you can claim. Career episodes must be written in the first person, and every technical sentence should carry an I-statement that isolates your contribution from the group's. Vague collective phrasing is the single most common reason a technically sound project produces a weak episode. Our I-statements guide shows the pattern in detail.
Technologist vs Professional Engineer CDR: Where the Scope Line Sits
This is the comparison competitor service pages skip, so it is worth setting out precisely. The table below is CDR Engineers Australia's reading of the two public competency standards, pairing the Technologist sub-element with its Professional Engineer counterpart so you can see where one scope ends and the other begins. Use it to calibrate your language, not to inflate it.
Competency area | Engineering Technologist (Sydney Accord) | Professional Engineer (Washington Accord) |
|---|---|---|
Problem type (ET2.1 / PE2.1) | Broadly-defined problems addressed with established methods, codes, and proven techniques | Complex, ill-defined problems requiring first-principles analysis and novel approaches |
Knowledge base (ET1.3 / PE1.3) | In-depth command of an established specialist body of knowledge | Knowledge at the frontier of the discipline, including research directions |
Design and synthesis (ET2.3 / PE2.3) | Component and sub-system implementation within an existing design framework | System-wide design authority and synthesis of the overall solution |
Method origin | Selects and applies known solutions | Derives solutions where no standard method exists |
Read the ET2.1 row carefully, because it decides most files. A Technologist who applied the standard and a Professional Engineer who wrote a new one can describe the same project, yet only one description matches the 233914 standard. Frame your commissioning or implementation work as skilled application of established practice, and it lands as strong ET evidence. Frame it as original problem-solving from first principles, and you have written a Professional Engineer episode that fails when assessed at Technologist scope.
EA Fees, Timeline, and Submission for ANZSCO 233914
Current Assessment Fee and the Fast-Track Option
As of the July 2026 EA fee schedule, the standard CDR skills assessment fee is AUD 1,034 including GST, up from the prior AUD 1,001. The fee schedule does not charge Engineering Technologist and Professional Engineer differently; both pay the standard CDR rate. Priority processing adds AUD 396 including GST from July 2026.
Read the fast-track terms carefully. The surcharge guarantees only that your file is assigned to an assessor within 20 business days; it is non-refundable and does not shorten the assessment itself. If you plan to include a skilled employment assessment, that combined pathway runs AUD 1,512.50. Full figures and effective dates are on our EA CDR fees breakdown for 2026.
After You Submit: Processing Time and Information Requests
Standard CDR processing runs roughly 18 to 24 weeks. Fast-track buys faster queue placement, not a faster verdict, so plan around several months either way. If an assessor needs more information, they issue an additional information request rather than rejecting outright, giving you the opportunity to close a gap before a final decision. Our assessment timeline guide tracks current processing windows.
Why Engineering Technologist CDRs Get Rejected
Claiming Elements Beyond Technologist Scope
Over-claiming Professional Engineer competency in a Technologist report is the leading documented cause of failure in this category. Three sub-elements are the usual hotspots. ET1.3 gets inflated when established textbook knowledge is written up as original synthesis. ET2.1 goes the same way when routine application of a known method is reframed as novel, complex problem-solving. ET2.3 fails when component-level implementation is presented as system-wide design authority.
Audit your episodes for these three specifically. If a sentence sounds like it belongs in a Professional Engineer report, it probably fails you here.
Career Episodes With No Measurable Personal Contribution
An episode built on "we" and "the team" with no isolated engineering decisions cannot support the ET2 rows. The assessor has nothing individual to credit. The fix is sharper attribution, not more words. Name the calculation, the standard, the setting you chose, the fault you traced.
Summary Statement Gaps That Break the Competency Trail
A vague Summary Statement row that points to a paragraph that does not actually demonstrate the claimed sub-element snaps the competency trail and leaves the assessor unable to validate the claim. Check every row against the paragraph it cites before you submit, and confirm all 16 are genuinely evidenced. A single unsupported row can stall an otherwise complete application.
Frequently Asked Questions About Engineering Technologist CDR
What is the difference between an Engineering Technologist CDR and a Professional Engineer CDR?
They are assessed against different Stage 1 standards. The Engineering Technologist standard (ET1 to ET3) aligns with the Sydney Accord and expects broadly-defined problem solving using established methods. The Professional Engineer standard aligns with the Washington Accord and expects complex, first-principles problem solving. The document structure is similar, but the competency scope you must demonstrate is not.
How many career episodes are required for ANZSCO 233914 assessment?
Three. Every Engineering Technologist CDR needs three career episodes drawn from your engineering experience, each demonstrating your personal applied contribution, plus one Summary Statement and one CPD list.
What word count should each career episode be for an Engineering Technologist CDR?
Between 1,000 and 2,500 words each, in first-person narrative with numbered paragraphs. Aim for enough depth to isolate your technical decisions, not maximum length.
Can I apply under ANZSCO 233914 with a 3-year bachelor of engineering degree?
Usually yes. A three-year bachelor or a Sydney Accord-recognised technologist qualification typically meets the educational entry point for Engineering Technologist. Keep in mind that EA assesses the competency evidence in your CDR content, not the degree title alone, so the report still has to demonstrate all 16 ET sub-elements.
Which competency elements do Engineering Technologists need to map in the Summary Statement?
All 16: ET1.1 through ET1.6, ET2.1 through ET2.4, and ET3.1 through ET3.6. Each sub-element requires its own row in the Summary Statement table, with a specific career episode paragraph reference and a brief description of the evidence. No row can be left blank. If a sub-element has no paragraph reference, it has no evidence, and the assessor cannot credit it.
Does the Engineering Technologist CDR CPD log require a minimum number of hours?
No. The Stage 1 CDR CPD log has no minimum hour count. EA expects a varied, genuine record of continuing learning on a single A4 page in a table with at least four columns. The 150-hour figure some sites cite belongs to Chartered and NER membership, which is a separate process entirely.
Ready to see the standard applied end to end? Browse CDR Engineers Australia's Engineering Technologist CDR samples to see exactly how each ET competency sub-element is mapped to career episode paragraphs in a complete, assessed submission.