Engineer – Support & Operations (Developer)

HireSetu's note

The job behind the title

Look at how the listing splits its own duties: build what's assigned, keep the existing project running, fix the issues in it, handle client requests, write documentation. Three of those five are maintenance. In a services company, Support & Operations on a developer requisition means you inherit an application someone else built, with a ticket queue attached to it. New features arrive as change requests against that code, not as a blank project you design.

That is steady, real work, and it suits someone content to know one system deeply. The documentation duty is genuine too. In support, handover notes and runbooks are how the next person fixes what you fixed last month.

If your only picture of software work is building a new app from an empty file, this will feel like a different trade.

Life in a ticket queue

Expect a queue. Tickets come from users or a client contact, you reproduce the issue, trace the cause, fix it or escalate it, and close it with a note. Standups, a sprint board and release windows set the rhythm of the week. Small changes ship often; bigger ones crawl, because they touch something live.

Nagpur is one of HCLTech's delivery centres, so you're likely one team on a wider client account with people in other cities. Ask if the seat runs shifts or carries an on-call rota, since support engagements sometimes come with both and it decides how your evenings look.

The upside is that a running system teaches you faster than a sandbox. You watch what your change does with real users on it, which is a habit worth having early in a career.

Drafted with AI from HCLTech's job posting and checked by Prashanth Jakkula before publishing. See our Editorial Policy.