How to Write a Competency-Based Assessment for Engineering

TL;DR: A competency-based assessment for engineering should measure what someone can actually do in real engineering situations, not just what they can recall. Start by defining the role, choosing the core competencies, writing observable performance criteria, and building tasks that reflect real work. Then score the work with a clear rubric, test it with a small group, and revise it before launch. CBA Pro can help teams structure these assessments so they are fair, practical, and easier to defend.

What does a competency-based assessment for engineering need to prove?

A good assessment proves that a person can apply engineering knowledge in context. That means more than checking formulas or asking theory questions. You want evidence of problem solving, safe judgement, technical accuracy, communication, and the ability to work within constraints. In engineering, those constraints often include codes, standards, budgets, timelines, and public safety.

If you are writing for a Canadian audience, think about how the job is actually done here. A civil engineer may need to consider provincial building codes, climate conditions, and bilingual documentation. A mechanical engineer may need to show how they evaluate risk, document design decisions, and work with cross-functional teams. The assessment should reflect those realities.

How do you define the role before writing the assessment?

Start with the job itself. Ask what level of engineer this is for, what discipline is involved, and what the person must be able to do on day one. A junior engineer, a technologist, and a senior project lead will not need the same assessment.

Write a short role profile that includes the main duties, the working environment, and the expected outcomes. Then identify the tasks that matter most. For example, if the role is in structural engineering, the assessment might focus on load analysis, drawing review, code compliance, and communication with project stakeholders.

At CBA Pro, this is the point where many teams get clearer. They stop writing around the job and start writing from the job. That shift makes the assessment much easier to score.

How do you choose the right competencies?

Pick competencies that are observable and job-related. In engineering, the list often includes technical knowledge, analytical thinking, problem solving, safety awareness, ethics, communication, teamwork, and project management. You do not need to test everything at once. Choose the few competencies that matter most for the role.

A helpful way to organize them is to group them into three types:

• Technical competencies, such as applying formulas, using software, interpreting drawings, or selecting materials.
• Professional competencies, such as writing reports, explaining trade-offs, and documenting decisions.
• Behavioural competencies, such as judgement, collaboration, and attention to safety.

Keep each competency concrete. “Strong engineering mindset” is too vague. “Identifies design risks and explains mitigation options” is much better.

How do you turn competencies into assessment criteria?

Once the competencies are set, write performance criteria that show what good work looks like. Each criterion should be observable, measurable, and tied to the role. Avoid vague language like “understands,” “appreciates,” or “is familiar with.” Those words are hard to score fairly.

Instead, describe the behaviour or output. For example:

• Correctly interprets project requirements and identifies missing information.
• Applies relevant engineering standards to the solution.
• Explains assumptions, limitations, and risks in plain language.
• Produces calculations or documentation with minimal errors.

This is where a competency-based assessment becomes useful. It gives assessors a shared standard and gives candidates a clear target.

What kind of tasks work best in engineering assessments?

The best tasks look like real work. For engineering, that might mean a design review, a case study, a calculation exercise, a technical memo, a site scenario, or a troubleshooting task. The more closely the task matches the job, the better the evidence.

For example, instead of asking a candidate to list the steps in a risk assessment, give them a project scenario and ask them to identify hazards, rank the risks, and recommend controls. That shows how they think, not just what they memorized.

You can also combine task types. A short written response can test reasoning, while a practical exercise can test application. If the role involves client contact, include a communication component. If it involves fieldwork, include site-based judgement.

How do you build a fair scoring rubric?

A rubric turns the assessment into a consistent process. It should define what counts as competent, borderline, and not yet competent. Keep the scale simple. Too many score levels make assessors argue about small differences instead of judging the work.

For each criterion, describe what performance looks like at each level. A strong rubric might say:

• Competent: Applies the correct standard, explains the reasoning, and makes a safe recommendation.
• Borderline: Uses some correct methods but misses key details or leaves risks unclear.
• Not yet competent: Misses the standard, gives unsafe advice, or cannot justify the solution.

Train assessors before launch. Even a good rubric can fail if people interpret it differently. CBA Pro recommends calibration sessions so assessors review sample responses and agree on what the rubric means in practice.

How do you check that the assessment is valid and practical?

Before you roll it out, test the assessment with a small group. Look for three things. First, does it measure the right competencies? Second, can candidates complete it in a realistic time? Third, can assessors score it without confusion?

Ask whether the assessment is too long, too abstract, or too dependent on one narrow kind of experience. Engineering roles vary, so the task should allow different but valid approaches where possible. If the assessment is too rigid, it may miss capable people who solve problems differently.

Also check for bias. Avoid language or scenarios that favour one background unfairly. Use plain English, define acronyms, and make the context clear. In Canada, where teams are often diverse and distributed, clarity matters a lot.

How do you document the assessment so others can use it?

Write a short assessor guide. Include the purpose of the assessment, the competencies, the scoring rubric, timing, instructions, and examples of acceptable evidence. If the assessment will be used across teams or locations, consistency is even more important.

Good documentation also helps with audit trails and quality assurance. If a candidate asks why they were not successful, the assessor should be able to point to specific criteria and evidence, not a general impression.

If you want a system that keeps this organized, CBA Pro is built to help teams structure competency-based assessments and keep the process clear. You can also create an account to set up your own assessment workflow.

What mistakes should you avoid?

The most common mistake is writing the assessment around theory instead of performance. Another is using vague criteria that different assessors will score differently. A third is trying to test too many competencies in one sitting.

Other problems include overly complex rubrics, unrealistic scenarios, and tasks that do not match the level of the role. If you are assessing an engineer for a project role, do not rely only on multiple-choice questions. If you are assessing a graduate engineer, do not expect senior-level judgement without support.

Keep the focus on evidence. That is what makes a competency-based assessment useful.

How do you improve the assessment over time?

After each use, review the results. Look for patterns. Were candidates confused by a question? Did assessors disagree on scoring? Did the task fail to show the competency you wanted? Use that feedback to revise the wording, the rubric, or the task itself.

Assessment design is never finished on the first draft. The goal is a process that is fair, repeatable, and tied to real engineering work. When you get that right, the assessment becomes a better signal for hiring, promotion, or certification decisions.

Related questions

What is a competency-based assessment in engineering?

It is an assessment that measures whether a person can perform engineering tasks to an expected standard. It focuses on observable skills, judgement, and applied knowledge.

How do you write competencies for an engineering assessment?

Use clear, job-related language. Describe actions and outputs, such as analysing data, applying standards, or explaining technical decisions.

What should be included in an engineering rubric?

A good rubric includes the performance criteria, clear score levels, and examples of what competent and not yet competent work looks like.

Can a competency-based assessment include technical questions?

Yes. Technical questions work well when they are tied to real work and used alongside practical tasks or case scenarios.

How do you make an engineering assessment fair?

Use plain language, define criteria clearly, test the assessment with a small group, and train assessors to score consistently.

Where can I manage a competency-based assessment process?

You can use CBA Pro to organize assessment workflows, and log in here if you already have an account.

Sources and further reading

• CBA Pro
• create an account
• log in here