Lesson 7 of 8 · 48 min

Scope, prioritization, mentorship, influence without title

Prioritization spines with real no's, mentorship with skill deltas, influence without authority via artifacts, standards/bar-raising, professional refusal language, and level calibration.

Leadership without a people-manager title

Senior loops ask how you prioritize, mentor, and influence when you cannot decree. This is not resume coaching about 'leadership skills.' It is evidence of leverage: you multiplied outcomes through scope choices, standards, and other humans. Builders who only tell pure IC hero stories under-score here.

Prompts: how do you prioritize; time you mentored someone; influenced without authority; said no; led a cross-team effort; raised the bar. All probe scope control + people leverage + standards.

Influence without title is not politics as theater. It is building shared reality with artifacts: design docs, metrics, prototypes, RFCs, office hours, crisp escalations.

Prioritization stories

code

1PRIORITIZATION SPINE23  Incoming demand (N items) → criteria (user harm, revenue, risk, learning) →4  ranking → explicit no's → communication to stakeholders → result of the yes →5  what you revisited later.67  Senior signal: criteria named before favorites. Non-goals written.

Bring a story where saying no was costly socially but correct for the metric. Pleasant prioritization only is weak.

Worked prioritization story

code

1PROMPT: How do you prioritize?23  Context: 1 IC + 0.5 shared designer; backlog had 14 'P0' requests.4  Criteria: (1) checkout user harm (2) launch-blocking (3) eng leverage.5  Yes: payment success alert gap + suggest latency (launch + harm).6  No: admin cosmetic redesign; new experimental badge (deferred with date).7  Comms: one-pager ranked list to PM/EM; kill criteria if launch moved.8  Result: launch hit; p95 latency win; redesign scheduled post-launch without drama.

Mentorship that is not vague coaching

Mentorship stories need a person, a skill gap, a method, and a delta. 'I mentored juniors and it was rewarding' scores near zero.

code

1MENTORSHIP SPINE23  Who + starting state → goal skill → your method (pair, review bar, design drills) →4  awkward moment → their independent outcome → what you changed in team practice.

code

1WORKED MENTORSHIP23  New mid-level wrote large PRs without rollout plans. I set a review bar: every4  prod PR needs flag/metric/rollback note. Paired on two deploys. Awkward moment:5  first blocked PR felt personal; I separated standards from worth.6  Outcome: their next three ships had canaries; they later enforced the bar on others.7  Team: checklist added to PR template.

Influence without authority

You need a story where the people who had to move did not report to you. Tools: shared metric, written proposal, prototype that falsifies fear, executive-aligned problem framing, coalition of peers.

code

1INFLUENCE MOVES23  1. Shared dashboard that made the problem undeniable4  2. Two-page RFC with options and ask5  3. Spike that de-risked the scary path in days6  4. Pilot with one partner team before global ask7  5. Decision meeting with clear owner, not endless Slack

Worked pattern: 'I could not order team B to adopt the schema. I built a compatibility layer + migration guide, piloted with one service, showed toil drop 30%, then got EM forum buy-in.'

Raising the bar / standards

Standards stories: code review bar, on-call hygiene, design review quality, testing norms. Show resistance, how you socialized the standard, and a measured or qualitative team delta.

01Standards need examples and templates, not only speeches.
02Apply the standard to your own work first.
03Measure something: revert rate, review time, page noise, incident repeat rate.
04Expect pushback; steelman cost of the standard.
05Leave ownership of the standard with the team, not only yourself.

Scope: saying no and protecting focus

code

1SAYING NO — PROFESSIONAL FORM23  "I can do A by date D. If we also need B, we slip D or drop C.4   My recommendation is A+C because [criteria]. If you need B first,5   say so and I'll replan."67  Offer the menu. Do not only refuse.

Weak vs strong influence endings

code

1WEAK2  "I convinced them with my communication skills and vision."34STRONG5  "Pilot reduced toil 30% on pilot; RFC adopted by EM forum; three services migrated6   next quarter; compatibility layer deprecated on schedule."

Level calibration

code

1  Mid:     solid prioritization on own backlog; some mentoring2  Senior:  cross-team influence; standards; explicit no's with criteria3  Staff+:  multi-team outcomes; develops other leaders; sets multi-quarter bets

Do not force Staff theater. Deep senior influence on a real interface is enough for most loops if evidence is sharp.

Title grants authority. Artifacts grant influence. Interviews hire for the second when the first is missing.

Mining checklist

code

1  [ ] Ranked a brutal backlog with documented no's2  [ ] Mentored one person with a skill delta3  [ ] Drove adoption across a team you did not manage4  [ ] Introduced a standard that outlived you on the team5  [ ] Protected a deadline by cutting scope socially hard6  [ ] Unblocked a partner org with a prototype or adapter

articleAmazon LPs — Earn Trust / Think Big / Deliver ResultsAmazon Jobs articleTIH Behavioral leadership questionsTech Interview Handbook articleExponent behavioralExponent articleHello Interview behavioralHello Interview

Checkpoint

Which mentorship story is strongest?

AI love helping people and my door is always open for juniors on the teamBMid-level shipped large PRs without rollout plans; I enforced flag/metric/rollback notes, paired on two deploys; they later enforced the bar; PR template updatedCI told them to study harder and read documentation more carefully

Checkpoint

Best evidence of influence without authority?

AI argued until they adopted my vision because I was passionateBPilot reduced toil 30%; RFC + EM forum adoption; three services migrated next quarterCMy manager ordered the other team to comply after I complained

Checkpoint

You must refuse a stakeholder request. Strongest form?

ANo. That is not my priority. Thanks.BI can deliver A by D; adding B slips D or drops C; I recommend A+C because [criteria]; if you need B first I will replanCYes to everything, then silently under-deliver on the least favorite

Checkpoint

Why are prioritization criteria necessary in the story before the ranked list?

AThey are not; lists alone show decisivenessBCriteria show Judgment and let stakeholders disagree on inputs rather than only on your personalityCAmazon requires exactly three criteria every time

Checkpoint

Raising a code review standard meets resistance about speed. Best response pattern in the story?

AIgnore resistance and block all PRs until people comply out of fearBSteelman the speed cost, apply standard to your PRs first, measure revert/incident delta, iterate the checklistCDrop the standard immediately so people like you

Do you have stories for prioritization-with-no, mentorship-with-delta, and cross-team influence with artifacts?

New to itGetting thereConfident

Leverage locked

Prioritization: criteria → rank → documented no's → comms → result.
Mentorship: person, gap, method, delta, team artifact.
Influence without title runs on artifacts, pilots, and shared metrics.
Say no with a menu of tradeoffs, not a door slam.
Standards stick when self-applied and measured.

Next: capstone mock + story bank structure to run a full behavioral loop.

Sources

Free to read · better with Enzo

Learn it with Enzo

Save your progress, answer the checkpoints, and let Enzo quiz you on what you just read.

Continue with Enzo Sign up free