Uploaded July 2026 | Updated September 2026, 3 weeks ago
Most of the coding agent market quietly optimizes for token usage; Cognition's deployed engineering team measures the opposite, the outcomes a customer can actually see, and reports something like an 82% reduction on the work they targeted. Jia Wu's argument is that you measure before Devin ever lands, then again once it is fully activated inside the customer, so the value is a real delta and not a vanity number. The way that value shows up is not linear: one team using the agent is a step function, a whole enterprise using it is parabolic, because the products Cognition builds and the customer's backlog start to overlap.
That changes what a deployed engineer is. As the pure engineering part trends toward zero, the job leans on business and people skills: understand the customer's real problem space, find the highest leverage place to point the agent, and communicate it back into the roadmap, since customers are the lifeblood. Each deployment is meant to derisk and improve the next, because the challenges recur in similar shapes across companies. The value underneath it all is blunt: correctness and customer success at all costs, ship the hard thing and leave nothing on the table.
Speaker info:
- linkedin.com/in/jia-rong-wu
Timestamps:
0:00 - Introduction: deployed engineering at Cognition
2:05 - Step function to parabolic productivity
3:35 - Where products meet the customer's problems
5:16 - Pointing agents at the highest leverage work
7:07 - How deployment challenges recur
8:34 - What a deployed engineer actually is
10:25 - Measuring outcomes, not token usage
12:56 - The 82% result, measured before and after
14:38 - Developers plus Devin, autonomously
15:53 - Core values: correctness and customer success
Most of the coding agent market quietly optimizes for token usage; Cognition's deployed engineering team measures the opposite, the outcomes a customer can actually see, and reports something like an 82% reduction on the work they targeted. Jia Wu's argument is that you measure before Devin ever lands, then again once it is fully activated inside the customer, so the value is a real delta and not a vanity number. The way that value shows up is not linear: one team using the agent is a step function, a whole enterprise using it is parabolic, because the products Cognition builds and the customer's backlog start to overlap.
That changes what a deployed engineer is. As the pure engineering part trends toward zero, the job leans on business and people skills: understand the customer's real problem space, find the highest leverage place to point the agent, and communicate it back into the roadmap, since customers are the lifeblood. Each deployment is meant to derisk and improve the next, because the challenges recur in similar shapes across companies. The value underneath it all is blunt: correctness and customer success at all costs, ship the hard thing and leave nothing on the table.
Speaker info:
- linkedin.com/in/jia-rong-wu
Timestamps:
0:00 - Introduction: deployed engineering at Cognition
2:05 - Step function to parabolic productivity
3:35 - Where products meet the customer's problems
5:16 - Pointing agents at the highest leverage work
7:07 - How deployment challenges recur
8:34 - What a deployed engineer actually is
10:25 - Measuring outcomes, not token usage
12:56 - The 82% result, measured before and after
14:38 - Developers plus Devin, autonomously
15:53 - Core values: correctness and customer success
