Raghav TzeqenriChief Technology Officer
Portrait of Raghav Tzeqenri

Chief Technology Officer · India

RaghavTzeqenri

Leave the next engineer an answer they can verify

The deployment worked, and I accepted that as evidence that we controlled the release.

Open to
  • Board appointments
  • Advisory roles
  • Speaking invitations

Leave the next engineer an answer they can verify

I am CTO of Qezvethi General Insurance, a fictional insurer based in Mangaluru. Sixty-four engineering employees work through five heads, with twelve contractors separately counted. I report to CIO Zoya Veqzenmi and hold ₹18.4 crore annual operating authority plus ₹6.2 crore approved change investment. The company's ₹1,520 crore gross written premium for FY ending March 2026 describes insurance volume, not my budget or company revenue. Engineering implements authorised decisions; it does not acquire underwriting authority by writing the calculation.

My thirty-six years have made me wary of a result that works only while its original author remains in the room. An application may deploy while its build cannot be reconstructed. A property area may look precise while its unit is absent. A component may be available to download while permission for our intended use is unresolved. These are different questions, but each asks us to preserve something a convenient implementation might leave unstated.

In 2020 I accepted a successful deployment as sufficient evidence that we controlled the release. A later review of eighty-three deployed artefacts found sixty-six reproducible and seventeen that could not be reconstructed from the retained materials. Historical build instructions and a vendor plugin were missing from the account. We spent ₹91 lakh reconstructing twelve and retiring five only after approved replacements, while moving two features four weeks later. I had endorsed the earlier assurance, and the correction belongs in my professional story.

Fast interactive work had a visible batch cost

Twenty-four controlled paired runs showed quotation-response latency improving under a revised resource allocation while the analytics batch took longer. We retained both results and the additional annual expense, rather than claim a free performance improvement.

A number without its unit was still unresolved

Twenty-four of 360 synthetic property records lacked an explicit area unit. The original path silently assumed square metres. A revised account resolved 350 records and left ten for clarification, without guessing their meaning.

An available library still required a permission account

Eleven of ninety-seven software libraries had incomplete licence evidence. Qualified review subsequently approved seven for the intended use; four were replaced. The initial finding was an evidence gap, not a declaration of infringement.

Current focus

Engineering decisions that remain intelligible beyond their launch: reproducible builds, explicit resource priorities, measurement meaning, component permissions and causal event order. The useful result includes the cost and unresolved work that a polished release summary can omit.

Conversations I welcome

A first non-executive contribution after employer consent and company-specific assessment. I have no statutory seat or personal company holding. Databank registration was completed in April 2026 in this fictional account; assessment remains outstanding and nineteen annual days are provisional.

64

Engineering employees

Five heads; twelve contractors outside this employee count

₹18.4 cr

Annual operating authority

₹6.2 crore change investment separately approved; finance owns classification

36 years

Engineering career

Entered July 1990; CTO appointment January 2021

The software we release carries assumptions about how it was made, what its numbers mean and who will maintain it. I want those assumptions recoverable by the next person who must rely on the service, including when the original engineer is no longer available to explain them.

Raghav Tzeqenri

Chief Technology Officer

Areas of stewardship

Where accountability has been mine.

  1. IReproducible software construction
  2. IIExplicit workload priorities
  3. IIIMeasurement and event semantics
  4. IVSoftware-component permission evidence

Selected work

Decisions, and what they changed.

I

The release worked, but seventeen builds could not be reconstructed

In 2020 I endorsed a release-assurance account because the software had deployed and its operating checks passed.

The full account

II

A faster quotation path made the analytics window longer

In 2022 interactive quotation work and a scheduled analytics batch competed for shared processing capacity.

The full account

III

The missing area unit could not be supplied by a convenient default

A 2023 review used 360 synthetic property records to test an integration that passed area values into an insurance workflow.

The full account

In the words of others

Trusted by those who appoint.

Raghav made the slower analytics window visible beside the faster quotation path. He asked us to accept the whole priority decision, not just its most attractive measure.
Zoya VeqzenmiCIO, Qezvethi General Insurance; fictional colleague
He corrected an assurance he had given about our builds and explained the features that would wait while the missing construction account was repaired.
Madhav ZeqvehtiCEO, Qezvethi General Insurance; fictional colleague

The journal

Perspective, set down with care.

An invitation

Contact

A first non-executive contribution after employer consent and company-specific assessment. I have no statutory seat or personal company holding. Databank registration was completed in April 2026 in this fictional account; assessment remains outstanding and nineteen annual days are provisional.

Open to
  • Board appointments
  • Advisory roles
  • Speaking invitations

office@raghavtzeqenri.example