Learning what another component will understand after our work is done

Mandate

Preserve valid customer-product meaning through configuration changes, usable interactions and state-aware release design

Outcomes

• Held configuration launch after forty-seven of 360 scripted sequences retained incompatible lining
• Funded keyboard alternatives and retained the limits of the twenty-four-participant comparison
• Deferred release after seventeen of forty-eight synthetic designs exposed rollback incompatibility
• Separated 120 logical preview requests from 1,080 backend attempts in a retry-amplification test

Decisions in context

I became CTO in January 2022. Seventy-two engineering employees now work through six leaders, with twelve contractor positions counted separately. My authority is ₹13.8 crore annual engineering expense and ₹5.2 crore separately approved development. The company employs 720 people in a twenty-eight-studio retail and online business, with ₹268 crore revenue and ₹21.6 crore operating profit for FY ending March 2026. I report to Amrita Nezqemi; Yusuf Tevqeri retains physical-design feasibility and the CIO owns enterprise systems and infrastructure. My cases examine configuration transitions, keyboard routes, saved-state reversibility and repeated backend work. I hold 1.2% within employee ownership and no statutory seat. The next learning challenge is to translate those engineering questions into collective oversight while understanding a receiving enterprise beyond the customer-product problems I have personally led.

Reason for the move

Continuing CTO responsibilities while preparing for a first outside non-executive contribution

Concurrent appointment

No statutory directorship is attached to the CTO role.

Mandate

Lead customer-software delivery while making interface assumptions and receiving behaviour explicit

Outcomes

• Retained responsibility for approving the centimetre interface before checking the metre-based receiver
• Held the 2021 release after eighteen of 120 synthetic quotations showed the unit mismatch
• Supported ₹41 lakh for the unit contract and its cross-component tests

Decisions in context

The engineering-director role began in April 2017 with forty-eight engineers, four heads and ₹8.4 crore annual expense under the CTO. Vedqezmi employed 510 people and recorded ₹189 crore revenue for FY ending March 2018. My title was a management appointment, without a statutory seat. In 2021 I accepted an interface change to centimetres while a receiving component still read the value as metres. Eighteen of 120 synthetic quotations exposed the mismatch before release. We held the change and allocated ₹41 lakh to its contract and tests. The account contains no live incorrect order, but my approval was still premature. The experience made me more deliberate about including receiving behaviour in a review, particularly when the visible product improvement makes a change appear simpler than its cross-component meaning actually is.

Reason for the move

Promoted to CTO with wider product-engineering authority

Concurrent appointment

Engineering director was a management role only, not a statutory appointment.

Mandate

Connect the customer configuration journey with technical-design rules and coherent software behaviour

Outcomes

• Developed a shared account of configuration meaning with physical-design specialists
• Separated software representation from authority to approve physical feasibility
• Built experience of customer changes and reversals within a product journey

Decisions in context

I moved into the retailer in September 2012 to lead twenty-eight engineers through three leads with ₹4.7 crore annual expense. Vedqezmi had 280 employees and ₹94 crore revenue for FY ending March 2013. Reporting to the CTO, I learned how software choices connected with a physical furnishing proposition. A customer could select familiar values while the resulting combination still required a design rule that was not obvious on the screen. I worked with specialists to make those relationships understandable without treating engineering as the owner of every physical decision. The role also made customer changes and reversals more important in my thinking. A forward demonstration could look complete while the product behaved differently when an earlier choice was replaced. That experience prepared me for wider leadership, though the later unit error shows why prior understanding must still be tested in each actual approval.

Reason for the move

Promoted to engineering director as the customer-product remit expanded

Mandate

Lead implementation while retaining the explanations and assumptions needed by receiving teams

Outcomes

• Made behaviour after edits and reversals part of team discussions
• Connected implementation decisions with the business meaning expected by another component
• Developed team responsibility without claiming ownership of every client policy

Decisions in context

In July 2007 I became engineering lead at Nebqeshi. The company employed 180 people and recorded ₹38 crore revenue for FY ending March 2008. Fourteen engineers worked within ₹1.6 crore annual expense under the engineering director. Leading a team meant thinking about the explanation another maintainer or component owner would need after our work was delivered. A demonstration could pass while leaving assumptions about changed inputs or reversed choices unclear. I wanted colleagues to describe those paths in terms of the business meaning they preserved, not only the code that executed them. The experience developed my interest in continuing product responsibility rather than project completion alone. Joining Vedqezmi offered that opportunity, with the added challenge of connecting a digital configuration to the judgement of physical-design specialists.

Reason for the move

Joined a retailer to take continuing responsibility for its customer-product engineering

Mandate

Implement commerce behaviour while learning how values and assumptions travel between components

Outcomes

• Entered software work after completing computer engineering
• Learned to ask what a valid value meant to its receiving component
• Built implementation experience before taking team and expense responsibility

Decisions in context

I joined Nebqeshi in July 2003 after completing computer engineering in May. The seventy-five-person business recorded ₹12 crore revenue for FY ending March 2004. I was part of an eight-person engineering team, with no direct reports or delegated budget. The work taught me that a value can be syntactically acceptable while carrying a meaning different from the one a receiving component expects. Senior colleagues retained architecture and client decisions; my responsibility was to implement and understand the behaviour assigned to me. I began to ask about the assumptions behind an example rather than regard a successful execution as the entire explanation. This appointment started a continuous twenty-three-year career and gave me a foundation for later team leadership, when I would need to make those explanations usable for other engineers as well as for myself.

Reason for the move

Promoted to engineering lead