I once accepted a release account built around a thirty-minute performance run. It showed the expected response behaviour, but it did not tell us how the application would behave through a full operating period. In 2019 an eight-hour exercise at a sustained synthetic workload exposed retained application objects. Backend process memory rose from 1.4 to 4.9 gigabytes while the load generator remained stable. I delayed the release and funded the correction. Three later eight-hour repetitions held within the defined 1.4 to 1.8 gigabyte band. That was stronger evidence for the tested conditions, not a promise about every future workload.

My present CTO remit covers fifty-eight engineering employees through four heads, alongside nine separately counted contractors. At Delvrashi Life Assurance in Nashik, I manage ₹14.6 crore annual engineering operating expense and ₹4.8 crore approved change investment. The company’s ₹1,450 crore gross written premium describes its insurance business; it is not my budget. I report to the CIO and explain engineering recommendations when directors invite management evidence. I have no statutory directorship. A 0.4 percent beneficial interest through the employee vehicle is part of the relationship account I would disclose before considering any outside contribution.

Later work tested boundaries that an attractive demonstration can also omit. A new status value behaved correctly inside our service but broke older client expectations in eleven of forty-eight contract scenarios. We corrected nine routes and withheld two that remained unresolved. An encryption-key rotation exercise then showed that successful new writes did not establish continued readability of older encrypted specimens. Eight of twelve failed historical cases were repaired; four remained outside the release. These decisions required cost, delay and professional ownership to be visible together. I would bring that approach to a life-insurer engineering mandate where evidence can change the delivery plan. For a possible board role, I would first complete the preparation and appointment review that management experience does not replace.

Current focus

Engineering evidence that follows sustained use, dependent consumers and authorised encrypted history.

Conversations I welcome

Life-insurer CTO mandates and a first board contribution after preparation, capacity and relationship assessment.