Feedback

Feedback is how teams learn, adapt, and improve. It's the mechanism by which individuals grow, products get better, and organizations become more effective. Without feedback, we're all operating in the dark—assuming our work is landing when it might not be, missing opportunities to improve, and letting small problems grow into large ones. The ability to give and receive feedback well is one of the most important skills you can develop as an engineer.

The arc of growth in feedback moves from learning to receive it gracefully to building cultures where it flows freely. Early in your career, you're developing openness and learning to see feedback as a tool for growth rather than judgment. As you progress, you become skilled at giving specific, constructive input, then at shaping feedback culture on your team, and eventually at embedding feedback into the systems and practices of the entire organization. At every stage, the core purpose remains the same: helping people and systems get better.

Early Career

At this stage, you're starting to understand that feedback is part of your job, not just something that happens in performance reviews. You may be new to giving or receiving feedback in a professional context, and that's okay. This is about developing openness, curiosity, and basic skills.

You may not yet feel confident offering suggestions or critique, but you're learning to listen well, receive feedback without defensiveness, and ask for input when you're unsure.

What This Looks Like

You're building the foundation of a healthy relationship with feedback. You listen without becoming defensive and thank others for their input, even when it's hard to hear. You incorporate simple suggestions into future work and ask for clarification when feedback is unclear. Perhaps most importantly, you're beginning to ask for feedback on your work and behavior, rather than waiting for it to come to you.

It's natural at this stage to take feedback personally or shut down emotionally. You might be unsure when or how to ask for feedback, or hesitate to offer any yourself. There's often a tendency to over-focus on praise and avoid critique, seeking validation rather than growth. These are common patterns—recognizing them is the first step toward outgrowing them.

The Shift

The fundamental shift at this stage is moving from seeing feedback as scary or personal to understanding it as a tool that helps you get better and build trust. Feedback isn't judgment—it's information. When you internalize this, you start to see every piece of input as an opportunity to learn.

You'll know the shift is taking hold when you show openness and a willingness to learn from feedback, when you act on constructive input in your day-to-day work, when you ask for feedback without prompting, and when you begin to see feedback as a path to growth rather than a threat to your standing.

How to Grow

Start by asking yourself reflective questions: What can I learn from this, even if it's hard to hear? Who do I trust to give me honest input? When have I grown because of someone's feedback? These questions help you approach feedback with curiosity rather than fear.

Build habits around actively seeking input. Ask for feedback on specific aspects of your work—code quality, communication, how you handled a situation. Reflect before reacting to feedback, giving yourself time to process rather than responding defensively. Write down recurring themes or suggestions to track your growth over time. And always say thank you when someone offers feedback, even if you disagree.

You'll know you're ready to move to the next stage when you invite feedback regularly and with specific questions, when you respond with maturity and curiosity, and when others feel safe giving you honest input. Building the muscle of receiving input well is the foundation for everything that follows.

At the early career stage, feedback is about developing openness—building the muscle of receiving input well, and seeing it as a path to growth.

Mid-Level Engineer

As a mid-level engineer, feedback becomes a regular part of your workflow. You not only receive it gracefully—you also begin offering it, especially in areas like code reviews, technical design, documentation, and collaboration.

You're learning how to give specific, constructive input that helps others improve. You see feedback as part of working well with others—not just correction, but contribution.

What This Looks Like

You give thoughtful feedback on code reviews and technical documents. You offer both positive and constructive input, recognizing that people need to know what's working as well as what could be better. You use questions to guide others toward insight—"What do you think about...?"—rather than simply telling them what to do. You respond to feedback with curiosity and follow-up, and you regularly ask for input on your technical decisions and work quality.

The challenges at this stage often involve calibration and courage. You might avoid giving feedback in high-stakes situations, or give vague, overly general feedback like "looks good" that doesn't actually help. Striking the right tone is tricky—too soft and the message doesn't land, too blunt and it damages the relationship. You might also take critical feedback on your technical work personally, even when it's offered constructively.

The Shift

