Skip to website

Leadership & perspective

Chief Technology Officer · India

2026-05-21 edition

Raghav Tzeqenri

I build insurance technology whose origin, assumptions and continuing obligations can be explained after the release team has moved on.

Raghav Tzeqenri · Chief Technology Officer · India

Ask what the enterprise must still be able to explain

My contribution to a board

I would help a board understand what a technology result leaves behind. A release may work while its construction account is incomplete. A faster interactive process may displace an analytical window. A populated numerical field may carry an unsupported unit. These questions matter because management may be asking the enterprise to rely on a stronger capability than the evidence demonstrates. My contribution would be to make the obligation and its owner visible enough for a collective decision.

I would bring experience of correcting my own endorsement. Seventeen of eighty-three artefacts could not be reconstructed after I had accepted deployment success as sufficient assurance. Twelve were rebuilt and five retired after approved replacement, with cost and feature delays retained in the account. A director should be willing to recognise that a technically valid result may still answer the wrong question. I would aim to improve the interpretation of management evidence, not to transfer architecture decisions from executives to the board.

Judgement in practice

01

Construction evidence survived the correction to my assurance

The review found sixty-six reproducible artefacts and seventeen without a sufficient construction path. ₹91 lakh funded twelve reconstructions and five retirements after approved replacements; two features moved four weeks later. The board question is whether the enterprise can substantiate the capability it believes it owns, including the dependencies required when the original team is unavailable. The finding did not prove malicious software or a production failure, and reproducibility did not certify security. I would help directors examine the claim and alternatives without asking them to approve build commands or individual technical components.

02

The priority decision included the work made slower

Twenty-four controlled paired runs improved quotation-response p95 from 4.8 to 1.6 seconds while the analytics batch moved from ten to 13.5 hours. ₹64 lakh implementation and ₹18 lakh annual expense supported that allocation. A board should be able to see which operating need was favoured, who accepted the consequence and what conditions bound the benchmark. The result was not a universal service promise or improved actuarial accuracy. Oversight would ask whether management had agreed a useful trade-off across receiving teams, rather than reward the fastest-looking measure in isolation.

03

A missing record did not supply a legal conclusion

Eleven of ninety-seven libraries had incomplete licence evidence. Qualified review approved seven for the intended use and four were replaced, at ₹42 lakh cost over six weeks. The initial gap was neither permission nor proof of infringement. Directors could ask whether management can recover the facts, obtain appropriate interpretation and fund the technical response. I would keep the evidence state distinct from the resulting judgement and avoid turning a board discussion into an unsupported allegation about a supplier. Changed versions or uses would still require the responsible owners to reconsider the account.

My first year on a board

I would spend the first part of an appointment learning which services the enterprise relies on and how management describes their continuing obligations. I would want to understand the relationship between technology, operating teams and professional decision owners before bringing a familiar engineering question into discussion. Enquiries would follow the chair's arrangements and relevant committee remit, with the executive team retaining responsibility for implementation.

My learning would include the assumptions behind reported progress: what was tested, what was inferred and which cost or unresolved condition remains outside the headline. I would listen for cases where an apparently awkward technical limitation is protecting an important business distinction. Nineteen provisional days would need review against induction, reading, travel and exceptional demands. If the role required capacity I could not provide alongside employment, I would not accept it on the hope that preparation could be compressed. The first year should establish a useful contribution to collective judgement and a clear boundary from executive delivery, rather than a reputation for supplying immediate technical answers.

Conflicts and their management

My continuing employment at Qezvethi would be disclosed before any proposed appointment progressed. Relationships with technology providers, insurance participants and professional advisers may matter even though I have no personal shareholding or current statutory seat. Qualified review must consider the particular enterprise and responsibilities. I would not equate the absence of one obvious financial interest with a settled independence conclusion.

I would keep source code, internal build records, licence advice and restricted operating material within the permissions of the organisation that entrusted them to me. A prospective board does not acquire access to those materials because my experience is relevant to its question. Where interests intersect, participation and access should follow the chair's process and appropriate advice. An unmanageable conflict would be a reason to decline the role. The examples on this site are invented to illustrate judgement; a real appointment requires verified disclosures and a practical method for recognising when relationships or responsibilities change.

My independence statement

I make no claim of legal independence. My employment and commercial relationships require qualified assessment for any proposed enterprise, despite having no personal holding or statutory seat.

Governance learning and readiness

IICA Independent Directors’ Databank: Registered

Registered in April 2026 in this fictional account; proficiency assessment remains outstanding. Preparation does not itself establish eligibility, independence or suitability for an appointment.

  • Practise collective oversight of technology obligations without taking delivery authority
  • Complete outstanding preparation and seek qualified company-specific eligibility review
  • Learn the receiving enterprise's professional decisions before interpreting its platform evidence

Committee contribution

Chair and member readiness
CapacityCommittees
Ready to joinTechnology or risk oversight after a specific suitability review

Board and committee exposure

Presented to the Board or a committee

Qezvethi General Insurance

Board technology and enterprise-risk discussions

2021–2026

Presented engineering choices, unresolved dependencies and resource trade-offs with the CIO. No statutory seat or authority over insurance professional decisions is claimed.

Capacity and preferences

Time available
19 days per year
Current directorships
0
Sectors
General insurance · Enterprise software and information-dependent services
Company type
An institution seeking clearer accounts of the obligations inside its technology estate
Company stage
Established operations examining shared platforms and continuing engineering commitments

The seat I am pursuing

I seek a first non-executive contribution in an enterprise that wants a clearer understanding of the obligations inside shared technology. The useful setting would have management willing to explain trade-offs, uncertain inputs and dependency decisions as part of its business account. I would be less useful in a role designed primarily to obtain an outside approver for day-to-day engineering choices.

Databank registration was completed in April 2026 in this fictional account, while proficiency assessment remains outstanding. Employer permission and qualified review of eligibility, conflicts and suitability would precede acceptance. I would want the chair to understand the limits of my available time and the learning required for a new sector. My thirty-six-year engineering history supplies examples and questions, not automatic knowledge of another enterprise. The contribution I hope to make is to help directors recognise both the value of technical progress and the commitments it leaves for management, including when the evidence requires me to revise a view I initially held.