Skip to content

Command Palette

Search for a command to run...

Measure Value

AI developer experience survey

Eight questions that show whether AI coding tools are helping your engineers: time saved, focus, confidence in what they ship, and whether they would miss the tools.

Start from:

1. Run the survey

Create a form in Google Forms or Microsoft Forms with these questions, word for word, on a 1–5 scale from strongly disagree to strongly agree. Keep it anonymous. Run it before the rollout and again a few months after.

  1. AI coding tools save me meaningful time each week.
  2. AI suggestions are usually good enough to use with little rework.
  3. I spend more of my time on hard, interesting problems than before.
  4. Working with AI tools adds mental overhead to my day.(reverse-scored)
  5. I am confident that AI-assisted code I ship is correct and secure.
  6. Reviewing AI-assisted pull requests takes more effort than other pull requests.(reverse-scored)
  7. I would be unhappy if our AI coding tools were taken away.
  8. Our team has clear guidance on when and how to use AI tools.
  9. Roughly how many hours do AI coding tools save you in a typical week? (number)

2. Import the responses

Export the responses as CSV and paste them here. Only the survey question columns are read; everything stays in your browser.

Or enter the averages

Average answer for each question, from 1 to 5, as your form's summary shows it.

Import your survey responses or enter the averages to see scores for each area, where to act first, and the hours people report saving. Or start from an example above.
Assumptions & sources

Scoring: each question's average (1–5) becomes 0–100, where 1 = 0, 3 = 50 and 5 = 100. Questions 4 and 6 are worded so that agreeing is a bad sign, so they are flipped before scoring; this also catches people who agree with everything. Each area is the mean of its two questions, and the index is the mean of the four areas.

Hours saved: self-reported and usually optimistic. Team hours a month = median hours per person per week × team size × 4.33. Treat it as an upper estimate and check it against delivery data before using it in a business case.

Privacy: pasted responses are processed in your browser and never sent anywhere. Only the survey question columns are read. The latest scores are kept in this browser for the AI Value dashboard.

The areas draw on published developer-productivity research such as the SPACE framework (satisfaction, performance, activity, communication, efficiency), adapted for AI coding tools. They are a pulse check, not a validated psychometric instrument.

Questions

How do I survey developers about AI coding tools?

Ask a short, anonymous set of agree/disagree questions covering time saved, output quality, focus, confidence in shipped code, review burden, satisfaction and guidance, plus an estimate of hours saved per week. Run it before the rollout and again a few months after, and compare the results with delivery data from your repositories.

Why are some questions reverse-scored?

Two questions are worded so that agreeing is a bad sign: AI tools adding mental overhead, and AI-assisted pull requests being harder to review. Flipping them before scoring catches people who agree with every statement and gives a more honest result.

Can I use self-reported hours saved in a business case?

Only as an upper estimate. People tend to overstate time saved, so check it against delivery measures such as merged pull requests and time to merge before treating it as a financial saving.

Are survey responses uploaded to this site?

No. Pasted responses are processed in your browser, only the survey question columns are read, and nothing is sent to Learn AI Engineering.