The shift at this stage moves from seeing feedback as a task or critique to understanding it as collaboration and investment. When you give feedback, you're not criticizing—you're contributing to someone's success. When you receive it, you're not being judged—you're being helped.

You're succeeding when you offer specific, helpful feedback in pull requests and team discussions, when you treat feedback as a normal, healthy part of collaboration, when you ask for feedback before it's too late to change course, and when you communicate feedback in a respectful, timely, and constructive way.

How to Grow

Build habits around timing and specificity. Offer feedback soon after the event, not weeks later when the context has faded. Balance critique with curiosity and encouragement. Be clear, kind, and focused on impact—what's the change you're hoping to see?

Ask yourself: What feedback will help this person or project succeed? Have I delivered feedback in a way that builds trust and clarity? Am I modeling the kind of feedback culture I want to be part of? Seek feedback on your feedback—ask teammates: "Was that code review helpful or overwhelming?" or "Is there something I missed in your approach?" or "How can I improve the way I give feedback?"

You're ready to move to the next stage when teammates seek out your input on technical and team matters, when your feedback improves outcomes without damaging trust, and when you're known for being honest, thoughtful, and respectful. At that point, feedback becomes a tool you use daily—not just to improve your work, but to help your team grow.

As a mid-level engineer, feedback is about contributing—using it daily to improve your work and help your team grow.

Senior Engineer

As a senior engineer, you are actively shaping the feedback culture on your team. You give high-quality, actionable feedback that strengthens products, processes, and people. You've developed the confidence to deliver difficult messages constructively—and the humility to welcome the same in return.

You're often a go-to reviewer for tricky code, design decisions, or communication strategies because people trust your insight and tone.

What This Looks Like

You deliver feedback that improves not just the outcome but the person. You address sensitive topics with clarity and compassion, spotting patterns in a teammate's work and providing growth-oriented input. You give structured, detailed feedback during design or strategy reviews, and you create space for others to give you honest feedback in return. Your feedback is remembered, acted on, and appreciated.

The risks at this stage involve overcorrection. You might become overly critical or prescriptive, forgetting to celebrate what's working. You may under-communicate praise when focused on improvement, or assume others are as comfortable with feedback as you are. Some people need more context or more care in how feedback is delivered—meeting them where they are is part of the skill.

The Shift

The shift at this stage moves from giving helpful feedback to creating a team where feedback flows freely and constructively. You're not just a good feedback-giver—you're a feedback culture builder. You're thinking about who gets feedback regularly and who might be left out, whether tensions are surfaced early enough to act on, and what habits could normalize high-quality feedback across the team.

You're succeeding when you use feedback to raise the bar on quality, thoughtfulness, and collaboration, when you adapt your style based on the person and situation, when your feedback is remembered and acted on, and when you model receiving feedback with humility and grace.

How to Grow

Champion feedback in rituals like retros, 1:1s, and design critiques. Offer feedback upward or cross-functionally with respect and clarity—it's often harder to give feedback to peers or those with more power, but it's equally important. Highlight feedback that led to improvements or changed your perspective, normalizing the idea that everyone benefits from input.

Ask yourself: Who gets feedback regularly—and who might be left out? Are we surfacing tensions early enough to act on them? How can we create habits that normalize high-quality feedback? Seek feedback on your feedback: "Was that helpful, or did it feel too strong?" or "How do you prefer to receive feedback on your work?"

You're ready for the next stage when people credit your feedback with helping them grow, when others emulate your style in how they give and receive feedback, and when feedback becomes easier, more honest, and more useful across your team. You're raising the quality and frequency of feedback around you.

As a senior engineer, feedback is about culture-building—raising the quality and frequency of feedback around you.

Staff Engineer

As a staff engineer, you scale a healthy feedback culture beyond your immediate team. You mentor others on how to give and receive feedback, and you embed feedback loops into systems, processes, and decision-making.

You help normalize feedback in higher-stakes settings—like cross-team collaborations, leadership discussions, or postmortems—and you model how to do it well.

What This Looks Like

