Joseph TezquvanChief Technology Officer
Portrait of Joseph Tezquvan

Chief Technology Officer · India

JosephTezquvan

Make the software assumption available for challenge

I used to favour sending every potentially useful service alert to the engineer on call.

Open to
  • Board appointments
  • Speaking invitations
Read the profileBegin a conversation

I lead engineering for a regional business lender by examining the assumptions hidden in dates, event order, service credentials and diagnostic work.

I am CTO of Qevruni Supplier Credit in Nagpur, reporting to the CIO. I lead 64 engineering employees through five heads, with fourteen contracted specialists counted separately. Our ₹1,260 crore loan portfolio describes company business, not my credit authority. The engineering remit supports the lender's authorised terms and operating decisions; it does not permit me to rewrite them through a software default.

I began as a software engineer in Kochi after studying computer engineering. The early work taught me that a technically valid output can answer the wrong question if the assumption behind it is left unstated. Business lending made the consequence more immediate. A scheduled action, a status message or a support record can influence what a colleague tells a customer. I want the engineering explanation to survive that journey without acquiring authority the code does not possess.

The cases concern schedule conventions, certificate rollover, diagnostic data, event ordering and the work created by paging rules. They include a release held for business clarification, a more deliberate credential transition and a slower route to authorised diagnostic detail. I also changed my earlier preference for sending every potentially useful alert to the on-call engineer. More signals did not necessarily mean a better response. A technology account should explain what the system assumes, who owns the decision and what evidence supports the result.

A library's calendar choice was not the lending agreement

A rehearsal of 9,600 synthetic schedules found 144 cases where a generic date adjustment differed from the business-approved convention. The release was held for correction and owner review. No live loan terms or customer accounts were changed by that exercise.

A later timestamp did not make an older event authoritative

In a controlled replay of 18,000 synthetic status events, 96 arrived in an order that made wall-clock sorting misleading. We used the authorised transaction version for state progression and retained timestamps for observation, without treating one clock as the business sequence.

The investigation needed a route, not every payload in every log

A review of 96 diagnostic streams found seventeen carrying financial fields beyond their routine support purpose. We narrowed those outputs and retained restricted, authorised investigation. The change reduced unnecessary collection; it did not establish that an earlier external disclosure had occurred.

Current focus

I am making engineering assumptions easier for the CIO and business owners to examine before release. That includes the rule behind a schedule, the authority behind a status transition and the action expected from a page. A better technical account should preserve business ownership and the cost of operating the design, not hide uncertainty behind a passing aggregate measure.

Conversations I welcome

I am interested in a first outside board contribution where software behaviour and business obligations must be understood together. I have no statutory seat. Fictional IICA registration began in March 2026 and the proficiency assessment was passed in September 2026, with no exemption claimed. Twenty-two days is provisional, subject to consent, relationships and the actual appointment demands.

64

Engineering employees through five heads; 14 contracted specialists separate

₹24 crore FY 2026–27 operating expense and ₹9 crore capital

31 years

Engineering to technology leadership

Five continuous appointments beginning July 1995

₹1,260 crore

Company loans, not personal credit authority

276 employees and eighteen service points at March 2026

An engineering default is a choice, even when nobody remembers choosing it. A calendar adjustment can move a date, a wall clock can make an older event look newer, and a diagnostic setting can copy more financial detail than the investigation requires. I want those assumptions examined before the system's convenient behaviour becomes the explanation another team is expected to defend. My responsibility is to make the implementation support the authorised business decision, including the work and cost that a more careful design requires.

Joseph Tezquvan

Chief Technology Officer

Areas of stewardship

Where accountability has been mine.

  1. IBusiness-owned scheduling conventions
  2. IICredential transitions with tested readiness
  3. IIIDiagnostic data appropriate to the support purpose
  4. IVEvent order and actionable engineering response

Selected work

Decisions, and what they changed.

I

Holding a schedule release when a generic date rule changed the intended result

A 2022 rehearsal examined 9,600 synthetic schedules against the lending conventions approved for the selected products.

The full account

II

Completing the certificate transition without making failed validation disappear

A 2023 certificate-renewal programme covered thirty-eight application integrations.

The full account

III

Accepting a slower investigation route to stop copying every financial field

A 2024 review examined ninety-six diagnostic streams from a defined application group.

The full account

In the words of others

Trusted by those who appoint.

Joseph explains the business assumption behind a technical choice before asking us to approve the result. He kept the unresolved schedule cases visible and did not let a library setting acquire lending authority by default.
Arun TezvuniCIO, Qevruni Supplier Credit; fictional colleague
He made the cost of the controlled certificate transition clear and supported the security requirement when a shortcut would have made the release easier. The account retained both the tested result and its limits.
Madhavi QezvoriCEO, Qevruni Supplier Credit; fictional colleague

The journal

Perspective, set down with care.

An invitation

Contact

I am interested in a first outside board contribution where software behaviour and business obligations must be understood together. I have no statutory seat. Fictional IICA registration began in March 2026 and the proficiency assessment was passed in September 2026, with no exemption claimed. Twenty-two days is provisional, subject to consent, relationships and the actual appointment demands.

Open to
  • Board appointments
  • Speaking invitations
Write to Joseph

office@josephtezquvan.example