Career Goals and Progression Questions

Direct answer

Pick a project you chose deliberately because it filled a specific, named gap in your experience or visibility, not just one that landed on your desk, and be concrete about the one thing that measurably changed in your trajectory afterward, a capability, a relationship, or a type of work you're now trusted with.

Structured elaboration

• Name the specific gap the project targeted. A skill, a type of stakeholder exposure, a kind of ownership, not "it seemed interesting."
• Distinguish accelerant projects from ordinary assigned work. You sought it out or volunteered specifically because of the gap; that intentionality is the actual signal being tested.
• Point to something durable in the "what changed" half. A new kind of work you're now trusted with, a relationship that opened later opportunities, or a capability you now use routinely, versus just "it went well."
• Keep it forward-looking. The project itself is evidence; the answer is really about what it changed about how you're used or seen now.

Worked example

Partway into a role, I noticed a gap in my own experience: I'd never owned something end to end in front of a skeptical stakeholder audience, only ever as part of a larger team. When a short, high-visibility project came up that nobody else wanted because of the tight timeline, I volunteered specifically because it forced that gap. I ran it end to end, made the calls, and presented the outcome directly to the stakeholders who'd been skeptical going in. What actually changed afterward wasn't the project's result, it was that I started getting pulled into that kind of stakeholder-facing, ambiguous work as a matter of course, work I'd never have been offered before proving I could carry it alone.

Trade-offs & pitfalls

• Choosing a project purely because it's visible, without it targeting a real gap, produces a story about luck rather than intentional growth.
• Framing the outcome as "and it went well" rather than naming what changed afterward misses the actual question, the interviewer wants the trajectory change, not the project recap.
• Volunteering for something without being honest about the real risk, a tight timeline, being out of your depth, undersells the growth; own the discomfort as part of the story.

Direct answer

The move is to separate diagnosis from reaction: before assuming the gap is unfair (inconsistent criteria, an indifferent manager) or purely a personal failing, do an honest, evidence-based audit of your own case first, then act on what you actually find rather than on the story you started with. That self-diagnosis is what keeps the response grounded instead of either resigned or entitled.

Structured elaboration

1. Name the trigger honestly, whatever it actually is: no advancement across two review cycles, criteria that seem to shift depending on who's managing you, or just a general sense of plateauing. Treat it as a starting observation, not a verdict.
2. Diagnose before reacting. Audit your own evidence (scope actually carried, outcomes attributable to you, feedback received) against whatever the organization's stated or informal bar is. Separately, note if the bar itself looks inconsistent or unclear across managers, that's useful information, not an excuse to skip the audit.
3. Have the direct conversation. Bring your honest self-assessment to your manager and ask explicitly what's missing, rather than silently accumulating resentment or silently giving up on the goal.
4. Decide on a bounded response. Set a real timeframe to see change, and know your own answer for what you'd do if nothing changes, without turning that into an ultimatum in the room.

Worked example

"At one point I'd gone through two review cycles without the scope change I was expecting, and it would have been easy to decide either that the process was broken or that I just wasn't good enough. Instead I sat down and mapped what I could actually point to: had I taken on next-level work, could I show outcomes that were mine, had anyone besides me confirmed it. Some of it held up, some didn't, there was a specific kind of cross-team decision I'd been avoiding making solo. I brought that honest picture to my manager instead of a complaint, asked directly what was missing from their side, and used what came back to set a concrete plan with a real check-in date rather than just waiting quietly for the next cycle."

Trade-offs & pitfalls

• Skipping the self-diagnosis and going straight to a conversation framed as a grievance is the entitled failure mode interviewers are listening for.
• Quietly disengaging or lowering your own ambition instead of raising the issue is the opposite failure mode, and just as costly.
• Blaming inconsistent criteria across managers without also checking your own evidence dodges the harder, more useful half of the question.
• Setting no real timeframe for reassessment lets "wait and see" drift indefinitely. A grounded answer names when you'd revisit the decision.

Direct answer

At the next level the shift is from executing well defined work to owning the definition of the work itself, making calls that currently need someone else's approval, and being accountable for outcomes beyond your own output. The honest test of a good answer is naming a specific decision type you don't yet own, not describing a vaguely bigger job. What would actually change is which decisions route to you first instead of to your manager, and which outcomes you're accountable for even when you didn't personally do the work.

Structured elaboration

Name the current boundary. State plainly what you own today: you execute assigned work reliably and flag risks, but calls above a certain size still route through your manager or a review.

Name the specific decisions that would move. Pick concrete decision types, not scope words. Sign-off on a class of technical or design trade-offs, direct negotiation of priorities with adjacent teams instead of relaying through a manager, representing your area in reviews without a chaperone.

Choose a credible vehicle. A few common paths show you've thought about mechanism, not just outcome: becoming the domain lead for a defined slice, the person others route decisions to for that area; taking a Tech Lead step, coordinating technical direction before any title changes; or demonstrating staff level individual contributor (IC) leadership without a manager title, driving cross team outcomes through judgment rather than headcount.

Build the evidence trail. Decision rights expand when you have a record of good decisions under less oversight. Volunteer for ambiguous problems, document your reasoning so it's auditable, catch your own mistakes before someone else has to.

Expect the time mix to shift. As scope moves toward you, your week shifts from mostly delivery toward more judgment calls, review, and framing problems for others, often the first visible sign the scope changed before any title does.

Worked example