You mentor others on how to deliver clear, constructive feedback. You introduce or improve feedback practices across teams or organizations. You facilitate conversations that resolve tension and deepen trust, surfacing hard truths in a way that leads to action rather than defensiveness. You make sure feedback flows across levels, roles, and functions—not just within teams.

The challenges at this stage are about sustainability and access. You may be stretched thin supporting others through feedback challenges, becoming a bottleneck for difficult conversations. If you're seen primarily as the giver of feedback, you might struggle to get feedback yourself. And the emotional labor of supporting others through feedback can lead to burnout if it's not distributed.

The Shift

The shift at this stage moves from mentoring individuals on feedback to helping systems learn, adapt, and improve through feedback. You're thinking about where feedback stalls or disappears in your organization, whether feedback is being used to improve systems rather than just individuals, and how feedback can support long-term strategy and values.

You're succeeding when you shape a culture where feedback is timely, thoughtful, and routine, when you equip others to give and receive feedback with skill and care, when you model feedback even when stakes are high or dynamics are complex, and when feedback culture is inclusive—not just available to the most vocal or confident.

How to Grow

Partner with leadership to embed feedback into organizational practices. Push for feedback loops in performance, planning, and product development. Ensure psychological safety in moments of conflict or change—people can only give and receive honest feedback when they feel safe doing so.

Ask yourself: Where does feedback stall or disappear in our organization? Are we using feedback to improve systems, not just individuals? How can feedback support our long-term strategy and values? Seek feedback from across the organization: "Where is feedback not landing—and what would make it more useful?" or "How do feedback practices differ across teams, and what can we learn from that?"

You're ready for the final stage when feedback processes scale across organizations or disciplines, when leaders look to you to help navigate tricky feedback moments, and when your influence shows up in how people give and receive feedback even when you're not in the room. You're a builder of systems and culture.

As a staff engineer, feedback is about systems—building the structures and culture that enable feedback to thrive at scale.

Principal Engineer

As a principal engineer, you lead with feedback at an organizational level. You don't just shape culture—you design and sustain systems that support growth, accountability, and trust.

You influence how the company thinks about learning, performance, and improvement. Feedback becomes a strategic advantage.

What This Looks Like

You embed feedback as a pillar of leadership, performance, and culture. You partner with executive leadership to design organization-wide feedback practices and advocate for company-level changes based on feedback insights. You drive alignment between feedback, values, and business outcomes, creating conditions where teams and leaders continuously improve.

The challenges at this stage are about balance and authenticity. There's a risk of over-systematizing feedback and losing the human nuance that makes it effective. Balancing consistency with flexibility across teams or functions requires judgment—what works in one context may not work in another. And maintaining credibility and openness as your influence scales means continuing to receive feedback yourself, even when it's harder to get.

The Shift

The final shift moves from helping systems learn through feedback to making feedback a defining feature of how the company leads, learns, and grows. You're asking: How does our feedback culture feel on the ground? What feedback have we institutionalized—and is it still useful? What are we missing because we're not hearing it?

You're succeeding when you champion a feedback culture that aligns with company values and mission, when you build scalable systems for feedback that empower individuals and teams, when you influence how leaders lead through feedback, and when feedback becomes a strategic asset—not just a management ritual.

How to Grow

Support systems that close the loop on feedback—ensuring that input leads to action and that people see the impact of what they've shared. Build infrastructure for learning, reflection, and accountability. Develop leaders who grow others through feedback, multiplying your impact across the organization.

Ask yourself the deepest questions: How does our feedback culture feel on the ground? What feedback have we institutionalized—and is it still useful? What are we missing because we're not hearing it? Seek feedback from the broadest possible set of perspectives to ensure you're not operating in an echo chamber.

Few things shape a company's trajectory more than how honestly people can talk to each other. Your growth continues through becoming more effective at designing feedback systems, more skilled at influencing how leaders develop their people, more attuned to what the organization needs to hear. You may also find that your growth takes you into adjacent domains: shaping industry standards around organizational learning, mentoring the next generation of culture builders, or contributing to how the broader community thinks about feedback as a strategic lever.

As a principal engineer, feedback is about legacy—making it a defining feature of how the company leads, learns, and grows.