Ask about the work developers experience
Use focused questions on concentration, collaboration, tools, and feedback. Start from a template or curate a question set for your team.
DevEx Survey
Understand the developer experience behind delivery
Run focused surveys, follow participation, and compare topic scores with benchmarks. Bring developer feedback into the same review as your engineering signals.
Developer Experience Dashboard
All teams · Last 90 daysSurvey overview
Company score, participation, and topic results
63/ 100
General Company Score
HealthyAcross 4 topics- Active surveys
- 2 Open for answers
- Responses
- 157 Of 200 invited
- Completion
- 78.5% Of invited people
- Engagement trend
- +12% vs previous period
Completion
78.5% completed
21.5% not completedTopics vs benchmark
1 of 4 meeting
3 topics below benchmarkAnswer sentiment
38% positive
27% neutral · 35% negativeTrend by topic
Feedback Loop scoreExplore the trend
Topic deep dive
Feedback Loop
Inspect review turnaround and the feedback that helps developers keep work moving. Agree on one follow-up with the team.
- Topic score
- 2.8 / 5
- Benchmark gap
- -1.1
Explore participation, switch to topic results, and select a topic to inspect its trend and benchmark gap.
From signals to decisions
Bring developer feedback into the engineering review
Start with the experience people report, then inspect the patterns and engineering context around it.
Follow participation and topic movement
Review completion alongside topic scores, benchmarks, and trends. Check whose teams are represented before interpreting the results.
Investigate the feedback with engineering context
Follow topics into question scores, related metrics, and AI-assisted diagnosis. Discuss the next action with the team.
What to look at
Build the survey around the question you need to answer
Choose a focused scope, make response visibility clear, and plan how the team will review the result.
- Templates and a reusable question bank
- Team scope and survey period
- Confidential or Identified response mode
- Topic benchmarks and question-level results
- Choose the question set
- Start from an Oobeya template, a custom template, or the question bank. Select the topics and questions that fit the review.
- Define scope and confidentiality
- Select the participating teams, survey period, and confidentiality mode. Make the response visibility clear before publishing.
- Review the topic and follow-up
- Follow completion, scores, benchmarks, and question-level results. Use topic diagnosis and related metrics to guide an improvement discussion.
Survey templates
Start with a focused question set
Use Oobeya templates for recurring experience and maturity reviews, or build a custom set from the question bank.
Developer Experience Core
MonthlyRecurring feedback on the day-to-day developer experience.
18 questionsWellbeing Pulse
WeeklyA short pulse for following wellbeing over time.
5 questions · Confidential onlyCode Review Effectiveness
MonthlyFocused feedback on the responsiveness and usefulness of code review.
15 questionsEngineering Team Health
MonthlyFeedback on the conditions that help a team work together.
18 questionsAI Engineering Maturity
QuarterlyAssess the maturity of AI-assisted engineering practices.
18 questionsSDLC Maturity
QuarterlyReview engineering practices across the development lifecycle.
18 questionsQuestion-level context
Follow the feedback into the work it describes
Likert questions and open text responses help teams describe the experience. Related metrics add context for investigating a topic.
Explore review and delivery symptomsResponse visibility
Make confidentiality clear before the survey starts
Choose the appropriate response mode and explain it to participants. Results are available to authorized roles.
- Confidential
- Results do not show who gave which answer. Wellbeing Pulse uses this mode.
- Identified
- Authorized roles can see the respondent associated with each answer.
From signals to decisions
Review the experience alongside engineering signals
Use feedback and the related workflow context to choose a follow-up and revisit the result.
Review feedback and delivery symptoms
Follow feedback-loop concerns into unreviewed pull requests, review delays, and the workflow signals behind them.
Contribution and collaboration
Use work distribution and activity patterns to add context to the team’s experience and responsibilities.
Delivery and quality outcomes
Revisit production delivery and quality after a workflow change to understand the result alongside the feedback.
What is Oobeya DevEx Survey?
DevEx Survey collects structured developer feedback and brings participation, topic scores, benchmarks, trends, and question-level results into a shared review. Use it to investigate the developer experience alongside engineering context.
Can we use templates or select our own questions?
Yes. Start with an Oobeya template, a custom template, or select questions from the question bank. Oobeya templates are fixed; custom question sets let teams tailor their survey scope.
Which question types are available?
The product supports Likert 1–5 questions and open text responses. Question configuration also includes whether an answer is required and whether comments are allowed.
What is the difference between Confidential and Identified?
In Confidential mode, results are visible to authorized roles without showing who gave which answer. In Identified mode, authorized roles can see the respondent associated with each answer. The Wellbeing Pulse template is confidential only.
Can results be reviewed by team and topic?
Yes. The dashboard supports team and period scope, participation and completion measures, topic scores, benchmarks, sentiment summaries, and topic-level analysis.
How does feedback relate to engineering metrics?
Survey questions can include a related metric, such as pull request cycle time, lead time, or delivery context. Use the question-level result and the related engineering signal to guide an investigation.
What does AI-assisted topic diagnosis provide?
The topic analysis view includes an AI-assisted diagnosis and suggested action areas. Review those suggestions with the question results, benchmark context, and the team’s own explanation.
Can a published survey be edited?
The product locks the published survey content. Its closing date can be extended, so confirm the question set and confidentiality mode before publishing.
See Oobeya in practice
Bring your developer experience questions into focus
Walk through survey templates, confidentiality, participation, and topic analysis with your engineering teams in mind.