Engineers Australia CDR Career Episodes: From Project Story to Engineering Evidence

What the three Career Episodes need to achieve

The three episodes should collectively provide evidence of your engineering knowledge and skill. Engineers Australia’s current guidance focuses on the engineering methods you selected, why you selected them, how you analysed results and the engineering evidence supporting your work.

That means a strong episode needs more than “I was responsible for design”. It should explain the engineering problem, the constraints, the analysis you personally performed, the decisions you made, the result and how you verified the result.

Choose episodes for evidence diversity, not prestige

Three versions of the same routine activity can make competency mapping difficult. Look for episodes that reveal different dimensions of your engineering practice.

For example, one episode may show design calculations and equipment selection, another may show failure analysis and redesign, and a third may show system optimisation, multidisciplinary coordination and commissioning. The right mix depends on your genuine experience and engineering category.

Use an engineering evidence chain

• Context: What engineering system, asset, product or process was involved?
• Problem: What technical performance, safety, reliability, design or operational issue required engineering work?
• Data: What measurements, drawings, specifications, operating trends or design inputs did you use?
• Method: What calculations, models, standards, design methods or engineering principles did you apply?
• Judgement: What options did you compare and why did you select or reject them?
• Personal action: What did you personally calculate, design, analyse, specify, review or decide?
• Verification: How did you test, commission, simulate, inspect or compare the result?
• Outcome and learning: What changed, and what engineering knowledge did you strengthen?

The difference between project activity and engineering contribution

“The project installed variable-speed drives on chilled-water pumps” describes project activity. It does not establish the applicant’s engineering contribution.

A first-person engineering account might explain that the applicant plotted measured pump operating points against pump curves, estimated the system resistance under representative loads, compared impeller trimming, pump replacement and VFD control, and selected a control approach after a life-cycle energy comparison. The value is in the reasoning, not in adding technical vocabulary.

Calculations, designs and technical evidence

Engineers Australia’s Career Episode guidance asks for sufficient engineering evidence and gives examples such as calculations, designs and data. Include evidence that is genuinely connected to your work and explain what it demonstrates.

Do not paste unexplained formulas or screenshots simply to make an episode look technical. State the input assumptions, the method, the result and how the result affected your engineering decision. If software was used, explain what you modelled, what result you reviewed and how you checked whether the result was reasonable.

First person must show ownership

Use “I” where you are describing your work, but go further. “I attended a design review” is participation. “I presented my pressure-drop calculation, challenged the proposed valve selection because the available pump margin was insufficient, and recommended the lower-loss option” shows identifiable engineering contribution.

Be precise about collaboration. Engineers work in teams. You do not need to pretend you worked alone. Explain your responsibility and distinguish your analysis from decisions made by a supervisor, client, vendor or multidisciplinary team.

Paragraph numbering and the Summary Statement

Number the Career Episode paragraphs consistently because the Summary Statement maps competency elements to the paragraphs where the evidence appears. Engineers Australia describes the Summary Statement as an overview of competencies demonstrated in the Career Episodes.

Do not write the Summary Statement as a second set of Career Episodes. Complete the episodes first, identify the strongest evidence paragraphs, then map competency elements to those paragraphs. If a competency is difficult to map, the right response may be to revisit the underlying episode evidence rather than forcing an unrelated paragraph into the table.

Before you finalise a Career Episode

• Can a reader identify exactly what I personally engineered?
• Have I explained at least one meaningful technical problem or constraint?
• Are calculations, designs, models or data connected to a decision?
• Have I explained why I selected a method or option?
• Did I describe verification, testing, commissioning or another form of result checking?
• Are team actions clearly separated from my own contribution?
• Are dates, employer details and project facts consistent with my other documents?
• Can the episode support competency mapping without stretching the meaning of the paragraph?