An employer’s interview competencies are more useful than a long list of generic behavioral questions. They show you which capabilities the organization has chosen to evaluate, giving you a rational way to decide which experiences to prepare and which gaps to address. The goal is not to memorize the employer’s language or force every answer to sound like a slogan. The goal is to connect the employer’s published priorities to specific evidence from your own work, education, volunteering, or other relevant experience.
This approach is especially valuable when a company publishes competencies, values, leadership principles, or interview guidance. Microsoft, for example, identifies collaboration, drive for results, customer focus, influencing for impact, judgment, and adaptability as core competencies. Its interview guidance also asks candidates to prepare specific examples and explain how their skills translate to the role. You can read the full guidance in Microsoft’s interview tips for all roles.
Start with the employer’s evaluation language
Begin with research rather than answer-writing. Review the job description, the employer’s careers pages, interview guidance, values, leadership principles, and any role-specific material you can find. Copy the exact words that describe what the organization wants to see. Then separate those words into three categories: skills required for the role, behaviors the employer values, and outcomes the role is expected to produce.
This distinction matters because a job requirement and an employer principle may overlap without meaning the same thing. A role may require project coordination, while a company principle emphasizes ownership. One story could demonstrate both, but you should know which part of the story proves coordination and which part proves that you took responsibility for an outcome. Microsoft describes its hiring process as a consistent framework that evaluates skills against role requirements alongside shared principles such as growth mindset, customer focus, collaboration, and accountability. Its supports treating both dimensions as preparation inputs.
Do not assume that every value deserves an entirely separate story. Some experiences can provide evidence for several competencies, but the emphasis should change depending on the question. A difficult client project might show customer focus, judgment, collaboration, and drive for results. Your preparation should identify those connections without pretending that one story proves everything.
Use published principles as filters, not scripts
Amazon offers another clear example of employer-specific language. Its public Leadership Principles include Customer Obsession, Ownership, Invent and Simplify, Learn and Be Curious, Bias for Action, Earn Trust, Dive Deep, and Deliver Results. These principles can help an applicant prioritize examples instead of preparing an unfocused collection of stories. They should not be repeated as slogans without evidence: the useful question is, “What did I actually do that demonstrates this principle?”
Research should also help you explain why the role and company appeal to you. UC Berkeley’s career guidance recommends researching the employer, thinking specifically about your interest in the role and company, and mining past experience for stories that show relevant skills and responses to work challenges. Its interview process overview is a useful independent reference for that preparation step.
Build a competency-to-evidence matrix
Once you have a list of competencies, create a working matrix. Do not begin by writing polished answers. First, collect evidence. For each competency, list two or three experiences that might fit, then choose the strongest example based on relevance, your individual contribution, and the clarity of the result.
Use this matrix to turn employer language into specific preparation prompts. The proof column is deliberately practical: it reminds you to capture what can be observed, measured, or verified rather than relying on adjectives.
Competency
Evidence prompt
Proof to capture
Collaboration
When did you work through different priorities or viewpoints with others?
Your role, the disagreement or dependency, and the shared outcome
Drive for results
When did you move an important task or project toward a concrete result?
Target, deadline, output, or measurable change
Customer focus
When did you identify and respond to a customer or user need?
Need discovered, action taken, and customer or user response
Influencing for impact
When did you persuade people without relying only on formal authority?
Stakeholders, reasoning, decision, and resulting action
Judgment
When did you make a decision with incomplete information or competing risks?
Options considered, trade-off, decision, and consequence
Adaptability
When did you adjust after a change, setback, or new requirement?
What changed, how you responded, and what improved
The matrix does not need to contain six unrelated projects. A single experience can appear in multiple rows if your actions genuinely demonstrate different competencies. For example, suppose you coordinated a delayed software launch. Under collaboration, you might focus on how you aligned engineering and communications. Under judgment, you might focus on how you assessed launch risks. Under adaptability, you might focus on how you changed the plan after a critical dependency moved. The facts remain the same, but the evidence you emphasize changes.
Add a follow-up column to your private notes. For every story, predict questions such as “What was your specific contribution?”, “What alternatives did you consider?”, “How did you measure success?”, and “What would you do differently?” This prevents a polished opening answer from collapsing when the interviewer asks for detail.
Shape each example with STAR(R)
After collecting evidence, turn the strongest examples into concise story outlines. Microsoft explicitly recommends the STAR(R) model and specificity. Use it as a structure, not a speech: Situation establishes context, Task defines the responsibility or goal, Action explains what you personally did, Result shows what happened, and Reflection captures what you learned or would carry forward.
Build your resume with AI
Put these tips into practice. Our AI-powered builder creates ATS-optimized resumes tailored to your industry.
The Action section deserves the most attention. Candidates often describe what “we” did, then leave the interviewer to infer their contribution. Replace broad team language with precise ownership while remaining accurate. “I analyzed the customer complaints, grouped them by issue, and proposed a revised triage process” is more useful than “we improved support.” If the work was genuinely shared, explain your part and how it connected to the team’s work.
Results do not have to be dramatic or financial. Use a measurable result when one exists, such as time saved, completion against a deadline, adoption, error reduction, response rate, or volume handled. If no number is available, describe an observable result: a decision was made, a process was adopted, a risk was reduced, a customer received a resolution, or a team reached an agreed next step. Never invent a metric to make a story sound stronger.
Reflection is useful when it adds information rather than a generic lesson. It might explain how you now involve stakeholders earlier, test assumptions before committing resources, or communicate trade-offs more clearly. Keep the reflection short and connect it to the competency. For adaptability, for instance, you could say that the experience taught you to confirm dependencies at the start of a project and maintain a fallback plan when timing is uncertain.
Example: convert a vague answer into evidence
Vague version: “I am adaptable because I handled a change in project requirements and helped the team stay on track.” This names a quality but supplies little evidence. A stronger outline would say: “Two weeks before a reporting launch, the stakeholder changed the required output. I reviewed the new requirements, identified which existing work could be reused, proposed a reduced first release, and confirmed the trade-off with the stakeholder. We delivered the revised version by the original date, and I documented the remaining improvements for the next cycle. I learned to separate essential requirements from desirable additions before assigning work.”
The second version is still concise, but it gives the interviewer a situation, a personal action, a result, and a reflection. It also creates useful follow-up paths: why was the release reduced, how did you confirm the trade-off, and what did the documentation contain? That specificity makes the story easier to adapt to a question about adaptability, judgment, stakeholder management, or drive for results.
Find gaps before the interview
Your matrix is also a diagnostic tool. Mark each competency as strong, usable, or weak. “Strong” means you have a relevant story with clear personal action and a result. “Usable” means the example fits but needs sharper detail. “Weak” means you are relying on a claim, a group outcome, or an experience that does not match the role closely enough.
For a weak area, do not immediately invent a new story. Search more broadly through coursework, internships, part-time work, volunteer projects, student organizations, personal projects, or previous roles. The best example is not necessarily the most senior or impressive experience; it is the one that clearly demonstrates the behavior the employer wants to evaluate. If no close example exists, prepare a truthful adjacent example and explain what you did, what happened, and what you would do next time.
Run a final relevance check against the role. Ask whether each story proves a capability from the job description, reflects at least one employer-specific competency or principle, and contains enough detail for follow-up questions. Remove duplicates that demonstrate the same behavior in the same way. Keep a few flexible stories, but do not depend on one example for every answer.
Review the employer’s published competencies, principles, and role requirements.
Select your strongest evidence for each priority competency.
Write five-part STAR(R) notes, with the Action and Result sections most detailed.
Add one metric, observable result, or concrete proof wherever it is available.
Practice answering the likely question in your own words, then stop and invite follow-up questions.
Prepare a specific explanation of why this role and employer interest you, based on your research.
Use the stories naturally in the conversation
Employer-published competencies are preparation signals, not a script. Listen for the question’s actual emphasis before choosing a story. If asked about influencing, do not lead with a story merely because it contains teamwork. Choose the example where your reasoning changed a decision or moved stakeholders to action. If asked about customer focus, explain how you identified the customer’s need and what changed as a result, rather than simply saying that you value customers.
You can also use the employer’s language in a natural way: “That experience is the example I would use for adaptability because the requirements changed and I had to reorganize the plan.” Then tell the story in your own words. This shows that you understood the evaluation area without turning the answer into a recitation of company values.
Finally, keep your preparation materials easy to scan. A concise resume example library can help you review how your experience is framed, while the employer’s sources should remain the authority for its own competencies and principles. Your objective is a small, well-supported story bank: relevant examples, clear ownership, credible results, and enough flexibility to answer the question actually asked.