360 Review Questions for Software Engineers

12 targeted questions to gather meaningful peer feedback. Covers collaboration, code quality, problem-solving, and team contribution.

Run Your 360 Review

What you'll learn

  • 12 copy-paste ready questions organized by category
  • Focuses on observable behaviors, not raw technical skill
  • Designed for IC engineers at all levels
  • Works for self-review, peer review, or manager assessment

Why These Questions Work

Generic 360 questions produce generic feedback. "Rate this person's communication skills" doesn't tell you anything actionable. These questions are specific to the engineering context and focus on observable behaviors that peers can actually assess.

Each question targets a specific competency that matters for engineering success—not just writing code, but collaborating effectively, maintaining quality, and contributing to team growth.

Technical Collaboration

Question 1

"How effectively does this engineer explain technical concepts to non-technical stakeholders?"

Question 2

"When disagreements arise about technical approaches, how does this engineer handle the discussion?"

Question 3

"How well does this engineer incorporate feedback from code reviews?"

Code Quality & Craft

Question 4

"How would you rate the clarity and maintainability of code this engineer produces?"

Question 5

"Does this engineer proactively identify and address technical debt?"

Question 6

"How thorough is this engineer in considering edge cases and error handling?"

Problem Solving

Question 7

"When faced with ambiguous requirements, how effectively does this engineer clarify and scope the problem?"

Question 8

"Does this engineer consider multiple solutions before committing to an approach?"

Question 9

"How well does this engineer balance shipping speed with code quality?"

Team Contribution

Question 10

"How actively does this engineer share knowledge and help others grow?"

Question 11

"Is this engineer someone others seek out for advice or pairing sessions?"

Question 12

"How does this engineer respond when asked to help with work outside their immediate responsibilities?"

How to Use These Questions

  1. Select 8-12 questions based on what matters most for this engineer's role and growth areas. You don't need to use all of them.
  2. Add a rating scale (1-5 or 1-7) and optional comment field for each question. Quantitative data enables tracking over time.
  3. Include context about the engineer's role and level so reviewers calibrate their expectations appropriately.
  4. Ensure anonymity by aggregating responses. Don't share individual feedback; show averages and themes.
  5. Focus on patterns when reviewing results. Single data points can be noise; consistent feedback across reviewers is signal.

Frequently Asked Questions

How many questions should I include in a 360 review for engineers?

8-12 questions is the sweet spot. Fewer questions get higher completion rates but less depth. More questions provide richer data but cause reviewer fatigue. These 12 questions can be pared down to 8 if you need brevity.

Should I include technical skill questions in a 360 review?

Focus on behaviors and collaboration rather than raw technical ability. Peers can assess how well an engineer explains technical concepts or handles code review feedback. They're less reliable at rating technical depth compared to technical interviews or manager assessment.

Who should review a software engineer?

Include engineers they work with directly (same team), engineers from other teams they collaborate with, their tech lead or manager, and any product managers or designers they partner with. Cross-functional feedback often reveals blind spots.

How do I ensure honest feedback?

Anonymity is crucial. Aggregate responses so no single person's feedback is identifiable. For small teams, consider excluding reviewer count or using ranges. Emphasize that honest feedback helps the person grow.

Should senior and junior engineers use the same questions?

The same questions work for both, but expectations differ. A senior engineer should demonstrate leadership, mentorship, and systems thinking. A junior engineer should show learning velocity and openness to feedback. Interpret responses accordingly.

Related Templates

360 Questions for Product ManagersStrategy, stakeholder management, and prioritization questionsEngineering Collaboration Feedback ExamplesSee what great engineering feedback looks likePersonal 360 Review GuideComplete guide to running your own 360 review

Skip the Setup

Our free tool handles question selection, anonymity, and aggregation automatically.

Start Your Free 360