An Engineers Australia assessor can reject a technically strong mining engineer inside the first career episode, not because the work was weak, but because the writing described a mine's operations instead of the applicant's engineering decisions. That failure mode sits behind most rejected ANZSCO 233611 applications. A strong CDR for mining engineer candidates turns site experience into evidence of engineering judgment, and this guide is written for overseas-qualified engineers with three to ten years of site or project experience who need the EA Migration Skills Assessment and keep being told their work reads as operational management.
Who Needs a CDR Under ANZSCO 233611
ANZSCO 233611 covers Mining Engineer (excluding Petroleum). The CDR pathway applies when your engineering qualification did not come from a Washington Accord signatory institution. A degree accredited under that accord usually triggers a formal qualifications assessment instead, so confirm your institution's status before writing a word.
The code boundary matters more in mining than in most disciplines because the adjacent codes sit close. Geotechnical work centred on slope stability and ground support can point toward 233212; petroleum reservoir work toward 233612; extractive metallurgy toward the metallurgist stream. EA assesses your primary engineering duties, not your job title. Choose 233611 only when mine design, planning, or extraction engineering was the core of what you actually did. Our ANZSCO codes guide walks through the boundary tests when the split is genuinely unclear.
Budget for the assessment while you are at it. Per Engineers Australia's July 2026 fee schedule, a standard CDR assessment costs AUD $1,034 including GST; the combined CDR and Relevant Skilled Employment assessment is AUD $1,512.50. The fast-track surcharge of AUD $396 buys an assessor within 20 business days and is non-refundable whatever the outcome. It rewards a clean application, not a rushed one.
The 16 Elements Mining Site Engineers Struggle to Evidence
The MSA booklet requires you to evidence all 16 Professional Engineer competency elements at least once across three career episodes, then map each one in the summary statement. They group into PE1 Knowledge and Skill Base (PE1.1 to PE1.6), PE2 Engineering Application Ability (PE2.1 to PE2.4), and PE3 Professional and Personal Attributes (PE3.1 to PE3.6).
Mining site engineers rarely fail on knowledge. The PE2 application elements are where applications collapse. PE2.3 asks for a systems approach with risk quantified and alternatives weighed before committing to a solution; PE2.4 asks for documented design proficiency from requirements specification through to verification. A shift-based site narrative records what happened at the pit, not the decision process that produced the outcome, so the elements carrying the most assessment weight go unproven.
Three more slip through even in careful applications: PE1.4 (engineering's place in society), PE3.3 (a creative or innovative approach), and PE3.6 (capacity for lifelong learning). Site work evidences all three, but only when you frame it deliberately rather than letting the operational narrative swallow the engineering.
Choosing Career Episodes That Prove Engineering Judgment
Start from the gap, not the project. The elements hardest to evidence from continuous site work are PE2.1 (problem identification), PE2.3, and PE2.4, so choose episode subjects that force you to show a defined problem, a weighed set of options, and a verified result. Three mining project types do this reliably.
Blast design: what the episode must show beyond the plan
A blast design episode fails when it reproduces the blast plan and stops. Passing requires the reasoning underneath. Show how you calculated burden and spacing for the measured rock density and the excavator's dig geometry; how you set a maximum instantaneous charge to hold ground vibration within the limit imposed by the relevant state mine safety legislation, such as Queensland's Coal Mining Safety and Health Act 1999 or Western Australia's work health and safety mining framework; and how post-blast fragmentation analysis confirmed whether the design worked. In a Hunter Valley open-cut coal pit or a Pilbara iron ore operation, that single design activity can carry PE2.1, PE2.3, and PE3.4 together.
Mine planning: carving an episode from a multi-year role
Mine planning optimisation is the strongest source of PE2.3 and PE2.4 evidence, but only when you resist writing the whole schedule. Anchor the episode to one defined problem: a pushback redesign, a cutoff grade change, a haul road realignment that recovered lost productivity. State the inputs you worked from, the constraints you were bound by, the options you modelled in Vulcan or Datamine, and the outcome you validated. That discipline turns three years of planning work into one assessable engineering decision.
Environmental rehabilitation: covering the sustainability elements
Rehabilitation design is the cleanest route to PE2.2 (social and environmental responsibility) and PE3.1 (ethical and legislative awareness), the elements blast and planning episodes tend to leave thin. Erosion modelling on a final landform, revegetation specified to a measurable standard, and a closure design tied to statutory obligations read as engineering. A description of a rehabilitation programme you helped run does not.
Blast Design vs Mine Planning vs Rehabilitation: Coverage and Gaps
Choose your three episodes so their coverage overlaps as little as possible.
Blast design is strongest on PE1.2, PE2.1, PE2.3, PE2.4, and PE3.4. It leaves the social and environmental elements, PE2.2 and PE3.1, almost untouched. Mine planning reinforces PE2.3 and PE2.4, adds PE1.3 (in-depth discipline knowledge) and PE3.5 (team leadership), yet typically runs light on regulatory and environmental responsibility. Environmental rehabilitation fills exactly those gaps, PE2.2, PE3.1, and PE3.4, while offering little quantitative design synthesis on its own.
That is why the trio works as a set. One episode's blind spot is another's strength. Plan two blast-heavy episodes and you will finish with a summary statement full of holes on the professional-attribute side, and those holes are what assessors flag first.
The FIFO Reframe That Turns a Failing Episode Into a Pass
Fly-in fly-out roles fail as episodes for a structural reason: continuous site employment has no natural project boundary, so applicants default to describing the roster. What they supervised. What they coordinated. What production targets they hit. That reads as operational management, and operational management is not engineering competency.
Here is the same Pilbara blasting activity written both ways.
Operational version: "During my FIFO roster at an iron ore operation, I was responsible for the drill-and-blast crew. I supervised daily blasting, ensured production targets were met each shift, and coordinated with the pit supervisor to keep the excavators fed. I maintained compliance with site procedures and reported outcomes to the mining superintendent."
An assessor reads that and sees a supervisor. PE2.1, PE2.3, and PE2.4 are all absent: no problem is identified, no alternatives are weighed, no design is verified.
Engineering-contribution version: "I identified that oversized fragmentation in the northern pit was raising excavator dig times and truck cycle times. I recalculated burden and spacing using the measured rock density and the bucket geometry, modelled three pit-zone initiation alternatives in Datamine, and set the maximum instantaneous charge to hold ground vibration below the regulated limit under Western Australia's work health and safety mining regulations. After the shot, I analysed the muckpile size distribution and confirmed dig rates recovered to target."
Same roster. Same site. PE2.1 (the defined problem), PE2.3 (options modelled and constrained), and PE2.4 (a verified result) are now all on the page.
The supervision and reporting lines were cut. Every engineering decision that was previously implied was made explicit. That is the entire reframe.
Writing Career Episodes for a Mining Engineer CDR
The mechanics are fixed and non-negotiable. Three career episodes, each 1,000 to 2,500 words, written in the first person with numbered paragraphs (1.1, 1.2, and so on). Use "I", not "we" or "the team": the assessor is evaluating you, so every engineering verb needs your name behind it. The personal engineering activity is the heart of each episode, and it is exactly where operational description gets flagged. If a paragraph could have been written by your supervisor about the site, it is not personal engineering activity.
Software needs careful handling. Vulcan, Surpac, and Datamine belong in your episodes as platforms through which you exercised judgment, not as the contribution itself. "I am proficient in Surpac" evidences nothing. "I used Surpac to model three pit shell configurations against a revenue-to-strip-ratio constraint and selected the one that reduced equipment exposure in a known ground-movement zone" evidences PE2.3. EA assesses the decision, not the toolbar.
One more mechanical trap: Engineers Australia runs every submission through Turnitin, and plagiarised or heavily templated content is a standalone rejection ground. Treat sample episodes as structure only. Our career episode guide and the skills assessment criteria go deeper than space allows here.
Mapping the Summary Statement to Mining Competencies
Every one of the 16 elements must point to a specific numbered paragraph in one of your episodes. Any element without that pointer is a gap the assessor locates before you do. For most ANZSCO 233611 applications, the summary statement is where the CDR for mining engineer comes apart.
Three elements are the usual casualties for site engineers. The moment you connect a design decision to a community, safety, or environmental consequence, such as a blast timed around a nearby township's vibration tolerance, you address PE1.4 (engineering's place in society). PE3.3 (creative or innovative approach) requires a genuine non-routine problem where you departed from the standard method, not a claim that you are innovative. To satisfy PE3.6 (lifelong learning), point to a concrete instance of learning a new method or software capability the role demanded.
A fourth failure is subtler: applicants who front-load the summary with knowledge claims and leave the PE2 application elements to a single thin paragraph. The assessor reads PE2.3 and PE2.4 first. If those cross-references point to paragraphs that describe activities rather than decisions, the application stalls regardless of how strong the knowledge profile looks. Our summary statement mapping resource shows the cross-referencing format element by element.
Where JORC Code Experience Helps and Where It Misleads
Mining engineers routinely overweight JORC reporting experience, and the distinction matters.
JORC Competent Person status is a separate credential from EA's assessment. It requires a minimum of five years' relevant experience with the deposit style in question, plus membership of AusIMM, AIG, or a Recognised Professional Organisation. It certifies that you can sign off public resource and reserve statements. It does not certify engineering design ability.
Resource estimation and classification evidence PE1.2 (specialist knowledge) and, through the public reporting obligation, PE3.4 (regulatory compliance). It does not evidence PE2.3 or PE2.4, because estimating a resource is not designing and verifying an engineering solution. Applicants who build an episode around JORC reporting tend to produce a strong PE1 profile and an empty PE2 one. That imbalance is exactly what fails. Use JORC as supporting context inside a broader planning or design episode, not as a centrepiece.
CDR Rejection Causes Specific to Mining Engineers
Three patterns account for the majority of ANZSCO 233611 rejections.
The first is describing a mine's operations instead of engineering decisions, the problem the FIFO reframe above is built to solve. The second is treating JORC reporting as engineering design evidence, the gap the section above explains. The third, and the one applicants least expect, is a summary statement that maps the knowledge elements credibly but leaves PE2.3 and PE2.4 pointing to activity descriptions rather than design decisions. An assessor who reads "I participated in mine planning" as a PE2.4 cross-reference will fail the application even when the career episodes contain the right engineering detail, because the mapping failed to surface it.
All three grow from the same root: writing from involvement rather than from decisions. The fix is the same in each case. Before you submit, the CDR submission checklist confirms every element maps cleanly.
CPD for Mining Engineers
EA accepts a broad range of continuing professional development for ANZSCO 233611: AusIMM technical conferences and short courses, METS sector forums and seminars, statutory safety training required under legislation such as Queensland's Coal Mining Safety and Health Act 1999, and software training courses for Vulcan, Surpac, or Datamine. Site engineers usually have more valid CPD than they bother to record. Because CPD format rules are common across every discipline, our 2026 CDR guide covers the required layout in full.
Frequently Asked Questions About CDR for Mining Engineers
Can I use a fly-in fly-out (FIFO) mining role as a career episode?
Yes, provided you do not write it as a roster. A FIFO role passes when the episode is built around one discrete engineering problem you defined, solved, and validated, rather than the shifts you supervised. Cut the supervision and reporting language and keep the design decisions.
How do I show personal engineering contribution in a large team?
Write every engineering action as an I-statement and isolate the decisions that were yours alone. EA is assessing you, so "I selected", "I calculated", and "I verified" carry the episode, while "we" and "the team" dilute it. Naming what you personally decided, even inside a large crew, is what evidences the competency.
Does underground mining experience count differently from surface mining?
EA does not formally separate underground and surface work into distinct competency tracks; both are assessed against the same 16 elements. In practice, underground work often evidences ground control and ventilation design clearly, while surface work leans toward drill-and-blast and pit optimisation. Choose whichever gives you the clearest defined-problem narratives.
Should my career episode cover a blast design or a mine planning project?
It depends on the gaps your other two episodes leave. Blast design is the stronger source of PE2.1 and PE3.4 evidence; mine planning better demonstrates PE2.4 design conduct and PE3.5 leadership. Pick the one that fills what your other episodes miss, not the one with the most dramatic story.
How does JORC Code reporting experience fit into a mining engineer CDR?
JORC work evidences specialist knowledge (PE1.2) and regulatory compliance (PE3.4), not engineering design (PE2.3 and PE2.4). Include it as supporting context within a design or planning episode, and avoid building a whole episode around resource estimation, which leaves the engineering-application elements unproven.
My mining project ran for three years. How do I define episode boundaries?
Anchor the episode to a single defined problem within the project, not the project's full timeline. A three-year mine plan contains dozens of discrete engineering decisions; choose one, such as a pushback redesign, and write its inputs, options, and verified outcome. The rest of the project becomes brief context.
Can I include mine safety management work as a career episode?
Only if it demonstrates engineering design or analysis rather than administrative compliance. A ventilation redesign or a risk-quantified engineered control can evidence PE2.3; running safety inductions or auditing procedures cannot. If the work was administrative, use it as CPD or context, not as an episode.
To see how discipline-specific mapping reads on the page, our CDR samples for mining engineers show ANZSCO 233611 episodes mapped element by element. The CDR writing service page explains how that competency mapping works in practice.