Start from a proven structure, then edit as needed.
Filter: Developer & Engineering
Measures developer satisfaction and outcomes across documentation, code samples, and community events to surface actionable improvement priorities for developer relations and product teams.
View templateMeasures developer awareness of prompt injection threats, captures current security mitigation practices, and identifies gaps in LLM application defense. Designed for engineering teams building or evaluating LLM-integrated features.
View templateMeasures documentation usability, findability, content clarity, and code accuracy based on a developer's recent session. Designed for DX and documentation teams seeking actionable feedback to prioritize improvements.
View templateMeasures developer familiarity, adoption stage, blockers, and rollout priorities for OpenTelemetry across engineering teams to inform instrumentation strategy and resource planning.
View templateMeasures how developers navigate open-source license compliance, including confidence levels, tooling satisfaction, workflow clarity, and key barriers. Designed for engineering teams and developer-tool organizations seeking to improve compliance processes and SBOM adoption.
View templateMeasures developer sentiment toward API deprecation timelines, guidance clarity, and migration burden to inform improvements in API lifecycle communication and support practices.
View templateMeasures developer willingness to pay, pricing model preferences, and fairness perceptions for third-party APIs using Van Westendorp price sensitivity analysis and structured qualitative probes.
View templateCollects structured feedback from incident responders and stakeholders to evaluate response execution, communication quality, and accountability of follow-up actions. Use after any significant incident to identify process improvements.
View templateAssess developer teams' API and SDK migration status, identify top blockers, and surface support needs to plan lower-risk, faster upgrades.
View templateEvaluates how easily developers can find, navigate, and understand technical documentation. Measures discoverability, search quality, information architecture fit, and terminology clarity to prioritize documentation UX improvements.
View templateMeasures developer-perceived latency thresholds, tail-latency tolerance, and performance trade-off priorities by use case. Use it to benchmark acceptable response times, set data-informed SLOs and SLAs, and prioritize performance investments that align with what developers actually care about.
View templateMeasures perceived return on investment from logs, metrics, tracing, and monitoring tools across DevOps and SRE teams, identifying high-impact areas for investment and key barriers to value realization.
View templateMeasures project setup friction, tooling usability, and productivity flow for software developers. Use to identify onboarding bottlenecks, prioritize tool investments, and benchmark developer experience.
View templateMeasures on-call alert burden, interruption impact, recovery effectiveness, and compensation preferences across engineering teams to benchmark workload and identify actionable improvements to reduce burnout.
View templateA developer-focused research instrument for benchmarking distributed tracing sampling adoption, practices, and trade-offs across OpenTelemetry and related observability tooling. Designed for engineering teams seeking to understand how peers approach head-based, tail-based, and adaptive sampling decisions.
View templateMeasures developer productivity, AI coding tool adoption and barriers, code quality practices, and professional growth for engineering teams. Designed for 6–8 minute completion with branching logic for AI tool users vs. non-users.
View templateBenchmarks uptime, incident response, on-call burden, error handling, and SLA priorities across engineering teams. Designed for SREs, DevOps engineers, and software developers managing production systems.
View templateMeasures contribution path clarity, governance transparency, maintainer responsiveness, and improvement priorities for open-source projects. Designed for project maintainers seeking to improve contributor satisfaction and retention.
View templateBenchmarks edge SLO/SLA maturity, failure handling patterns, and release safeguards for DevOps, SRE, and platform engineering teams managing edge workloads.
View templateQuantifies toil sources, automation maturity, and incident-resolution quality for SRE, platform, and DevOps teams over a 30-day period. Use to benchmark reliability operations and prioritize tooling investments.
View templateTell us your research goal and we can help design a template.