Reader · no content
No body text on file.
Open the original to read the full piece.
On 2026-04-27 Andrew Ng wrote that AI-native teams use coding agents to build…
Brief
AI-native software engineering teams, Andrew Ng argues (Apr 27, 2026), are reorganizing around dramatically faster code production enabled by coding agents—he cites speedups on the order of 10x–100x—which moves the bottleneck from implementation to deciding and coordinating work. As a result, engineer:product-manager ratios are falling (from ~8:1 toward 1:1), and the highest-velocity groups are small, often 2–10 people, where engineers take on product decisions and PMs pick up engineering tasks. Rapid delivery exposes downstream constraints in design, marketing, and legal—Ng gives examples of features shipped in a day while marketing scrambled and legal needing a week—so teams favor generalists and co-location to minimize communication friction. He concludes that individuals who learn cross-functional skills (engineers learning PM; PMs learning to build) will excel in this era.
Why it matters
On 2026-04-27 Andrew Ng wrote that AI-native teams use coding agents to build products much faster—he estimates development speedups of roughly 10x to 100x—causing non-coding parts of delivery to become the new bottlenecks.
Key details
- Engineer:PM ratios are dropping; Ng cites conventional ratios like 8:1 shrinking toward 1:1, and says the fastest teams have engineers who make product decisions (and some PMs who can code) so a single person can both decide what to build and implement it.
- Ng gives concrete bottleneck examples: teams have shipped features in a day while marketing scrambled to communicate them, and legal reviews that take a week become the rate-limiter when coding is done in a day.
- AI-enabled teams of ~2–10 people (especially co-located two-person teams) favor generalists who cross engineering, product, design, marketing, and legal; Ng urges engineers to learn product skills and PMs to learn to build.