Developer Documentation Experience Assessment

Thank you for participating in this documentation experience survey. Your responses are voluntary, confidential, and will be reported only in aggregate to help us improve our documentation. There are no right or wrong answers — we want your honest opinions. This survey takes approximately 8 minutes. Please think of one specific documentation session within the last 60 days. Answer all questions about that single session.

Which product, API, or tool were you reading about?

How did you navigate to the relevant documentation? Select all that apply.

• Site search on the docs
• External search engine (e.g., Google)
• Sidebar or table of contents
• On-page find (Ctrl/Cmd+F)
• Direct link or bookmark
• Link from another docs page
• Tutorial or example page
• Other (please specify)

Which best describes the code examples on the page(s) you visited?

• Runnable examples embedded in the page
• Copy-paste examples only
• No examples on the page(s)
• Not sure / don't recall

Did you run any sample code or follow step-by-step instructions during this session?

• Yes, I ran sample code
• Yes, I followed step-by-step instructions (no code)
• No, I only read the documentation

Rank the following aspects of your session from most frustrating (top) to least frustrating (bottom).

1. Finding the right page or topic
2. Dense or unclear writing
3. Insufficient or missing examples
4. Inaccurate or outdated code
5. Missing troubleshooting guidance

Which best describes your current role?

• Software engineer
• Data scientist / ML engineer
• Student
• Product manager
• Technical writer
• Researcher
• Other

Thank you for completing this survey! Your feedback will directly inform improvements to our documentation. Your responses are confidential and will be reported only in aggregate.

What was your main goal during that session?

• Set up or install
• Understand a concept
• Reference API syntax or parameters
• Troubleshoot an error
• Evaluate options or compare approaches
• Check constraints, limits, or pricing
• Other

Approximately how long did it take to find the right page or topic?

• I went directly to it (0 minutes)
• Less than 2 minutes
• 2–5 minutes
• 6–10 minutes
• 11–20 minutes
• More than 20 minutes

The examples were relevant to my use case.

Of the sample code you ran, approximately what proportion worked without modification?

• All of it worked as-is
• Most of it (roughly 75%+)
• About half
• Less than half
• None of it worked as-is

How likely are you to recommend this documentation to a colleague?

How many years of professional development experience do you have?

• 0–1 years
• 2–4 years
• 5–9 years
• 10+ years

Before this session, how familiar were you with this product or tool?

How easy or difficult was it to find the information you needed?

The examples were complete enough to follow without external resources.

Which issues, if any, did you encounter when trying code or following steps? Select all that apply.

• Version mismatch with my environment
• Missing imports or dependencies
• Deprecated API or outdated instructions
• Wrong language variant shown
• Environment or setup steps missing
• Typos or syntax errors
• Permissions or quotas blocked progress
• Unclear or hidden prerequisites
• No issues encountered

If you'd like, please share a link to or name of a specific documentation page relevant to your feedback.

Which programming language(s) did you primarily use in that session? Select up to two.

• Python
• JavaScript / TypeScript
• Java
• C# / .NET
• Go
• Ruby
• C / C++
• Other

The site navigation and structure clearly reflected my task or goal.

Overall, how clear was the writing on the page(s) you used?

Thinking about your overall experience in that session, what is the single most important change that would improve this documentation? Please share any additional thoughts or context.

Where are you primarily located?

• North America
• Latin America
• Europe
• Middle East
• Africa
• East Asia
• South Asia
• Southeast Asia
• Oceania
• Prefer not to say

Search results (if used) were relevant and helpful.