There's a category of professional skills that doesn't appear in most job descriptions, doesn't come up in most career services workshops, and isn't on most students' radar when they're preparing for interviews.
Amy Everson, Senior Director of University Recognition and Institutional Events at the American Public University System, named them in the State of Higher Ed webinar: navigating ambiguity, pivoting under pressure, rolling with unexpected changes.
These aren't abstract virtues or resume buzzwords. They're descriptions of specific, recurring professional situations: when the priorities shift midway through a project and no one tells you what to do next; when the approach you planned doesn't work and you have to adapt without a playbook; when the ground moves under you, new information, a changed requirement, a stakeholder who reverses course, and you have to find your footing quickly.
These situations happen constantly in professional environments. They're among the most important skills employers evaluate in interview processes. And almost no one coaches students to talk about them.
Why These Skills Go Unmentioned
The skills that appear in job descriptions and career coaching materials tend to be the ones that are easiest to define, measure, and evaluate through standard credential evidence. Communication skills can be assessed through writing samples and presentation practice. Technical skills have certifications. Leadership has organizational titles. Project management has completed projects.
Navigating ambiguity doesn't have a certification. It doesn't show up in a title. You can't list "pivoted under pressure" as a bullet point without explaining what that actually looked like.
The result is a gap in how students are coached to present themselves: they're prepared for the questions that fit standard frameworks, and underprepared for the more revealing questions that ask how they've handled real uncertainty, real setbacks, and real situations where the expected approach didn't work.
Employers know this gap exists. The hiring managers who ask "tell me about a time when you had to deal with a sudden change in priorities" or "describe a situation where you didn't know what to do next" are specifically trying to surface evidence that job description language and standard interview prep can't generate artificially.
The Skills You're Already Building
Here's what students often don't realize: they're developing navigating-ambiguity skills every day. They're just not recognizing them as professional skills, and definitely not preparing to discuss them in interviews.
A student carrying a full course load while working a part-time job and managing a leadership role in a student organization is managing constant competing demands, unexpected schedule conflicts, and shifts in priority that require ongoing judgment about what to do next. That's ambiguity navigation. But the student describes it as "being busy," not as a professional competency.
A student in a group project who keeps the project moving when two team members aren't contributing, the scope changes after the first draft is done, and the deadline gets moved up is navigating ambiguity, pivoting under pressure, and demonstrating professional problem-solving in an unstructured situation. But the student describes it as "it was a rough semester."
A student in a research role who discovers in week four that the hypothesis can't be supported by the available data, redesigns the approach, and produces a defensible conclusion anyway is demonstrating exactly the kind of critical-thinking-under-uncertainty that employers rank highest. But the student describes it as "things didn't go as planned."
The pattern is consistent: students have the experiences, they just don't recognize them as professional competencies or prepare to describe them in professional language.
How to Surface and Describe These Competencies
The first step is recognition: auditing your experiences for situations that involved genuine ambiguity, unexpected change, or unstructured problem-solving. Ask yourself when the plan changed in a way you didn't expect and you had to figure out what to do next; when you didn't know the right answer and had to make judgment calls with incomplete information; when you had to keep something moving when the people around you weren't sure what to do; when you started something without a template and had to develop your own approach; and when you delivered something that required navigating a constraint or obstacle you didn't anticipate.
Once you've identified the experiences, the description follows the same structure as any strong competency example: the situation (what the context was), the action (what you specifically did), and the outcome (what changed or resulted). What makes ambiguity and pivot examples powerful is the specificity of the challenge: "I didn't know what to do next" is honest and relatable in a way that makes the solution more impressive.
Consider the difference between saying a group project didn't go well because the scope kept changing, versus describing how, in the third week of a group project, a client changed the primary deliverable and two teammates wanted to restart from scratch, so the existing work was assessed against the new requirements, a majority of it was found still applicable, and the remaining timeline was restructured around building on what worked, resulting in an on-time delivery and a satisfied client.
The second version describes the same situation, a challenging group project, but provides evidence of prioritization under pressure, leadership through ambiguity, and structured problem-solving. Those are the competencies that differentiate.
What Employers Do With This Evidence
Hiring managers who ask about ambiguity and pivoting aren't looking for evidence of disaster avoidance. They're looking for evidence of professional judgment: whether a candidate has a track record of functioning effectively when conditions are imperfect.
Most professional environments involve imperfect conditions constantly. The resources are insufficient, the timelines are tight, the requirements are unclear, and the people involved have competing priorities. Candidates who have demonstrated they can function productively under those conditions, and who can describe that functioning clearly, are lower-risk hires than candidates who have only worked in structured, predictable environments.
The evidence doesn't have to come from high-stakes situations. A well-described example from a student job, a challenging course, or a co-curricular leadership role can be just as compelling as an example from a prestigious internship. What matters is the specificity of the challenge and the quality of the judgment the candidate describes.
Frequently Asked Questions
How do I answer "tell me about a time you failed" in a way that demonstrates these competencies?
Focus on the pivot and the learning rather than the failure itself. Describe what you were trying to do, what didn't work and why, what you adjusted, and what you concluded about how to approach similar situations differently. The honest acknowledgment of what didn't work, combined with evidence of adaptive response, is much more compelling than either minimizing the failure or over-dramatizing it.
What if I don't have examples where I had to navigate major ambiguity?
Start looking differently at the experiences you do have. Most students underestimate the ambiguity in their existing experience because they experienced it as stress rather than as skill-building. The group project where everyone was confused is an ambiguity example. The job shift where something unexpected happened is an ambiguity example. The class where the expectations weren't clear is an ambiguity example.
Is it okay to use academic examples for professional competency questions?
Absolutely. Employers who ask about ambiguity and pivoting are evaluating the underlying judgment capability, not the professional context. An academic example that's specific and well-described is more compelling than a vague professional example.
How many of these examples should I prepare?
Two to three strong examples that span different types of experiences, academic, work, co-curricular, gives you coverage across different interview question formats. Each example should be specific, honest, and demonstrate judgment rather than luck or circumstances.
The skills employers screen for most carefully in interviews are the ones students are least prepared to discuss. That's a fixable problem. Audit your experiences for the moments when the ground moved and you kept your footing. Those are the stories that differentiate. For the full data on what employers prioritize and what drives career readiness, read the 2026 State of Higher Ed Report.
