An illustrative example, not a required script
A useful conversation starts with a clear ask.
You do not need a finished plan before asking for help shaping one.
Start with the work you already have
For a first engineering ticket, growth can mean tracing the code and explaining a proposed change before asking for an implementation. Timebox the investigation, ask for a hint when stuck, and check the explanation against actual behavior.
A mentor ask: Could you review my understanding and ask questions before suggesting a solution?
Evidence of learning: I corrected my explanation after tracing the request, then handled a similar change with less guidance.
How practice can expand over time
- Understand a change: Interpret a ticket, trace code, test assumptions, and explain what happens.
- Own a bounded change: Plan, implement, debug, and verify a small change with less guidance.
- Reason about a system: Connect components, compare alternatives, and anticipate failures and operational effects.
- Work across boundaries: Understand other teams’ constraints, dependencies, and downstream effects.
- Improve how others work: Develop others’ judgment and improve decisions across a broader area.
These are practice choices, not ranks. You might handle broad testing concerns while building confidence in unfamiliar application code. Repeat, try another context, or widen scope when the evidence and opportunity support it.
Before the conversation
Where I am now: I can propose solutions but struggle to explain the trade-offs.
What I want to develop: Compare options and recommend one using the team’s constraints.
My ask: Could I lead the options discussion for the next API change?
Questions: Is that an appropriate scope? What would a strong comparison show? Who could give me feedback?
After the conversation
What I heard: Start with retry behavior rather than the entire API.
My next action: Compare two retry strategies and write down their constraints by Thursday.
What I’ll bring back: Feedback on my comparison, the decision rationale, and what happened when we tried it.
If that opportunity isn’t available
Ask what smaller existing task could provide practice, or seek feedback from a peer. Record the constraint and choose a realistic next step. A postponed conversation does not prevent you from working independently.
Examples to adapt to your situation
Ownership
A vague request: I need more responsibility.
Earlier-career example: Could I own the rollout checklist for this change, with feedback on the risks I identify?
Experienced-engineer example: Could I coordinate the next cross-team rollout and review how I resolve ownership gaps?
Useful evidence: The risks identified, decisions made, feedback received, and rollout result.
A completed task alone doesn’t establish growth. Discuss the quality of your judgment and what changed in how you worked.
Design judgment
A vague request: I want to get better at architecture.
Earlier-career example: Could I compare two retry strategies and get feedback on my reasoning?
Experienced-engineer example: Could I lead the trade-off discussion across the affected services and have a peer challenge my assumptions?
Useful evidence: Constraints, alternatives, review feedback, and whether the decision held up in practice.
A completed task alone doesn’t establish growth. Discuss the quality of your judgment and what changed in how you worked.
Communication
A vague request: How do I communicate better?
Earlier-career example: Could you review one proposal and tell me where the intended decision is unclear?
Experienced-engineer example: Could I frame the next disputed decision for both teams and get feedback on how I surface their constraints?
Useful evidence: What readers understood, revisions made from feedback, and the resulting decision.
A completed task alone doesn’t establish growth. Discuss the quality of your judgment and what changed in how you worked.
Cross-team influence
A vague request: I need more visibility.
Earlier-career example: Could I explain our integration issue to the partner team and get feedback on the handoff?
Experienced-engineer example: Could I bring the teams together around one shared reliability constraint and get feedback on how I build agreement?
Useful evidence: Constraints uncovered, explicit commitments, remaining disagreements, and subsequent outcomes.
A completed task alone doesn’t establish growth. Discuss the quality of your judgment and what changed in how you worked.