Skip to main content
Developer experience surveys are available to every organization. Managers can view survey results, and admins can launch and manage survey cycles under Reports → Surveys.
DevEx surveys measure tooling, workflows, and team health. Each launch creates a survey cycle; answers roll up by section. Respondents see Quarterly check-in in the product.

Why not a form?

A generic form captures answers. Weave surveys turn them into signal:
  • Pre-built, validated question bank — DORA/SPACE-style questions on tooling friction, build and review wait times, docs, focus time, and psychological safety. No guessing what to ask.
  • Qualitative meets quantitative — survey answers sit next to your actual engineering data in Weave (PR review speed, build times, output), so you can see whether what developers feel matches what’s actually happening.
  • Trends over time — each cycle rolls up by section, so you catch drift early instead of relying on memory of who said what.
  • Scales with you — direct feedback gets noisier as the team grows; surveys keep the signal structured without the manual lift of designing, sending, and aggregating forms by hand.

Access and roles

*When identifiable mode is on for that cycle. Admins and managers find surveys at Reports → Surveys. See User roles for details.

Survey cycles

  • Admins launch manually
  • One open cycle per org at a time
  • Closes on schedule (daily job) or when an admin closes early
  • Default window: 2 weeks (1–12 in org settings or per survey)

Default questions

Four sections, 12 preset questions (Likert, time/percentage/hours buckets, optional freeform). Admins can add custom questions and sections at launch.

Launching (admins)

  1. Reports → Surveys → enable Survey enabled in settings (gear) if first cycle
  2. Click + — three steps: Questions (bank + custom, instruction message with {{first_name}}, {{teams}}, etc.) → Recipients (all members, or filter by role/team/person) → Configuration (title, close date, identifiable mode, draft or send)
Drafts need a title, questions, recipients, and a valid close date before send.
Reminders can be configured in the launch flow but are not emailed yet (detail page shows None scheduled).

Respondents

On send: email invite (from launching admin), home banner, and Notifications entry. Survey at /feedback — intro plus one step per section, auto-saves drafts, ~5 minutes.

Results

  • Results by section — answer distributions (managers and admins)
  • Individual responses — admins only, when identifiable mode is on (statuses: not started, viewed, in progress, completed)

Settings (gear icon)

Identifiable mode removes anonymity but helps follow up with non-responders.
Last modified on October 17, 2026