AI shifts engineers from coders to systems architects, Inc42 argues

Inc42 has framed a growing tension in software engineering: as AI coding assistants handle more of the execution work, the discipline’s value may be shifting toward systems thinking. The argument, published this week, echoes a pivot some suggest is already underway in enterprise engineering teams. Rather than writing code, engineers could be spending more time designing architectures, reviewing AI-generated outputs, and ensuring those outputs integrate with existing systems.

When we covered Elastic’s Ravindra Ramnani in late September, he described a similar possibility: enterprises might not be bottlenecked by model size or compute, but by what he called “context engineering.” The challenge could be not generating code, but ensuring AI systems understand the nuances of legacy systems, business logic, and edge cases. Zeit AI’s €5 million seed round, reported earlier this month, appears to target this gap, aiming to automate data engineering workflows that might require deep systems knowledge rather than brute-force coding.

The shift may not be uniform, though. Cognition’s $2 billion raise at a $48 billion valuation, disclosed just days before Zeit’s funding, reflects a different bet: that AI might still dominate the coding itself, not just the adjacent workflows. The startup’s revenue, nearing $900 million, could indicate demand for AI that writes, not just assists. But even Cognition’s trajectory might depend on whether engineers transition from being the primary authors of code to the architects of AI-driven systems. The difference between these two approaches—AI as a coding tool versus AI as a systems enabler—could influence how startups position themselves in the near term.

For engineering education, the discussion raises questions. If Inc42’s argument gains traction, universities and bootcamps might produce engineers who are fluent in syntax but less prepared to design resilient, scalable systems. The mismatch between education and enterprise needs has been discussed before, and AI could amplify it. Some startups, like Zeit AI, seem to be betting on tools that address this divide, while incumbents like Elastic might lean toward consulting or tailored solutions. Neither direction is certain, but the divergence hints at an industry still searching for clarity.

How this transition plays out remains unclear. Systems thinking has long been part of elite engineering teams, but AI could change how—or how widely—it’s applied. Smaller startups might struggle if they can’t adapt, while larger enterprises could explore specialized roles. The pace of change could outstrip curricula or job descriptions, leaving the next wave of funding rounds to show which startups are positioning themselves as part of this shift, and which are treating it as an open question.

Sources: inc42.com