Two applicants can hold the same pressure vessel design role for the same three years. One writes up a defined engineering problem, the analysis that resolved it, and the trade-off behind the final specification. The other describes a project. The first passes; the second collects a request for additional information, or worse. That single distinction, engineering decisions versus project narration, is what a CDR for mechanical engineer assessment turns on.
This guide is written for qualified mechanical engineers assessing under ANZSCO 233512 from outside Australia. Every claim here is grounded in mechanical practice, not advice that fits any discipline. A submission succeeds on discipline-specific evidence: which project types map to which competency elements, why maintenance and production roles trip so many capable engineers, and how the summary statement, more than the prose, decides your outcome.
What ANZSCO 233512 Covers and Why It Shapes Your Entire CDR
Start with the wording, because it sets the scope of every career episode you write.
How Engineers Australia reads the mechanical engineer occupation
ANZSCO 233512 covers an occupation that "plans, designs, organises and oversees the assembly, erection, commissioning, operation and maintenance of mechanical and process plant and installations" at Skill Level 1. Read that verb list carefully. Design sits near the front and carries the most weight. An episode anchored on operation and maintenance alone sits at the thin end of the definition, and you have to work harder to prove the engineering judgment EA is looking for.
The adjacent codes that catch applicants
Three neighbouring codes pull work that looks mechanical on paper:
233511 Industrial Engineer investigates and reviews the utilisation of personnel, facilities, equipment, and materials, and current operational processes, to recommend improvements in the quality and efficiency of operations. Engineers whose work centres on process and operational efficiency rather than mechanical equipment design may be read here.
233513 Production or Plant Engineer plans and coordinates the construction, modification, and maintenance of industrial equipment. Plant-side operations engineers often belong under this code.
233914 Engineering Technologist applies existing engineering technology to testing and implementation across several disciplines, and sits at Skill Level 1 but below the full professional engineer standard EA expects for 233512.
The decision rule is straightforward. If the bulk of your evidence shows you designing or analysing mechanical equipment against engineering standards, 233512 fits. If it shows you optimising a production line or running a plant, expect the assessor to test whether another code describes you better.
Which pathway applies and what it costs in 2026
Most engineers trained outside the Washington, Sydney, or Dublin Accords use the Competency Demonstration Report (CDR) pathway, with Engineers Australia as the sole assessing authority for ANZSCO 233512. As of the July 2026 fee schedule, a standard CDR assessment costs AUD 1,034 including GST (AUD 940 excluding GST). Fast-track adds a non-refundable AUD 396 surcharge and commits EA to assigning an assessor within 20 business days, though not to a final decision in that window. A combined CDR and relevant skilled employment assessment runs to AUD 1,512.50 including GST. Standard processing commonly runs 10 to 16 weeks.
Choosing Three Career Episodes That Prove Mechanical Competency
Three career episodes are required, each 1,000 to 2,500 words, and each drawn from a distinct project. The instinct is to pick your three biggest projects. The better filter is which three, taken together, let you demonstrate the widest spread of competency elements with real engineering decisions attached.
Not every mechanical project carries the same evidentiary weight. The table below maps common project types against the three competency stages, so you can see before you write which elements a given project naturally supports. It is derived from the EA competency framework, not from competitor samples.
Project type | PE1 (Knowledge & Skill Base) | PE2 (Engineering Application) | PE3 (Professional Attributes) |
|---|---|---|---|
Pressure vessel design (AS 1210 / ASME BPVC) | PE1.1, PE1.2, PE1.3 | PE2.1, PE2.3, PE2.4 | PE3.2 |
FEA structural or thermal analysis | PE1.3 | PE2.3, PE2.4 | PE3.2 |
HVAC system design | PE1.1, PE1.2 | PE2.1, PE2.4 | PE3.1, PE3.2 |
Rotating equipment design | PE1.2, PE1.3 | PE2.3, PE2.4 | PE3.2 |
Heat exchanger specification | PE1.1, PE1.2 | PE2.1, PE2.4 | PE3.2 |
Manufacturing process engineering | PE1.3 | PE2.3 | PE3.1, PE3.3 |
Maintenance troubleshooting (non-routine) | PE1.2 | PE2.3 | PE3.3, PE3.5 |
Read the table by column, not just by row. A pressure vessel design episode reaches across all three stages on its own; a maintenance episode clusters in PE3 and touches PE2 only when a non-routine failure forced genuine analysis. That asymmetry is the whole game.
Making maintenance and reliability roles count
A maintenance or reliability role can anchor a career episode, but it fails by default for a structural reason: task completion and PE3 attributes are easy to show, while PE2.1 stays empty. PE2.1 rewards problem identification and formulation with original analysis. Following a CMMS work order, replacing a worn bearing, and closing the ticket demonstrate none of that, however competently done.
The fix is to isolate one non-routine failure inside the role and build the episode around it. A qualifying version reads like this: recurring seal failures on a pump traced to a shaft misalignment the standard procedure never checked; you ran a vibration analysis, quantified the misalignment against the manufacturer's tolerance, chose a laser alignment correction over a coupling redesign on cost and downtime grounds, and verified the result held. Problem formulation, discipline-specific judgment, and a weighted decision in one paragraph. Routine upkeep, however skilled, is not that.
Reframing manufacturing and production experience
Manufacturing and production management episodes need the most rework before submission, for a related reason. Scheduling, throughput management, and yield improvement are real work, but they tend to evidence PE3 professional attributes and operational outcomes rather than PE2.4 design. Map a line-balancing project to PE2.4, and the assessor will note that you managed production rather than designed equipment from requirements through verification. When manufacturing is your strongest domain, centre the episode on a specific engineering design decision inside it: a fixture designed to a load case, a tooling change you analysed against a defined mechanical constraint, a process you re-engineered with quantified results.
Writing Career Episodes That Survive EA Assessment
Assessors now read for engineering judgment and clearly attributed technical responsibility ahead of grammatical polish, and they frequently open the summary statement first to check whether your mapped paragraphs actually own the competency you claim.
Show the decision, not the deliverable
Four writing patterns reliably draw an adverse assessment: a collective voice that hides your individual contribution, background description standing in for engineering decisions, assertions with no method or process stated, and technical claims with no named standard, code, or calculation behind them. Each is the same defect wearing different clothes. Your evidence of competence is the decision and its basis, never the outcome on its own.
Weaving in calculations, FEA, and standards without overstuffing
Technical evidence separates approved mechanical CDRs from rejected ones, but volume is not the point. One well-shown calculation that drives a decision beats a wall of figures. The pattern that passes: name the standard, state the result, identify the decision and the trade-off. For a pressure vessel, that means applying AS 1210 to calculate the required shell thickness for the design pressure, selecting a plate grade and corrosion allowance on that basis, then weighing a thicker shell against the added weld inspection and material cost. Three sentences, and several competency elements are visible.
FEA earns its place only under a specific test. Naming ANSYS, SolidWorks Simulation, or Abaqus proves nothing on its own. FEA counts as competency evidence when you select the constitutive model, define the boundary conditions, justify the mesh density, interpret the stress or thermal results against a design criterion from a named standard, and then make a design decision on that basis. "FEA was used to confirm the design" is visualisation, and it maps to nothing. "Peak von Mises stress exceeded the yield criterion at the nozzle junction, so I added a reinforcing pad and re-ran the model" is engineering.
I-statements that pass the personal contribution test
Every I-statement must show what you personally analysed or decided, not what the team or the project delivered. Engineers Australia flags collective constructions; "we optimised" and "the team delivered" tell the assessor nothing about you. Write "I calculated," "I selected," "I specified," "I rejected option B because." The personal engineering contribution is the unit of evidence, and vague verbs like "assisted" and "was involved in" rank among the leading rejection causes precisely because they surrender ownership.
Mapping Competency Elements in the Summary Statement
The summary statement is where most CDR for mechanical engineer applications are actually won or lost. Every one of the 16 competency elements must be mapped to specific numbered paragraphs in your career episodes using CE notation, and the assessor checks that each mapped paragraph genuinely demonstrates the element claimed.
The Stage 1 and Stage 2 elements that carry mechanical work
Across the three stages sit 16 elements: six in PE1 (Knowledge and Skill Base, PE1.1 to PE1.6), four in PE2 (Engineering Application Ability, PE2.1 to PE2.4), and six in PE3 (Professional and Personal Attributes, PE3.1 to PE3.6). For mechanical work, the load-bearing ones are PE1.2 (in-depth technical competence in the discipline), PE1.3 (command of engineering analysis and design tools), PE2.1 (problem formulation with original analysis), PE2.3 (systems approach with quantified risk and weighted alternatives), and PE2.4 (design from requirements through verification). Design and analysis episodes should hit all five, which is why they make stronger sources than operations episodes.
Three mapping errors that produce an ANZSCO 233512 rejection
The prose can be sound and the mapping still sink you. Three errors recur:
1. Mapping routine maintenance to PE2.1 with no evidence of original problem formulation. A checklist is not original analysis, and an assessor will note the distinction.
2. Mapping a manufacturing operations episode to PE2.4 when the role was scheduling or throughput, not engineering design. PE2.4 covers design from requirements through verification; production management does not reach it.
3. Under-claiming: citing an FEA or calculation result but mapping it only to PE1.3 (tools) when the decision it drove also satisfies PE2.3 (quantified risk with weighted alternatives). Leaving an element undemonstrated is as fatal as claiming one you did not earn.
Our summary statement mapping guide works through the CE notation in full.
Format and Document Requirements for ANZSCO 233512 Applications
What each career episode must contain
Each of the three career episodes runs 1,000 to 2,500 words in first person, structured as introduction, background, personal engineering activity, and summary. The background sets the project and your role briefly; the personal engineering activity is where the marks are, and it should dominate the word count. Every submission is screened through Turnitin, and high similarity or AI-generated content produces an unsuccessful outcome, a potential 12 to 36 month reapplication ban, and referral to the Department of Home Affairs. Write it yourself, or have it written to your own genuine project record.
CPD when you have little formal post-graduation training
The CPD list is capped at a single A4 page, and many mid-career mechanical engineers worry here because they hold few formal certificates. EA does not require them. Self-directed standards study (reading AS 1210 or the relevant ASME code for a live project), in-house technical training, supplier and equipment commissioning sessions, industry webinars, and mentoring all count. List the activity, the year, and the hours; keep the total to one A4 page. Depth of formal training matters far less than a credible record of staying current.
What Distinguishes a Passing Mechanical Engineer CDR Sample
Reviewing samples helps only if you read them for the right thing. A passing CDR for mechanical engineer applications is not the one with the most impressive project or the cleanest English. In every career episode, you should be able to identify a defined engineering problem the applicant personally recognised, the mechanical analysis applied, the standard or calculation that grounded the decision, and the trade-off weighed before committing. Weak samples describe; strong samples decide. When you next read a CDR sample, track how many sentences show a decision and its basis against how many just report what happened. That ratio is what the assessor is scoring.
Frequently Asked Questions: CDR for Mechanical Engineers
Can a maintenance engineer submit a CDR under ANZSCO 233512?
Yes, provided the career episode centres on a specific non-routine engineering problem you identified and solved, not routine upkeep. A maintenance role qualifies when you isolate a failure mode, apply mechanical analysis such as fatigue, vibration, or corrosion assessment, and select a solution against alternatives. An episode that reads as a log of parts replaced does not qualify, regardless of technical complexity.
Which mechanical projects produce the strongest career episodes?
Design and analysis projects with clear engineering decisions: pressure vessel design, HVAC system design, heat exchanger specification, rotating equipment design, and FEA-based structural or thermal analysis. These naturally reach PE1.2, PE2.1, and PE2.4 in a single episode. Operations and maintenance projects can work too, but only with a defined engineering problem at their centre.
How do I show thermodynamic or fluid mechanics work in an episode?
Show the analysis driving a decision. For a heat exchanger, state the duty and approach temperature you sized to, the correlation or method you applied, and why you chose a given surface area or configuration over another. For a piping system, calculate the pressure drop, justify the pump or pipe size it dictated, and name the trade-off. The competency lives in the reasoning, not the topic.
Does FEA software like ANSYS count as competency evidence?
Only when you drove the analysis, not just the software. FEA in ANSYS, Abaqus, or SolidWorks Simulation counts when you select the model, define boundary conditions, justify the mesh, interpret results against a design criterion, and make a design decision on that basis. Using it to render or to confirm a pre-sized part does not satisfy PE1.3 or PE2.4.
Can I use the same project for two career episodes?
No. Each of the three career episodes must come from a distinct project. Two episodes drawn from separate phases of a very large program may be acceptable if each covers genuinely different engineering work and stands alone, but three clearly different projects are the safer path.
What ANZSCO code applies if I specialise in HVAC systems?
HVAC and building services engineering fall under ANZSCO 233512 as a mechanical engineering specialisation, not a separate code. Design HVAC systems, size equipment, and analyse thermal loads, and you sit squarely within 233512. No distinct HVAC ANZSCO code exists to assess under.
Before you commit three projects to paper, it helps to see the pattern in finished work. Read through the CDR samples to see how strong mechanical engineering career episodes are structured, or look at what the CDR writing service covers before you start.