"In my current role I own execution well, but any decision affecting another team's roadmap still gets escalated to my manager. Two teams kept colliding on the same shared dependency, and each time it went to my manager to referee. Instead of saying someone should own this, I proposed taking the domain lead role for that shared area for one planning cycle, gathering both teams' constraints and proposing the trade off myself, escalating only if we couldn't agree. My manager agreed to a trial. I ran two of those conversations, documented the reasoning each time, and by the end of the cycle both teams were routing that kind of conflict to me directly. That's the evidence I'd bring into a scope conversation, not that I want more responsibility, but a specific decision I already made well, repeatedly, without oversight."

Trade-offs & pitfalls

• Describing scope growth as more of the same work reads as ambition without a plan.
• Picking a vehicle that doesn't match your organization, pushing for a formal Tech Lead title in a flat org that doesn't use that ladder, wastes the conversation on semantics.
• Conflating volume with scope. Taking on more tickets is not the same as gaining authority over a new kind of decision, and a reviewer notices the difference immediately.
• Overclaiming scope you can't back with a track record invites the exact pushback (show me you've done this already) that a demonstrated vehicle avoids.

Direct answer

Structure it as an evidence led case, not a request for a favor. Open by naming the specific ask, promotion, a stretch assignment, or dedicated time and budget, back it with three or four concrete instances of impact and readiness, and pre-empt the most likely objection with a fallback. The conversation should feel like two people already broadly aligned on the goal, working out timeline and specifics, not a persuasion contest.

Structured elaboration

Open with the ask itself. Name what you want as your first sentence, not your last. Ambiguity in the open lets the conversation get steered before you've made your case.

Bring evidence, not adjectives. Two to four concrete instances where you already operated at the level you're asking for, a project led beyond formal scope, a decision others now rely on, a skill built and applied. Evidence should be specific enough that your manager could describe it to their manager without you in the room.

Anticipate the likely objections. There's no open role at that level, the timing is wrong for budget, you need more evidence in one area. A prepared response isn't a rebuttal, it's a next step, what would close the gap and by when.

Bring a fallback. If the primary ask can't be granted in full, have a smaller alternative ready, an interim scope change, a defined stretch project with a review date, or a partial commitment such as title now and a compensation review next quarter. Arriving with only one possible outcome makes it binary and easy to defer.

Close with a mechanism. Propose a specific follow up date and what would need to be true by then for the answer to change.

Worked example

"I asked for time on my manager's calendar and opened directly, saying I wanted to talk about taking the stretch assignment leading the migration project and what that meant for my scope going forward. I brought three examples where I'd already operated at that level informally, a cross team escalation I'd resolved without waiting for my manager, a proposal the team had adopted, and feedback from a peer who said they now came to me first on a certain class of problem. My manager's first response was that the team couldn't spare me from current work. I'd anticipated that and offered a fallback, take the assignment for the first phase only with a defined handoff point, so my current responsibilities weren't left uncovered. We agreed to that scope, with a check in scheduled for the midpoint to decide whether to extend it."

Trade-offs & pitfalls

• Leading with feelings instead of evidence invites the manager to respond to the emotion rather than the case.
• Bringing only one possible outcome, with no fallback, turns the conversation into a yes or no vote you can lose outright.
• Overloading the evidence list dilutes it. Two or three strong, specific instances beat six vague ones.
• Skipping the close is the most common gap. A conversation that ends without an agreed next step tends to quietly disappear from both people's priorities.

Direct answer

A promotion packet is a structured evidence file built over months, not written the week before the review. It has an impact summary, a scope and ownership section, a section that explicitly counts non-technical contributions, and a visibility trail showing others already recognized the work before the packet existed. The packet documents evidence, the persuasive conversation that uses it is a separate skill and belongs in the room, not on the page.

Structured elaboration

The non-technical ledger is the section most packets under-build. Mentoring and documentation are real promotion evidence and should be quantified in terms you can actually verify, not vague credit.

The visibility trail has two strong levers. Turning a side project into a visible internal product, something that started as personal initiative and is now relied on by others, and building an external technical brand, a talk, an open source contribution, or public writing, that puts your name on the work before the packet does.

Building visibility so the packet isn't a surprise means never letting it be the first time your manager, or their manager, hears about the work in it. Share progress in venues that already exist, be deliberate about which pieces of work you narrate publicly, and invest consistently in one or two visibility levers rather than spreading thin.

Worked example

"Over the year before my review cycle I kept a running log of contributions as they happened, not reconstructed at the end. When I built a small internal tool to solve a recurring problem on my team, I didn't stop at solving my own problem, I documented it, offered it to an adjacent team, and it ended up adopted as the default approach for that class of problem, a side project that became a small internal product. Separately I wrote up a design decision as an internal post, which a colleague on another team referenced months later solving a similar problem, so I had a quoted instance of influence beyond my own team. When I assembled the packet, the non-technical ledger included the two people I'd onboarded that year with specific notes from them on what helped, plus a piece of documentation that became the team's reference for a process I'd designed. None of this was manufactured for the packet, it was work I'd done anyway, tracked as I went."

Trade-offs & pitfalls

• Building the whole packet in the final month reads as reverse-engineered and gives peers no time to corroborate it.
• Treating mentoring and documentation as filler instead of first-class evidence under-sells real work that reviewers weight more than most candidates expect.
• Over-investing in external visibility at the expense of internal scope evidence. External brand supports the case, it doesn't replace it.
• Keep the packet as evidence and artifacts, save the persuasive framing and objection handling for the conversation itself, or the packet reads as a sales pitch instead of a record.