Suhani Qevzrami · Chief Technology Officer · India

Examine the distance between a demonstration and a commitment

My contribution to a board

I would bring practical questions about the difference between a technical demonstration and the commitment a company makes from it. My experience includes a short-run account I accepted too quickly, consumer contracts that a new status could break and historical encrypted specimens omitted from a new-write demonstration. A board should understand the scope and limits of that evidence, together with the cost and authority required to address what remains. It should not become a group selecting test parameters or approving individual releases. I would help directors ask whether the relevant operating and professional owners are represented in the recommendation and whether unresolved findings survive the journey into the board paper. My engineering background offers a way to make those questions concrete, but does not replace independent assurance or the receiving company’s legal and security expertise. I would need to learn its service model before assuming that an insurer’s experience transfers directly.

Judgement in practice

The duration of the evidence was shorter than the promise

The thirty-minute run had useful results, but the eight-hour exercise revealed application memory growth under a sustained synthetic workload. I would ask directors what operating period the release evidence describes and whether the measurements distinguish the service from the test equipment. Three later repetitions supported a narrower, better-founded recommendation; they did not establish behaviour under every future condition. The board should understand that limitation and the management response without deciding which objects an engineer must release or how much memory to allocate. My own earlier acceptance matters because it shows how a familiar success measure can pass through leadership without its scope being examined. A useful oversight question asks what the demonstration omitted before treating it as evidence for the wider commitment.

A current success did not establish historical readability

The key-rotation exercise read sixty of seventy-two synthetic specimens through the proposed route. Eight of the twelve failures were corrected, leaving four unresolved. I would ask whether the board’s account separates successful new encryption from continued authorised access to older information. The remaining dependency needs a named management owner and the relevant security and retention assessment. Directors should not prescribe indefinite key storage or infer a production loss from constructed specimens. They should understand why the release recommendation excludes the affected cases and which authority can approve the next step. The lesson is to keep the earlier information obligation visible while a new technical capability is introduced, with the boundaries of the test and the professional responsibilities stated together.

My first year on a board

My induction would begin with the company’s process for turning engineering evidence into a business commitment. Through arrangements agreed with the chair, I would examine one significant release proposal and one continuing dependency, meeting the responsible executives without creating a parallel reporting line. I would ask how quality findings, operating needs and financial consequences are brought together, and how unresolved disagreement reaches directors. Twenty-four annual days must cover preparation, meetings, induction and exceptional demands rather than only attendance. I would seek feedback on whether my contribution makes the decision clearer or draws the board into technical management. A useful first-year outcome might be a more precise account of what a major technology promise covers and what it leaves open. That should respond to an actual company priority, not become a personal campaign to reproduce my insurer’s engineering process elsewhere.

Conflicts and their management

My current employment gives me access to platform designs, supplier negotiations, service plans and protected information. I also have a 0.4 percent beneficial interest through the employee vehicle, within an ownership structure that includes founder and corporate investors. Those relationships belong in an appointment assessment before confidential material is exchanged. I would disclose relevant connections with insurers, software suppliers, implementation partners and investors, and ask the receiving company to assess eligibility and committee suitability. A commercial party might see my technical role as a route into procurement; an outside appointment must not provide that access. Recusal can address a defined matter, but repeated exclusion from the technology agenda could remove the reason for appointing me. Employer consent and the practical calendar also need resolution. I would refuse an arrangement that expects protected design knowledge, informal product endorsement or a personal certification of readiness outside the company’s authorised evidence and assurance process.

My independence statement

My insurer employment and 0.4% beneficial interest through its employee vehicle require disclosure and assessment. I do not claim independence from Delvrashi or automatic eligibility for another company’s board.

Committee contribution

Chair and member readiness
Capacity	Committees
Ready to join	Technology and operational-risk discussions · Service-dependency and information-lifecycle oversight

Capacity and preferences

Time available: 24 days per year
Current directorships: 0
Sectors: Insurance and long-lived digital services · Enterprises with dependent applications and retained information
Company type: A company with accountable engineering management and a chair who examines the limits of technical evidence
Company stage: Changing a platform or strengthening how release commitments are scrutinised

The seat I am pursuing

I would consider one non-executive contribution where experienced directors want to examine the evidence behind long-lived technology commitments. Preparation and company-specific assessment must come first because I have no statutory board experience to offer. My initial contribution could fit technology or operational-risk discussions under established leadership, with no claim to chair a statutory committee. I would want clarity about the skills already represented and why an engineering perspective is needed. The company should retain capable management and appropriate assurance rather than use a director as a substitute for either. I would avoid a role framed around supplier introductions, access to insurer partners or informal release approval. The useful seat would let me help colleagues ask what a successful demonstration establishes, which dependencies remain and how management carries those obligations into the next decision.

Board and committee exposure

Presented to the Board or a committee

Delvrashi Life Assurance

Invited engineering investment and release-risk discussions

April 2022–present

Explains CTO recommendations and unresolved technical findings with the CIO; no statutory appointment or voting role.

Reported to a committee

Delvrashi Life Assurance

Engineering evidence through the technology leadership team

April 2016–March 2022

Prepared management accounts of test scope, correction expense and release limitations; committee exposure only.

Governance learning and readiness

IICA Independent Directors’ Databank: Not yet registered

Independent-role preparation and registration where applicable are unfinished. No statutory service, proficiency pass or exemption is asserted.

Preparing to distinguish collective technology oversight from implementation and assurance responsibilities
Learning to assess appointment requirements, financial interests and supplier relationships before accepting confidential board material