How Students Should Talk About Competencies in Interviews

Students should not lead with the word competency in an interview. They should tell a short, concrete story about what they did, what changed, and what they learned, then connect it to the skill only if that connection helps the interviewer understand the example. A phrase like “I have strong communication” is less useful than “I translated a lab report into a one-page summary for a nontechnical supervisor, which helped our team catch a dosing error before the next shift.”

Start with evidence, not labels

When students are coached to “talk about competencies,” they often hear that as a cue to repeat the competency name. That usually sounds flat. Interviewers already know what teamwork, communication, or problem solving means in general. What they do not know is whether the student has actually used that skill in a real setting, at a useful level, under real constraints.

A competency rating on a résumé or assessment report is useful as background, but it is not enough for an interview answer. In conversation, the rating has to become evidence. The student needs a situation, a task, an action, and a result. That structure keeps the answer grounded and makes it easier for the interviewer to picture the work.

For example:

• Weak: “My teamwork is good because I’m collaborative.”
• Better: “On a five-person consulting project, two teammates disagreed about the recommendation. I set up a 20-minute meeting, asked each person to list their top concern, and we narrowed the issue to cost versus speed. We revised the recommendation and the client chose the faster option.”

The second answer does not just claim teamwork. It shows how the student behaved when the team had friction.

Why the competency label can hurt the answer

Naming the competency first often makes the answer sound like a form response. It can also put the student in a defensive position, as if they are trying to prove a label they were assigned. Interviewers usually trust stories more than self-ratings because stories contain details that can be checked mentally against the job.

There is another problem. Some competency words are too broad to be persuasive without context. “Leadership” can mean running a club, taking initiative in a class project, or quietly coordinating a shift change at work. “Professionalism” can mean punctuality, follow-through, or handling conflict without escalation. If the student starts with the label, the interviewer still has to guess what it means.

A better approach is to let the story reveal the competency. The student can name it at the end if needed: “That example shows how I handled conflict on a team,” or “That was my first experience leading a process change.” The label becomes a summary, not the main point.

Coach students to answer in three parts

A simple structure works well for most interview questions about skills.

1. Set the scene in one sentence

The student should name the context quickly: a class project, internship, student job, research role, club, or volunteer assignment. One sentence is enough.

Example: “During my internship at a local nonprofit, I was asked to organize donor records before a board presentation.”

2. Describe the action in concrete terms

This is where the competency shows up. The student should use verbs that show behavior, not claims about personality.

Examples:

• “I compared three versions of the spreadsheet and found duplicate entries.”
• “I asked the supervisor which information mattered most to the board.”
• “I rewrote the draft so the key numbers were in the first paragraph.”
• “I met with the group twice to divide the work and set deadlines.”

3. Close with a result or lesson

The result does not have to be dramatic, but it should show impact. If there is a number, use it. If not, explain the practical outcome.

Examples:

• “The board deck was ready a day early.”
• “We reduced the report from six pages to two and got approval faster.”
• “The client understood the recommendation and accepted the revised timeline.”
• “I learned that clarifying expectations early prevents rework later.”

This format helps students avoid vague language and keeps them from drifting into a list of traits.

Turn ratings into stories

If a student has a competency rating, that rating should guide story selection, not dictate wording. A high rating in critical thinking, for example, might point to a moment when the student compared options, noticed a pattern, or revised a plan after new information came in.

A helpful coaching move is to ask, “What did you do that made someone rate you that way?” That question usually produces better material than “Tell me about your critical thinking.” Students remember actions more easily than labels.

Here are a few examples of turning a competency into interview language:

• Communication: Instead of “I communicate well,” say, “I adapted a technical update for a supervisor who did not know the terminology, then followed up with a short email so the team had a record of the decision.”
• Teamwork: Instead of “I’m a team player,” say, “When two teammates missed a deadline, I reorganized the task list and took the section that was blocking the group.”
• Problem solving: Instead of “I’m good at solving problems,” say, “When the survey link failed, I tested it on my phone, found the issue was the character limit in the URL, and sent a corrected version within 30 minutes.”
• Leadership: Instead of “I have leadership experience,” say, “I noticed our volunteer team kept losing track of supplies, so I created a shared checklist and assigned one person to restock each week.”

The story should fit the student’s actual level of responsibility. A first-year student does not need to sound like a manager. A strong example from a campus job is better than a weak example from a prestigious internship.

Help students avoid the two common mistakes

Too abstract

Students often answer with traits: “I’m hardworking,” “I’m adaptable,” “I’m detail-oriented.” Those statements are hard to verify and easy to forget. They also sound interchangeable.

Push them to attach each trait to an action. If they say they are detail-oriented, ask what detail they caught. If they say they are adaptable, ask what changed and how they responded.

Too much context, not enough action

Some students give a long setup and never get to the point. Interviewers do not need the full backstory. They need the part where the competency appears.

A good rule is this: if the setup takes longer than the action, the answer is probably too slow. Students should spend more time on what they did than on who was on the committee or how many meetings were held.

Coach for the interview, not the transcript

Advisers sometimes see students assume that a strong résumé bullet will work unchanged in an interview. It usually will not. A bullet can be concise because the reader can scan it. An interview answer has to sound natural out loud and survive follow-up questions.

That means students should practice telling the same story in different lengths:

• A 20-second version for a quick prompt
• A 60-second version for a standard behavioral question
• A 2-minute version with a bit more detail if the interviewer asks for it

The core facts should stay the same. The student should not invent a stronger role or add responsibilities they did not have. If they only contributed a small piece, they should say so clearly. Precision matters more than sounding impressive.

A simple coaching test

If a student’s answer can be copied and pasted under a résumé heading without changing a word, it is probably too vague for an interview. If the answer includes a clear setting, a specific action, and a result, it is probably ready.

When students can explain what they did in plain language, the competency becomes visible without being announced. That is usually what interviewers remember.