Understanding the 34 Engineering Competencies

The Engineers Canada national competency framework defines 34 competencies organized into 7 categories that a professional engineer is expected to demonstrate. This framework serves as the foundation for the experience review process in most Canadian provinces and territories, and understanding it thoroughly is essential for a successful licence application.

Unlike a checklist of tasks, these competencies describe the abilities, knowledge, and professional attributes that an engineer must possess. Your job during the application process is to provide evidence, usually through experience narratives, that you have exercised these competencies in real engineering work under appropriate supervision.

Each competency is assessed on a spectrum. You do not need to demonstrate mastery-level performance in every single one, but you do need to show a minimum level of competence across all categories. Strong applications demonstrate depth in several competencies while meeting the baseline across the board.

Category 1 -- Technical Competence: This is where most engineers feel most comfortable. It covers your ability to apply engineering knowledge, use appropriate tools and methods, interpret codes and standards, and solve technical problems. Competencies in this category include applying specialized knowledge, using engineering tools, and conducting analysis.

Category 2 -- Communication: Engineers must communicate effectively with technical and non-technical audiences. This category covers written communication (reports, specifications, correspondence), oral communication (presentations, meetings, client interactions), and the ability to listen and adapt your message to your audience.

Category 3 -- Project and Financial Management: This goes beyond scheduling and budgeting. It includes planning work, managing resources, understanding financial concepts relevant to engineering projects, assessing risk, and ensuring deliverables meet quality standards. Even junior engineers contribute to project management through task estimation and progress reporting.

Category 4 -- Team Work: Engineering is fundamentally collaborative. This category assesses your ability to work within multidisciplinary teams, contribute to team goals, resolve conflicts constructively, and support colleagues. It also covers your experience working with contractors, subconsultants, and other stakeholders.

Category 5 -- Professional Accountability: This is about integrity, ethics, and the public interest. It covers your understanding of professional obligations, adherence to codes of ethics, awareness of the societal impact of engineering work, and your commitment to maintaining professional standards.

Category 6 -- Social, Economic, and Environmental Impact: Engineers operate within a broader context. This category requires you to demonstrate awareness of how engineering decisions affect communities, economies, and the environment. Sustainability, stakeholder engagement, and consideration of long-term consequences fall here.

Category 7 -- Personal Continuing Education: Professional development does not stop at licensure. This category assesses your commitment to lifelong learning, staying current with developments in your field, and actively seeking opportunities to expand your knowledge and skills.

The primary vehicle for demonstrating competencies is the experience narrative, sometimes called a Situation-Action-Result (SAR) statement. Each narrative should clearly connect a specific work experience to one or more competencies, explaining what you did, why you did it, and what the outcome was.

Be specific rather than general. Instead of writing "I managed project schedules," describe a particular project where you developed a work breakdown structure, adjusted timelines in response to a site constraint, and delivered the project phase within the revised deadline. Concrete examples carry far more weight than broad claims.

Use the language of the competency framework. If a competency mentions "applying codes and standards," your narrative should explicitly reference the specific code or standard you applied, the context in which you applied it, and how your application of that standard contributed to the project outcome.

Each narrative does not need to be a lengthy essay. Aim for 200-400 words per narrative: enough to establish context, describe your specific contribution, and explain the result. Quality and specificity matter more than volume.

The SAR (Situation-Action-Result) structure is the most effective format for competency narratives. It forces you to provide context, describe your personal contribution, and demonstrate the outcome of your work.

Situation: Set the scene in 1-2 sentences. What was the project? What was the engineering challenge or context? What constraints or requirements were relevant? Keep this brief but specific enough that a reviewer who has never seen the project can understand the context.

Action: This is the core of your narrative and should receive the most attention. What specifically did you do? What engineering judgment did you apply? What tools, methods, or standards did you use? How did you collaborate with or direct others? Use first person ("I") and be precise about your individual contribution versus the team's work.

Result: What was the outcome? How did your work affect the project, client, or public interest? Quantify where possible (cost savings, schedule improvement, environmental benefit). If the result was a learning experience, explain what you learned and how you applied that learning to subsequent work.

For Technical Competence (Category 1), draw from your most challenging technical work. Describe problems that required engineering judgment, not just routine calculations. Mention specific software, codes, or analytical methods by name.

For Communication (Category 2), remember that every engineering project generates communication. Think about reports you authored, presentations you delivered, client meetings you led, or technical reviews you participated in. If you trained a junior colleague, that counts too.

For Project and Financial Management (Category 3), you do not need to have been a project manager. Describe your contributions to scheduling, cost estimation, scope management, or quality assurance. Even tracking your own task progress and reporting it demonstrates competence in this area.

For Team Work (Category 4), focus on specific instances of collaboration, mentoring, or conflict resolution. Cross-disciplinary work (e.g., coordinating with electrical, structural, or environmental teams) is particularly strong evidence.

For Professional Accountability (Category 5), describe situations where you upheld professional standards, identified and reported concerns, or ensured that public safety was prioritized. This category often overlaps with ethics scenarios from the NPPE.

For Social, Economic, and Environmental Impact (Category 6), draw from projects where you considered sustainability, performed environmental assessments, engaged with affected communities, or evaluated the long-term consequences of engineering decisions.

For Continuing Education (Category 7), document formal training, conferences, self-directed learning, and professional association activities. Be specific about what you learned and how you applied it to your engineering practice.