Learning what the working question requires

The service desk gave me an early education in the distance between an application response and a useful answer. A caller could describe a problem in ordinary working language while our categories demanded a technical label. I learned to ask what the person was trying to do before deciding which system event explained it. That habit has remained useful as my responsibility grew. It also makes my own shortcuts harder to defend when a neat technical rule turns out to answer less than the operating question requires.

I grew up in Bomdila in a Buddhist family and completed a computing degree at the fictional Qeznoli College of Computing in June 1995. Tevqemi Systems employed me in July as a service-desk analyst. The company had forty-two employees and₹7.2 crore revenue for FY ending March 1996. I joined a seven-person support group without reports or delegated spending, reporting to the service-desk manager. My work involved understanding requests, recording what was known and routing questions to the colleagues able to resolve them. Closing a support entry was not the same as establishing that the caller's work could continue.

In April 2002 I became applications lead. Tevqemi employed 105 people and recorded₹22 crore revenue for FY ending March 2003. Twelve colleagues worked through two leads within₹75 lakh annual function expense, and I reported to the head of applications. I gained responsibility for the quality of a working system rather than only its support response. The role taught me to examine defaults that made a process convenient for technology while transferring an unresolved choice to the user. A small rule could become a significant operating assumption when it was repeated often enough.

I joined Veqmethi as service-platform manager in October 2008 and moved to Kolhapur. The enterprise then employed seventy-two people, worked with fifty-two independent partner workshops and recorded₹24 crore revenue for FY ending March 2009. Seventeen IT colleagues worked through two leads with₹1.4 crore annual expense under the head of technology. Roadside-service coordination required a careful boundary between the record and the real assignment. A partner appearing nearby did not establish availability, capability or an appropriate route. Technology had to support qualified operating decisions without presenting a convenient default as authority to undertake the work.

I became head of enterprise IT in January 2015. Veqmethi had 176 employees, 118 partner workshops and₹71 crore revenue for FY ending March 2016. Twenty-two IT colleagues worked through three leads within₹4.2 crore annual expense, and I reported to the CEO. The role connected the service application with telephony, access arrangements and enterprise continuity. It also increased my influence over the assumptions built into common workflows. I supported a distance-based partner ordering that seemed transparent and efficient. The later controlled review showed where its simplicity had concealed a road-access question the calculation had not answered.

The CIO appointment began in February 2021. I now lead twenty-six colleagues through four leads within₹6.8 crore FY 2026–27 operating expense, with₹2.4 crore separately approved capital. Veqmethi employs 284 people, coordinates with 180 independent workshops and records₹138 crore FY 26 service revenue. Mira Qelmoru is CEO and Arun Qazvemi leads operations. Working founders own 47%, a private investor 38% and an employee vehicle 15%;I have no personal or vehicle holding. I do not hold a statutory seat, and the CIO role confers no authority to decide a repair method or a safe live dispatch.

The route-context review examined sixty controlled scenarios. Forty-nine supported the initial ranking and eleven required further work. Eight of those were resolved through the₹47 lakh programme, with three held for operating judgement. A separate attachment review found sixty of two hundred compressed images no longer retained the needed readability. Fifty could be recovered from originals and ten required a fresh request. The₹39 lakh work concerned the usefulness of the evidence, not a technical diagnosis or proof that a service intervention had succeeded.

Partner access required its own correction. Of ninety selected completed-service cases, twenty-two exposed unrelated earlier location history in the assigned partner's view. Twenty were corrected and two held outside that view while review continued, within a₹54 lakh programme. We did not claim universal privacy compliance or infer whether anybody had used the earlier view. In recovery work, a four-hour application restoration left the telephone and working route unproven. A₹62 lakh programme tested twenty-eight controlled calls;twenty-two completed the defined workflow and six required manual fallback. No actual emergency or live-response outcome is represented by those exercises.

I speak Hindi, English and working Marathi. In this fictional career I registered for the IICA databank in February 2026 and passed its proficiency assessment in July. That preparation does not establish suitability for a particular appointment. I have provisionally allowed twenty-eight days and would need employer consent, a relationship review and induction into the enterprise's wider responsibilities. I would contribute a practical concern for what a technology assurance actually covers. My own distance-ranking approval belongs in that account, alongside the colleagues whose operating knowledge made its limits visible.

Open to Board appointments · Advisory roles

Languages / Hindi · English · Marathi — working proficiency