The Case for a Core Branch When Everyone Is Choosing Computing

For roughly fifteen years the flow of engineering students has moved towards computing. The reasons are understandable. The consequence is less discussed: fewer students are entering the branches that build and maintain physical infrastructure, at a time when India is building a great deal of it.

What core engineers actually do

A civil engineer works on things that must not fail: structures, foundations, water systems, roads. A mechanical engineer works on things that must move reliably: machines, thermal systems, manufacturing processes. An electrical engineer works on the system that everything else depends on: generation, transmission, protection, drives and increasingly renewable integration and electric mobility.

These are not legacy jobs. The grid is being rebuilt around renewables and storage. Transport is being electrified. Construction is absorbing digital methods such as building information modelling. The domains are old; the current work in them is not.

The competitive argument

This is the uncomfortable part, and it is worth stating plainly. When a branch attracts fewer applicants, the students who do choose it face less competition for the roles that branch leads to. That is not a reason on its own to choose a branch. It is a reason to discount the assumption that the crowded branch is automatically the safer one.

Where core and computing meet

The most useful position is often the boundary. A mechanical engineer who can write code to process test data, a civil engineer fluent in BIM, an electrical engineer who understands embedded control. Those people are scarce in a way that neither pure discipline is.

This is also why the AI question matters less in core branches than students assume. A model can generate a calculation. It cannot take professional responsibility for a structure.