Safiya ZevqenriChief Technology Officer
Portrait of Safiya Zevqenri

Chief Technology Officer · India

SafiyaZevqenri

Keep the meaning intact when the customer changes direction

The screen said centimetres. The receiving component still assumed metres.

Open to
  • Board appointments
  • Advisory roles
  • Speaking invitations

Keep the meaning intact when the customer changes direction

I lead customer-product engineering at Vedqezmi Window Furnishings in Vadodara. The fictional retailer combines twenty-eight studios with online curtain and wallcovering configuration. Seventy-two engineering employees work through six leaders, with twelve contractor positions counted separately. My authority covers ₹13.8 crore annual engineering expense and ₹5.2 crore separately approved development; company revenue and the CIO's enterprise remit are different responsibilities.

My twenty-three years began in commerce software. A configuration journey has taught me to examine more than its successful forward path. People change a fabric, undo a choice, enter a dimension in a different unit or use a keyboard instead of dragging a visual control. Software also changes version while saved designs remain. Engineering needs an account of the meaning and state that survive those transitions.

In 2021 I accepted an interface change to centimetres while a receiving component still interpreted the bare number as metres. A 2.35-metre width became 235 centimetres, then was read as 235 metres. Eighteen of 120 synthetic quotations exposed the mismatch. We held release and allocated ₹41 lakh to the unit contract and its tests. No live incorrect order is claimed, but my approval had preceded a complete understanding of the receiving behaviour.

Undoing one choice left another choice invalid

Forty-seven of 360 scripted configuration sequences retained an incompatible lining after the fabric changed. We held launch and funded ₹68 lakh of state-transition validation. Individually valid choices did not establish a valid combination, and engineering could not replace the technical-design owner's feasibility decisions.

The action needed another usable route

Nine of twenty-four adult participants could not complete width setup when it required dragging. After a ₹52 lakh keyboard and labelled-input programme, three of the same twenty-four could not complete the task. Practice and order effects remain possible; this is neither controlled causality nor complete accessibility certification.

Returning to old code did not return saved data to its old form

Seventeen of forty-eight synthetic saved designs could not be read by the old version after a data-structure change. A twelve-week ₹1.2 crore compatibility and recovery programme preceded release. The rehearsal does not claim an actual customer data loss or completed universal recovery.

Current focus

Customer-product engineering that preserves units, valid state and usable interactions while making rollback and retry behaviour part of the release account. I want each technical assurance to retain the evidence that supports it and the questions still open.

Conversations I welcome

A first outside non-executive contribution after company-specific learning, relationship review and employer agreement. I hold 1.2% within employee ownership and no statutory seat. Fictional IICA registration and proficiency assessment are complete; twenty-four provisional days remain subject to the actual appointment.

72

Engineering employees

Six leaders; twelve contractor positions counted separately

₹13.8 crore

Annual engineering expense

₹5.2 crore approved development is a separate authority

23 years

Software career

Commerce developer from July 2003; CTO from January 2022

An interface does more than transmit a number or display a choice. It carries assumptions about units, valid combinations, usable actions and the state that another version must understand. I ask engineering to make those assumptions explicit, especially when an attractive demonstration can hide the customer path that exposes them.

Safiya Zevqenri

Chief Technology Officer

Areas of stewardship

Where accountability has been mine.

  1. IExplicit units across product interfaces
  2. IIValid configuration transitions
  3. IIIKeyboard-operable customer journeys
  4. IVState-aware release and retry design

Selected work

Decisions, and what they changed.

I

I approved centimetres at the screen while the receiver still expected metres

In 2021, as engineering director, I approved an interface change that expressed curtain width in centimetres.

The full account

II

Undo returned a familiar choice without restoring a valid design

A 2023 review of the furnishing configurator tested 360 scripted sequences rather than only the ordinary forward path.

The full account

III

A width control needed a keyboard route as well as a dragging gesture

In 2024, twenty-four adult participants attempted a defined width-setup task in our configurator.

The full account

In the words of others

Trusted by those who appoint.

Safiya explained why returning to an older application would not necessarily restore a usable customer design. That made the release delay a concrete enterprise decision rather than an unexplained technical objection.
Amrita NezqemiCEO, Vedqezmi Window Furnishings; fictional colleague
She kept the software's valid state connected with our product rules, including when a customer undid an earlier choice. Engineering did not claim that a convincing preview could replace physical feasibility.
Yusuf TevqeriTechnical-Design Head, Vedqezmi Window Furnishings; fictional colleague

The journal

Perspective, set down with care.

An invitation

Contact

A first outside non-executive contribution after company-specific learning, relationship review and employer agreement. I hold 1.2% within employee ownership and no statutory seat. Fictional IICA registration and proficiency assessment are complete; twenty-four provisional days remain subject to the actual appointment.

Open to
  • Board appointments
  • Advisory roles
  • Speaking invitations

office@safiyazevqenri.example