Following the decision behind the completed field

The latest upload had become the accepted script in a workflow I had approved. It looked like a sensible way to keep a recording team current. Anjali Qezmethi asked which approved picture cut that script accompanied. The answer was not reliably available in the job record. A timestamp could order arrivals, but it could not establish the creative and customer decision needed for the session. I had made an administrative convenience carry an authority it did not possess. That correction is a useful starting point for explaining my work.

I was born in Berhampur and completed computer science at the fictional Veznari College of Computing in June 1998. Tazqoli Business Systems employed me the following month as an applications analyst. The firm had fifty-four employees and ₹9 crore revenue for FY ending March 1999. I worked in a seven-person group without direct reports or spending authority. Business users helped me understand why an apparently complete record could still require a conversation before somebody acted on it. I learned to follow the purpose of a field rather than judge it only by whether the application accepted its value.

In March 2004 I became application manager. Tazqoli had 118 employees and ₹29 crore revenue for FY ending March 2005. The function's annual allowance was ₹72 lakh; two leads coordinated my twelve-person team. The role brought responsibility for support, changes and the explanation between technical and business teams. I became more attentive to decisions that software seemed to make automatically. A default or sorting rule might be useful, but somebody still needed to decide when it represented the work appropriately. The person who configured it was not always entitled to determine that meaning.

Dazqeni recruited me as business systems manager in June 2010. The language-services enterprise had seventy-two direct employees and ₹18 crore fee revenue for FY ending March 2011. I led fourteen technology colleagues through two leads with ₹1.7 crore annual operating expense. The move placed applications beside practitioners whose decisions concerned language, timing, performance and intended audience. A completed technical transfer could not establish the quality of a translation or the suitability of a caption. I wanted our systems to retain the context those professionals required, without presenting the application as their replacement.

I became head of IT in January 2017. Dazqeni then employed 132 people and recorded ₹43 crore service fees for FY ending March 2018. Twenty technology colleagues worked through three leads within ₹3.2 crore annual expense. The wider remit included working environments, enterprise records and investment choices. I saw how easily a shared field could collapse different services into one attractive status. I also learned that a text record could remain intact in storage while its display required further examination in the actual receiving environment. Those distinctions mattered to the people expected to deliver and defend the work.

The CIO appointment followed in March 2022. Today I lead twenty-five technology staff through three leads, with ₹4.8 crore FY 2026–27 expense and a separate ₹1.9 crore change programme. Dazqeni has 190 direct employees and ₹74 crore FY 26 service fees; external performers and freelance practitioners are outside the employee count. Operating founders hold 61%, a professional vehicle 23% and a capital partner 16%. I have no personal or vehicle holding. Farhan Vezlomi is CEO, while Anjali and qualified language, accessibility, commercial and rights owners retain professional decisions and permissions.

The version review covered 120 jobs. One hundred and four already had an agreed script-to-cut relationship. Sixteen required examination; ten were reconciled and six remained held. The ₹79 lakh programme did not report every mismatch as a translation failure or every held job as lost work. It corrected the basis on which the workflow selected material for a session. The latest-file rule had been my approval, and I wanted the revised account to preserve that responsibility rather than blame colleagues for following the system.

The caption-service review examined eighty films. Sixteen initially met the agreed full-caption review, while sixty-four contained dialogue-only tracks. A ₹44 lakh programme completed suitable captions for forty-eight of those, leaving sixty-four accepted and sixteen pending in the cohort. A separate ₹71 lakh display programme examined seventy-two predefined text-and-environment cases. Fifty-eight initially met the agreed criteria; ten of fourteen failing cases were corrected and four stayed outside the approved delivery route. Neither exercise established universal accessibility, translation quality or correct display on every device.

The management-report correction concerned eighty commissions, each with three language versions. Their combined contracted fee value was ₹11.4 crore. An incorrect join repeated it into ₹34.2 crore in an internal report. The ₹52 lakh correction preserved 240 version records and the actual commission total. Finance retained accounting treatment; we did not describe the report error as extra money earned or its correction as a saving. I work in Odia, English and Hindi. I have no statutory seat and have not registered with the IICA databank. With assessment preparation ahead and twenty-three provisional days, I would consider a board contribution that examines how an enterprise's information supports professional judgement without quietly taking its place.

Open to Board appointments

Languages / Odia · English · Hindi