For engineers preparing a professional assessment for New Zealand, presenting technical experience clearly is just as important as describing qualifications. A strong report should show how your engineering knowledge has been developed through education, projects, employment, and professional learning. In a KA02 Assessment, the focus is not simply on stating that you have worked on engineering projects; instead, your report should explain the technical knowledge you used, the problems you addressed, your personal contribution, and how your decisions were supported by engineering principles. Engineering New Zealand describes the Knowledge Assessment as an evaluation of technical knowledge and understanding gained through work and learning against the level associated with a Washington Accord-accredited qualification.
KA02 Assessment: Understanding the Purpose of Your Technical Experience
KA02 Assessment and the Role of Professional Experience
Technical experience provides the practical context through which an engineer can demonstrate knowledge. Therefore, your report should move beyond a simple employment history and explain the relationship between your engineering education and the work you have actually performed.
For example, stating that you worked as a civil engineer on a construction project provides only basic information. A stronger presentation explains the engineering problem, the technical principles considered, the methods used to investigate the issue, the solution developed, and the reasoning behind your final decision.
Consequently, each experience should contribute meaningful evidence to your overall technical profile. Your objective is to make the assessor understand not only what you did, but also how and why you did it.
Presenting Your Individual Contribution
One of the most important aspects of technical experience is demonstrating your personal contribution. Engineering New Zealand's assessment guidance specifically recommends writing in the first person so that the assessor can identify the applicant's contribution.
Instead of repeatedly writing that “we designed the system” or “our team solved the problem,” explain your own involvement. You can describe how you analysed the requirements, performed calculations, reviewed technical information, developed a design approach, evaluated alternatives, or contributed to implementation.
This distinction makes the report more authentic because it separates your professional knowledge from the general activities of the organisation or project team.
KA02 Assessment: Turning Work Experience into Technical Evidence
Explaining the Engineering Problem
A technical experience becomes meaningful when it demonstrates how engineering knowledge was applied to a genuine problem. Therefore, begin each major experience by establishing the technical context.
Explain what the project was intended to achieve, what engineering conditions affected it, and what specific challenge required technical consideration. The problem might involve structural performance, electrical reliability, mechanical efficiency, process optimisation, environmental conditions, software functionality, safety, materials, or another discipline-specific issue.
However, avoid turning the section into a lengthy company description. The emphasis should remain on the engineering problem and the knowledge required to address it.
Describing Your Technical Approach
After explaining the problem, describe how you approached it. This is where your technical experience becomes evidence of engineering knowledge.
For instance, you might explain how you reviewed design requirements, interpreted drawings, examined specifications, performed calculations, used modelling software, assessed technical alternatives, consulted relevant standards, or evaluated previous project data.
Furthermore, explain the reasoning behind your approach. Simply saying that software was used does not demonstrate much technical understanding. Instead, explain what you used the software for, what inputs were considered, how the results were interpreted, and how those results influenced your engineering decision.
This approach creates a logical connection between problem → analysis → engineering knowledge → decision → outcome.
KA02 Assessment: Connecting Experience with Engineering Knowledge
Linking Projects to Your Knowledge Profile
Your technical experience should support the knowledge areas being assessed rather than appearing as an unrelated career history. Engineering New Zealand provides specific guidance and documentation for Knowledge Assessments, including a Knowledge Assessment Applicant Guidance document.
Therefore, when describing a project, identify the engineering knowledge that enabled you to complete your responsibilities. Depending on your discipline, this could include mathematics, natural sciences, engineering fundamentals, specialist engineering knowledge, design principles, engineering technology, professional practice, sustainability, or research-based knowledge.
For example, an engineer working on a mechanical system could explain how thermodynamics, fluid mechanics, materials knowledge, numerical analysis, and design principles influenced a particular technical decision.
Similarly, an electrical engineer could discuss circuit theory, power-system principles, control systems, protection requirements, simulation, testing, and technical standards where relevant.
Demonstrating Application Rather Than Listing Knowledge
A common weakness in technical reports is simply listing engineering subjects. A stronger approach is to demonstrate how that knowledge was applied.
For example, rather than writing that you possess knowledge of structural engineering, explain how structural principles influenced your analysis of loading conditions, member selection, connection design, or structural performance.
Likewise, instead of stating that you understand engineering mathematics, describe how mathematical modelling or numerical calculations helped you evaluate a technical problem.
As a result, your experience becomes evidence rather than a collection of unsupported statements.
KA02 Assessment: Presenting Technical Projects Clearly
Selecting Relevant Engineering Experiences
Your report should concentrate on experiences that provide strong technical evidence. Not every task performed during your career needs the same level of detail.
Choose projects where your involvement demonstrates meaningful engineering knowledge and decision-making. Projects involving technical analysis, design, problem-solving, investigation, optimisation, testing, implementation, or evaluation can provide useful evidence when they are genuinely based on your own experience.
For engineers with limited industry experience, relevant academic projects, laboratory work, research, internships, or supervised engineering activities may also provide useful context where appropriate. The important consideration is whether the example genuinely demonstrates the required knowledge.
Creating a Logical Technical Narrative
Each project should read like a technical story rather than a job description.
Begin by establishing the project background and technical objective. Then introduce the problem or requirement. Explain your role and the engineering methods you applied. After that, describe the technical reasoning, calculations, analysis, design decisions, testing, or implementation. Finally, explain the result and what the experience demonstrates about your engineering knowledge.
This structure makes the information easier to follow because the assessor can see the progression from the original requirement to the engineering outcome.
IPENZ KA02: Presenting Experience for New Zealand Engineering Context
Understanding the IPENZ KA02 Terminology
Many international engineering applicants still use the phrase IPENZ KA02 when discussing the New Zealand Knowledge Assessment. The terminology is commonly associated with the historical name IPENZ, while the current assessment guidance is provided by Engineering New Zealand. Current Engineering New Zealand materials refer to the process as a Knowledge Assessment. Therefore, applicants researching IPENZ KA02 should make sure that they are working from current Engineering New Zealand requirements and guidance rather than relying only on older terminology.
Showing New Zealand-Relevant Professional Awareness
For applicants from New Zealand and Australia, or international engineers seeking professional recognition in New Zealand, technical experience should be communicated in a way that demonstrates professional engineering understanding.
Where relevant to your actual experience, explain how you considered technical requirements, safety, environmental factors, sustainability, quality, risk, communication, and professional responsibilities.
At the same time, do not add New Zealand-specific knowledge merely to make the report appear stronger. Your statements should accurately represent your education, professional experience, and genuine understanding.
IPENZ KA02 Knowledge Assessment: Making Technical Decisions Understandable
Explaining Why You Chose a Solution
An assessor should be able to understand the reasoning behind important technical decisions. Therefore, avoid presenting your final solution without explaining how you reached it.
Suppose you selected a particular material, design configuration, software method, equipment specification, or engineering model. Explain the technical factors that influenced the decision. You could discuss performance requirements, cost considerations, safety, reliability, environmental conditions, compatibility, maintainability, or applicable technical requirements, depending on the actual project.
This demonstrates engineering judgement without turning the report into a simple list of responsibilities.
Discussing Alternatives and Evaluation
Technical decision-making becomes clearer when you explain how alternatives were considered. If you evaluated two or more possible approaches, describe the criteria you used to compare them and why the selected approach was suitable for the project.
For example, you might compare alternatives according to structural capacity, energy efficiency, reliability, lifecycle considerations, manufacturability, safety, or project requirements.
However, the explanation should remain connected to your real experience. Avoid creating hypothetical scenarios that you did not personally encounter.
KA02 Assessment: Using Evidence to Support Your Technical Experience
Connecting Work Samples with Your Narrative
Technical experience becomes more convincing when supported by appropriate evidence. Engineering New Zealand's guidance identifies supporting documentation as part of the Knowledge Assessment process.
Depending on the requirements applicable to your assessment, relevant evidence can include technical calculations, engineering drawings, design documentation, analysis, reports, project records, research material, or other authentic examples of your work.
The evidence should complement the narrative rather than replace it. A calculation by itself does not explain why the calculation was necessary or how its result influenced your engineering decision.
Maintaining Authenticity and Accuracy
Your report should accurately represent your own education and experience. Every technical example should be something you can explain confidently if the assessor asks questions about it.
This is particularly important because technical experience may involve confidential employer information. Consequently, describe the engineering principles and your contribution without disclosing commercially sensitive information.
Similarly, avoid exaggerating your responsibilities. If you supported a senior engineer, describe the support you actually provided. If you independently completed an analysis, explain that accurately. Clear and truthful descriptions are more useful than inflated claims.
KA02 Assessment: Improving the Technical Presentation of Your Report
Writing with Technical Precision
Technical writing should be precise but understandable. Avoid unnecessarily complicated language when a simpler technical explanation communicates the same idea.
For example, instead of filling a paragraph with general statements such as “I utilised my engineering expertise to successfully overcome a challenging problem,” explain exactly what you analysed, what method you applied, and what conclusion you reached.
Moreover, maintain consistent terminology throughout the report. If you introduce a technical abbreviation, explain it when first used and then use it consistently.
Maintaining a Professional First-Person Style
Because the assessment focuses on your knowledge and experience, first-person writing can make your contribution clearer. Use phrases such as “I analysed,” “I calculated,” “I evaluated,” “I designed,” “I reviewed,” and “I recommended” when they accurately describe your role.
At the same time, avoid beginning every sentence with “I.” A professional narrative can naturally combine first-person statements with technical explanations.
For Australian students and engineers preparing documentation for New Zealand professional recognition, this style can also help bridge the difference between an academic description and a professional engineering account.
KA02 Assessment: Common Presentation Problems to Avoid
Avoiding a Resume-Like Description
A resume summarises employment, whereas a technical assessment needs evidence of engineering knowledge. Therefore, writing several paragraphs that simply describe job duties may not provide enough technical depth.
Instead, select meaningful experiences and explore the engineering reasoning behind them.
Avoiding Excessive Generalisation
Statements such as “I solved complex engineering problems” are difficult to evaluate without supporting detail. Explain what made the problem technically challenging and what knowledge you applied.
Likewise, avoid claiming responsibility for an entire project when your role covered only one component. Precision about your contribution improves the credibility of your technical narrative.
Avoiding Unconnected Technical Information
Another issue occurs when applicants add engineering theories that have little relationship to their project. Technical knowledge should appear naturally within the explanation of your work.
Consequently, every major technical concept should answer an important question: How did this knowledge help me understand, analyse, design, evaluate, or solve the engineering problem?
KA02 Assessment: A Strong Approach for New Zealand and Australian Applicants
Building a Consistent Technical Story
For applicants from Australia and New Zealand, the strongest presentation is one that connects education, professional development, engineering projects, technical decisions, and outcomes into one consistent story.
Your academic background establishes the foundation. Your work experience demonstrates application. Your project examples provide technical depth. Your professional development demonstrates continued learning. Together, these components can create a clearer picture of your engineering knowledge.
Reviewing Your Report Before Submission
Before finalising your report, read each project as if you were an assessor who had never worked with you. Ask whether the technical problem is clear, whether your personal role is obvious, whether the engineering principles are explained, whether your decisions have technical reasoning, and whether the evidence genuinely supports your statements.
Engineering New Zealand provides dedicated Knowledge Assessment guidance and a checklist, so applicants should use the current official requirements when preparing their submission.
Conclusion
Presenting technical experience effectively requires more than describing where you worked or which projects you completed. A strong KA02 Assessment should demonstrate how your engineering knowledge was developed, applied, evaluated, and strengthened through authentic technical experience. For applicants researching IPENZ KA02 or preparing an IPENZ KA02 Knowledge Assessment, the focus should remain on clear evidence, personal contribution, technical reasoning, and an accurate connection between experience and engineering knowledge. By presenting each project as a logical technical narrative and explaining the decisions behind your work, you can make your professional experience easier for an assessor to understand.
FAQs
What is the purpose of a KA02 Assessment report?
A Knowledge Assessment evaluates whether an engineer has acquired technical knowledge and understanding through education and experience at a level comparable with the relevant Washington Accord-accredited qualification standard.
How should technical experience be written in a KA02 Assessment?
Technical experience should explain the engineering problem, your personal role, the knowledge and methods you applied, your technical reasoning, the solution or outcome, and what the experience demonstrates about your engineering knowledge.
Is first-person writing appropriate for a KA02 Assessment?
Yes. Engineering New Zealand's assessment guidance recommends first-person wording such as “I” and “me” so the assessor can clearly identify the applicant's individual contribution.
What does IPENZ KA02 mean?
IPENZ KA02 is a commonly used term associated with the New Zealand engineering Knowledge Assessment. Current official guidance is provided by Engineering New Zealand, so applicants should use the latest official documentation when preparing their assessment.
Can work experience support an IPENZ KA02 Knowledge Assessment?
Yes. Work and learning are both relevant to demonstrating the technical knowledge assessed through the Knowledge Assessment. The key is to explain genuine engineering experiences and show how your knowledge was applied rather than simply listing employment duties.
