Welcome! This brief survey (≈5–7 minutes) asks about your workloads, latency targets, and trade-offs. Please answer based on your experience over the last 30 days.
Which languages/platforms did you actively use in the last 30 days? (Select all that apply)
- JavaScript/Node.js
- TypeScript
- Python
- Java
- Go
- Rust
- .NET/C
- Ruby
- Kotlin
- Swift
- C/C++
- Other
Which use cases are most relevant to your current work? (Select all that apply)
- User-facing web API
- Interactive UI actions
- Search/query
- Payments/auth/checkout
- Online ML inference
- Batch ML/offline scoring
- Streaming/real-time feeds
- Data pipelines/ETL
- Background jobs
- Build/test/dev tooling
How latency-sensitive are your primary workloads overall?
For user-facing requests, what is an acceptable median (p50) latency?
For user-facing requests, what is an acceptable p95 latency?
How important is reducing tail latency (p95/p99) relative to average latency?
What p95 latency do you typically observe for your primary endpoint? (ms, last 30 days)
What is your default timeout for external calls? (ms)
Attention check: To confirm you are paying attention, please select “I agree.”
How acceptable are occasional latency spikes if the median meets target?
Rank your go-to strategies when latency threatens your SLA/SLO (1 = top priority).
Select the maximum acceptable end-to-end latency for each operation type.
Allocate 100 points across the following to reflect your priorities for a latency-sensitive workload.
Above what latency do interactive actions start to feel slow to users?
What best describes your current role?
- Backend engineer
- Frontend/web engineer
- Full-stack engineer
- Mobile engineer
- ML/AI engineer
- SRE/DevOps
- Data engineer
- Engineering manager
- Other
How many years of professional software development experience do you have?
Approximately how large is your organization?
Where are you primarily located?
Anything else about acceptable latency, tail behavior, or how latency shapes your designs?
Max 600 chars
AI Interview: 2 Follow-up Questions on latency and trade-offs
Thank you for participating! Your responses help us improve developer experiences around latency.