﻿<?xml version="1.0" encoding="utf-8"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="01/10/2026" />
        <classifier id="PublicationName" value="HI" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="NumCol" value="0" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="36,55,955,883" />
        <classifier id="Layer" value="Default" />
        <classifier id="numcol" value="8" />
        <classifier id="ArticleStyle" value="" />
        <classifier id="Epaper-Build" value="7.96.0.0" />
        <classifier id="ProcessingDateTime" value="Wed Sep 30 2026 22:26:47 GMT+0530" />
      </identified-content>
      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="HI" date.publication="20261001T000000+5.30" edition.name="VJA" edition.area="VJA" position.section="1MAIN09FVJA" position.sequence="9" ex-ref="1MAIN09FVJA.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
    <body.head>
      <hedline>
        <hl1 id="Headline1" class="1" style="Headline1">
          <lang class="3" style="Headline1" font="Arial" size="15"></lang>
        </hl1>
      </hedline>
    </body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
      <block>
        <media id="1" media-type="image">
          <media-reference id="tn" source-credit="" data-location="1" source="lead12_9_VJA_tn.jpg" Units="pixels" width="50" height="50"></media-reference>
          <media-reference id="tn" source-credit="" data-location="2" source="lead11_9_VJA_tn.jpg" Units="pixels" width="50" height="50"></media-reference>
          <media-reference id="tn" source-credit="" data-location="3" source="lead121_9_VJA_tn.jpg" Units="pixels" width="50" height="50"></media-reference>
        </media>
      </block>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Sharath Sirivolu</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Engineering has always been about solving problems. But the way engineers solve problems is changing. Technology is evolving quickly, and tools such as artificial intelligence are becoming part of everyday engineering work. This does not make engineering skills less important. Instead, it changes what those skills need to include.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">For the next generation of engineers, knowing how to code will remain valuable. But being able to think, question, understand and adapt will be equally important.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Bold" size="9">Coding Is Just the Beginning</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Coding has traditionally been one of the most important skills for engineering students, particularly as technology has become central to almost every industry. However, as AI-powered tools become capable of supporting coding and other technical tasks, engineers will need to look beyond writing code.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The real value lies in understanding what needs to be built, why it is needed and how it can solve a particular problem. Technology should be treated as a tool to achieve an outcome, rather than the outcome itself.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">This shift means students need to focus on building a strong foundation in problem-solving alongside their technical skills.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Bold" size="9">Learning to Ask the Right Questions</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">One of the most important skills an engineer can develop is the ability to ask the right questions. Before looking for a solution, engineers need to understand the problem. What is causing it? Who is affected by it? What information is available? What information is missing? Are there different ways to solve it? This requires curiosity and research. Engineers need to be comfortable gathering information, examining different possibilities and making decisions based on what they learn.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Critical thinking becomes particularly important when there is no single correct answer. Instead of simply following an existing approach, future engineers will need to assess whether that approach is still the right one. Creative thinking and collaborating across borders further enhances this ability to get diverse perspectives, something an AI ecosystem may not be very effective yet.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Bold" size="9">Understanding the World Behind the Technology</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Technical knowledge becomes more valuable when it is combined with an understanding of the field in which it is being applied.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">An engineer working in healthcare, for example, needs to understand the needs of patients, doctors and healthcare systems alongside the technology being developed. Similarly, engineers working in manufacturing, mobility or energy need to understand the challenges and priorities of those sectors. Equally important here is also the understanding of how the technology works. This is almost always rooted in the fundamental engineering principles. For example, an AI system is a composite of foundational principles drawn from mathematics, data, network communications and hardware system areas.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Domain knowledge helps engineers move from building something that works to creating something that is genuinely useful.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Bold" size="9">Solving Problems from the User’s Perspective</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Good engineering is not only about technical performance. It is also about how people experience and use a solution.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Design thinking can help engineers look at problems from the user’s perspective. It encourages them to understand needs, explore different ideas, test solutions and improve them based on feedback.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Giving students opportunities to work on real-world projects can help develop this mindset. Practical experiences teach lessons that cannot always be learned through textbooks or classrooms. Empathizing with a user (putting yourselves in their shoes) and understanding the problem they are trying to solve remains a key human-skill to hone early in the career.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Bold" size="9">Preparing Engineers for a Changing Workplace</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Future engineers will also need to communicate clearly and work with people outside their own areas of expertise. An idea has greater impact when an engineer can explain it to a customer, researcher, business leader or colleague in a way that everyone can understand.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">They will also need to keep learning. The tools used today may change significantly over the course of a career, but the ability to learn, adapt and solve new problems will remain relevant.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The engineer of the future, therefore, will not be defined only by how well they code. They will be defined by how well they understand problems, ask questions, connect technology with real-world needs and turn ideas into meaningful solutions.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Italic" size="9">(The author is Head 
of R&amp;D Centre for Application &amp; 
Research - ZEISS Meditech)</lang>
      </p>
    </body.content>
  </body>
</nitf>