Career Goals and Progression Questions

Direct answer

Readiness shouldn't rest on a feeling, it rests on evidence you can point to: scope you've already been operating at before any title caught up, outcomes attributable to your own judgment, and calibration from people other than yourself. And where the organization doesn't have a clean rubric for the next level, which is common, a strong answer includes proactively asking your manager what evidence would actually count, rather than guessing at criteria that may not exist.

Structured elaboration

1. Separate feeling from evidence. Three categories: scope already carried at the next level informally, outcomes you can attribute to your own decisions rather than someone else's plan, and external calibration (peer, manager, or skip-level feedback, not just self-assessment).
2. Build toward it deliberately. Take on a piece of next-level scope early, track what you did and why, collect feedback along the way instead of waiting for a review cycle to surface it.
3. Where there's no formal ladder, close the ambiguity yourself. Name that condition honestly, then ask your manager directly what evidence would count for them, write down the answer, and revisit it periodically rather than assuming a rubric exists somewhere you just haven't seen.
4. Distinguish this from title-chasing. The evidence should describe genuine readiness for the next level's actual work, not tenure or hours logged.

Worked example

"At one point I suspected I was ready for more scope but had no rubric to check it against, our team didn't really have one written down. Instead of waiting, I asked my manager directly what would convince them, and got back three things: could I make a call without checking in first, could a newer teammate learn from working with me, and had anything I'd built outlived the project it was built for. I went and found real evidence for each of those over the following months instead of trusting a feeling of being ready, and used that same list when the promotion conversation eventually came up."

Trade-offs & pitfalls

• Relying purely on tenure, "I've been doing this for three years", is not evidence of next-level readiness.
• Assuming a rubric exists somewhere and waiting passively for someone to notice is a common and costly mistake in organizations without a formal ladder.
• Self-assessment alone, with no outside calibration, is one-sided and unconvincing to whoever eventually has to sign off.
• Overcorrecting into constant self-promotion without real artifacts reads as entitled. The antidote is genuine evidence and a direct question to your manager, not repeated assertion.

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 real difference isn't seniority, it's what you spend your energy multiplying. An individual contributor multiplies impact by going deeper into their own craft; a manager multiplies impact through other people's work, spending most of the day on unblocking, coaching, and prioritizing rather than building it themselves. Say which pull is stronger for you right now, and back it with a concrete signal, not just a stated preference.

Structured elaboration

To build the answer:

1. Name the actual mechanism each track uses to create impact, deepening a skill versus multiplying people.
2. Self-assess honestly against a real moment: did you want to take the hard problem yourself, or did you want someone else to grow by taking it?
3. Note the choice usually isn't permanent, many organizations support lateral moves or parallel tracks, which softens the stakes of naming a current lean.
4. Answer with a directional preference plus the evidence, not a hedge like "I like both equally."

Worked example

"A few months ago I had a choice: take point on a hard, ambiguous problem myself, or step back and let a newer teammate lead it while I coached from the side. I chose the second, on purpose, and noticed I got more satisfaction watching them work through the ambiguity and land the decision than I think I'd have gotten from solving it myself. That's the kind of moment I look back on when I say I'm currently drawn toward management, not just a stated preference."

Trade-offs & pitfalls

• Answering only in the abstract, "management is about people, the other track is about the work", with no self-assessment signal is incomplete.
• Presenting one track as inherently more senior or more valuable is a red flag to interviewers whose organizations run dual-track ladders on purpose.
• Treating the choice as permanent and irreversible, when in most organizations it isn't, overstates the stakes.
• A flat "I like both equally" with no lean reads as indecisive. Better to name a lean plus what genuinely still appeals about the other path.

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.

Direct answer

Don't argue the premise. Reframe scope as breadth of impact rather than headcount of teams touched, surface concrete evidence that your depth already produced value beyond your immediate team, and pair it with a dated, checkable plan for closing whatever gap is real.

Structured elaboration

• Separate whether the pushback is right from whether it's complete. Even genuinely deep, narrow work usually throws off reusable artifacts, informal mentoring, or unsolicited cross-team requests, find and name those rather than assuming the panel has the full picture.
• Categories of scope evidence beyond team headcount: tools or practices other teams adopted from your work, standards that outlived the original project, unsolicited requests for your input from outside your team, an improvement whose benefit reached other teams indirectly, and direct peer or stakeholder statements about your influence.
• The milder version of this same move, quantifying your influence on company-level KPIs (key performance indicators), not just team-level ones, is worth building into a promotion case proactively, even without a panel pushing back, rather than only pulling it out defensively when challenged.
• Acknowledge any genuine gap honestly, then attach a plan scoped to the next one or two review cycles with specific, checkable milestones, not a vague intention to "do more cross-team work."
• Tone matters as much as content. Agreeing with the legitimate part of the feedback lands better than arguing the premise; panels respond to "here's what already extended beyond my team, and here's exactly how I close the rest," not to defensiveness.

Worked example

When a promotion committee told me my influence looked narrow after a long stretch deep on one product, I didn't argue the premise. I went back through the year and pulled out everything that had actually left that product's boundaries: a utility I'd built for my own use that two other teams had since adopted, a set of monitoring practices another team copied after seeing them in a review, and specific unsolicited messages from peers on other teams asking me to weigh in on their design decisions. I hadn't been tracking any of that as "scope," only as good engineering. I paired that evidence with a concrete plan for the next two review cycles, naming the two teams I'd deliberately extend work toward and a milestone I could point to at each checkpoint. The panel's read shifted from "narrow" to "narrow so far, but closing on a plan."

Trade-offs & pitfalls

• Getting defensive or arguing the panel is simply wrong is the most common failure mode, even when you privately disagree.
• Overclaiming influence with specifics you can't stand behind under questioning is worse than admitting the gap plainly; panels probe.
• A plan with no dates or checkpoints reads as a promise, not a plan; always attach a review-cycle timeline.
• Confusing volume of your own output with scope; breadth means other teams' work changed because of yours, not how much of your own work you personally did.