Beyond code generation: rethinking engineering productivity in the age of AI agents (opens in new tab)

AI coding agents have increased Dropbox’s code production, but they have also exposed bottlenecks in review, testing, release coordination, and operations. The central argument is that engineering productivity must be measured by end-to-end product velocity and customer impact—not code or pull-request volume alone. Dropbox is responding with agent platforms, stronger workflow infrastructure, broader quality metrics, and training that helps engineers adapt to new responsibilities.

From Copilots to Agents

• Copilots assist with explanations, snippets, and questions within existing workflows.
• Agents can take scoped tasks, inspect repositories, edit files, run tests, fix failures, and return changes for human review.
• Engineers remain responsible for intent, architecture, quality, and release decisions.
• Increased parallel work and code output create new pressure on:
  • Code review systems
  • CI and testing infrastructure
  • Validation workflows
  • Release processes
  • Production operations
• More code and pull requests do not necessarily create more customer value.

Nova as Dropbox’s Agent Platform

• Nova runs AI coding agents in controlled environments with relevant codebase context and internal engineering practices.
• Its value comes from the surrounding platform—safe execution, workflow integration, guardrails, and human review—not only from the underlying model.
• Nova generates approximately one in twelve Dropbox pull requests.
• It supports both feature work and maintenance tasks, including:
  • Migrations
  • Flaky-test remediation
  • Bug investigation
  • Dependency updates
  • Other high-effort engineering work
• The intended workflow is structured: define the task, let the agent work within constraints, validate the result, and require human approval before production.

Measuring Product Velocity and Impact

• Pull-request throughput was useful when implementation speed was the main constraint, but it is insufficient as AI increases output.
• Dropbox evaluates whether the broader engineering system can absorb additional work efficiently.
• Its four-stage measurement model tracks:
  • Fuel: Whether engineers use AI tools
  • Adoption: How teams change their workflows
  • Output: Whether AI contributes to production work
  • Impact: Whether products reach customers faster and create greater value
• Quality and trust metrics include review turnaround time, first-run test pass rate, defect ratio, and rework rate.
• Productivity improvements must not come at the expense of reliability or customer trust.

Evolving Engineering Workflows

• Engineers increasingly focus on defining intent, framing problems, reviewing changes, and making architectural and quality decisions.
• Adoption requires more than tools; Dropbox uses hands-on learning, hackathons, bootcamps, workflow examples, and peer-led training.
• Teams should adopt agents at different speeds based on risk, context, and readiness.
• The goal is not to automate every workflow, but to make agentic development safe, useful, measurable, and repeatable.

Broader Lessons

• AI does not remove bottlenecks; it shifts them downstream.
• Organizations must invest in validation, orchestration, governance, workflow integration, and measurement alongside code generation.
• Competitive advantage will come less from access to common foundation models and more from the systems built around them: internal context, safeguards, quality controls, and integrated engineering workflows.

Dropbox’s experience suggests that companies should treat AI agents as a change to the entire software delivery system, not merely as faster coding tools. The strongest results will come from improving the full path from idea to validated production impact.