In this LinkedIn post, Rhushik Matroja argues that traditional proficiency with computer-aided design software is no longer the core competency that defines an engineer’s value. For decades, being adept at menus, commands, and geometric modeling was treated as a badge of honor, but Matroja insists this focus has obscured the real purpose of engineering: understanding physics, systems, trade-offs, and the reasoning behind design decisions. CAD proficiency, he says, is fundamentally data entry that translates intent into digital form, not engineering itself. That role is increasingly susceptible to automation as artificial intelligence grows more capable of generating geometry and exploring design alternatives. AI can run optimization loops, evaluate multi-objective tradeoffs, and synthesize thousands of potential configurations far faster than a human operator ever could. Matroja is not dismissing the craft of experienced CAD users, but he stresses that expertise in execution does not equate to engineering judgment.
The evolution of engineering work, he says, demands skills that go beyond clicking on features. Modern design challenges involve interacting constraints across manufacturability, certification, supply chains, cost, lifecycle impacts, and physics phenomena such as stress and heat transfer. These are not sequential concerns but interconnected domains that must be understood simultaneously. Engineers who grasp why an optimization has converged on a particular solution, recognize physically implausible outputs, or can interrogate and steer computational tools will have enduring value. Matroja proposes a shift from operator to conductor: the engineer as design orchestrator. Instead of rebuilding analysis pipelines from scratch, orchestrators define high-level intent, deploy appropriate algorithms, synthesize multi-disciplinary results, and apply judgment in final decisions. In this new paradigm, mastering the underlying science, systems thinking, and algorithmic literacy outweighs proficiency with software interfaces. The conclusion is clear: CAD skill alone no longer distinguishes engineers; understanding does.