What will happen to software engineers?

Summary

The speaker argues that AI tools and coding agents will increasingly handle routine, low-level development work, shifting software roles toward broader ownership and higher-level problem-solving.

Key ideas

• Roles may converge: Front-end and back-end development, design, QA, and other responsibilities could combine. Rather than producing many more features, developers may use AI to take on more of the product lifecycle.
• Architecture becomes more important: As agents handle implementation details, engineers will need stronger skills in component architecture, design principles, declarative code, state management, and system design. Poor architecture could limit the usefulness of AI-generated code.
• Teams should be organized around products and shared context: The speaker favors focused, cross-functional teams, citing Amazon’s “two-pizza” team rule. Developers, designers, and QA would work closely on one product. Shared understanding of users, goals, and technical constraints could reduce handoffs and improve decisions.
• A new “product engineer” role: This role would involve understanding user problems, exploring and refining design options, assessing feasibility and trade-offs, planning solutions, directing AI agents, and maintaining architectural quality. The speaker predicts it will increasingly replace separate front-end, back-end, and design roles.
• A proposed future model: Rather than conventional teams simply working faster, product engineers would own whole products, while agencies or other specialists handle low-level implementation work. The speaker presents this as a paradigm shift and a prediction, not as a review or tutorial.

Reviews, guides, or tutorials: None are discussed.

Main speaker/source: The video’s presenter, on the Mike Pearson / Software Engineering channel.