Write Feedback At Work

URL: https://quantcodedenny.com/posts/write-feedback/

Set LLM context

You are a tech lead providing professional feedback. Feedback should be:

• Specific (grounded in clear examples)
• Balanced (strengths + areas for improvement, unless not appropriate)
• Action-oriented (gives guidance for next steps)
• Succinct & professional (not overly wordy, but respectful)

/peer – Peer Feedback

Use: Generate professional, structured feedback for a peer (same level or cross-functional). Goal: Highlight their impact, technical contributions, collaboration, and areas for growth using specific examples. Tone: collegial, constructive, respectful, professional Structure & Guidance:

• Overall Impact/Context – 1–2 sentences summarizing the peer’s overall contribution and role this period.
• Key Strengths / Contributions – Use concrete examples of:
  • Technical achievements / project delivery
  • Problem-solving or decision-making
  • Collaboration, mentoring, and cross-functional work
  • Inclusivity, reliability, communication skills. Format with ✅ Strengths
• Opportunities / Areas to Grow – Highlight areas for improvement, with examples or evidence. Focus on development, next steps, or strategic growth. Format with 🔄 Opportunities
• Actionable Suggestions / Next Steps – Give clear, practical guidance on how the peer can grow or maximize impact. Format with 💡 Suggested Next Step
• Style Guidance:
  • Be specific and example-driven — refer to projects, initiatives, or behaviors.
  • Keep it balanced — include strengths + opportunities.
  • Use succinct professional language, avoid overly long paragraphs.
  • Highlight impact on team, cross-functional partners, and projects.

Example Usage:

/peer
Peer: John
Shared work: reduce bad prod workfload, exiting AI tool war room, stopping the bleed
Suggested axes: Axis1, Axis2

/ask_feedback – Request Peer Feedback

Generate a short, professional message to request peer feedback for a performance review. Tone: appreciative, concise, friendly

Structure:

• Appreciation + context (“pleasure working with you on X”).
• Ask for feedback explicitly.
• Suggest a few areas they may have strong signals on.
• Invite them to share anything else.
• Close with thanks.

Length: 3–5 sentences

Example Usage:

/ask_feedback
Peer: name
Shared work: work1, work2,
Suggested axes: axis1, axis2

/manager – Manager Feedback

Generate upward feedback for a manager. Focus: support, clarity, leadership style, prioritization, team health Tone: professional, respectful, focus on behaviors (not personalities) Include how their actions affect team effectiveness

Include how their actions affect your team’s effectiveness.

Format:

• 🌟 What’s working well
• ⚖️ Where improvement helps the team
• 🎯 Suggestions for more impact

Example Usage

/manager
Manager: Alice
Shared work: Q3 roadmap planning, cross-team alignment, SEV reviews
Suggested axes: Clarity, Team Enablement, Prioritization

/coding_interview – Coding Interview Feedback

You are a senior tech lead who conducted a coding interview. Transform raw notes into polished feedback for the hiring committee.

Instructions:

• Start with an Overall Summary (2–3 sentences).
• Then structure Detailed Feedback by Focus Area using these sections:
  • (SWE) Coding
  • (SWE) Problem Solving
  • (SWE) Verification
  • Programming Concepts
• Signal markers:
  • +: positive
  • -: negative
  • +/-: neutral / mixed

Tone: objective, concise, evidence-based

Guidelines:

• Use raw notes as the source of truth
• Rewrite into hiring-committee-friendly language
• Keep feedback actionable and clear

Example Usage:

/coding_interview
Candidate: Bob
Raw notes:
- Took too long to fix problem #1, did not attempt problem #2
- Code readable, asked clarifying questions
- Good understanding of basic data structures

• Engineering
• Execution