From drawing review to the responsibility behind a claim

Mandate

Connect product evidence with the conditions behind customer-use claims

Outcomes

• Funded route and configuration qualification programmes
• Withheld a calendar-life claim unsupported by accelerated test hours
• Made instruction comprehension a defined development question

Decisions in context

I became CTO in January 2020. My remit covers 78 engineering colleagues through six leads, with ₹13.4 crore annual expense and ₹5.6 crore separately approved development capital. Zervqani employs 840 people and recorded ₹318 crore revenue and ₹24.7 crore operating profit for FY 2026. I report to Ritu Zeqruni, while Arun Vevquri leads quality through a separate CEO reporting line. The employee trust owns 45%, working founders 30% and a regional investor 25%. I am a trust beneficiary without individual shares. My cases examine route geometry, replacement mounting conditions, coating claims and instruction comprehension. I organise the technology programme while preserving specialist acceptance authority and the distinction between funded work and demonstrated results. A commercial statement must remain connected to the conditions its engineering evidence actually represents.

Reason for the move

Current technology leadership; no statutory appointment

Mandate

Lead product development and explain the basis of engineering claims

Outcomes

• Assumed broader product-programme responsibility
• Owned an acoustic claim approved from the wrong load condition
• Held preproduction units and retained correction cost and delay

Decisions in context

I became head of engineering in April 2015, reporting to the CEO. The company employed 610 people and recorded ₹224 crore revenue for FY 2016. I led 46 colleagues through four leads, with ₹8.1 crore annual expense. In 2017 I endorsed a loaded-use acoustic claim after an unloaded demonstration. Nine of thirty assemblies later missed the project's agreed criterion under loaded review. We held 120 preproduction units before customer release, delayed introduction ten weeks and incurred ₹48 lakh in testing and redesign. The case did not involve a field recall or injury. It exposed the inference I had accepted between different conditions. I learned to ask what the evidence represented before allowing a result to become a broader promise, while leaving technical acceptance with its authorised owners.

Reason for the move

Appointed CTO in January 2020

Mandate

Develop trolley products around defined use requirements

Outcomes

• Moved into industrial material-movement products
• Connected engineering work with load, route and interface conditions
• Built development leadership before enterprise engineering responsibility

Decisions in context

I joined Zervqani in September 2009 as development manager. The enterprise employed 390 people and recorded ₹126 crore revenue for FY 2010. I led 24 colleagues through three leads, with ₹4.2 crore annual expense under the engineering director. The products served factory material movement and were neither patient equipment nor lifting devices. The work made the relationship between a drawing and its use setting very practical. A product had to be understood through loads, routes, interfaces and the instructions supporting it, rather than only a nominal specification. My responsibility was to organise development around those requirements and explain unresolved questions. I did not hold every quality or safety approval. This appointment gave me the product context and leadership experience that later made my own overbroad acoustic inference especially important to acknowledge.

Reason for the move

Promoted to head of engineering in April 2015

Mandate

Coordinate design work with manufacturing and product-support requirements

Outcomes

• Moved into direct engineering-team responsibility
• Explained design choices across manufacturing and support
• Developed assembly-level judgement beyond isolated dimensions

Decisions in context

The senior-engineer appointment began in June 2004. Neqvori had 240 employees and ₹73 crore revenue for FY 2005. I led seven engineers with ₹68 lakh annual expense, reporting to the engineering manager. I had to explain design choices to people responsible for making and supporting the product. That experience showed me how a correct dimension could leave the complete assembly's behaviour unresolved. I learned to ask what changed when components were brought together and which assumptions needed confirmation in the intended setting. My authority remained within the engineering remit; wider commercial and product-release decisions belonged elsewhere. The role prepared me to manage a larger development group by connecting technical detail with the work other colleagues needed to perform, rather than treating a finished drawing as the end of the conversation.

Reason for the move

Joined Zervqani as development manager in September 2009

Mandate

Develop mechanical-design practice under experienced engineering supervision

Outcomes

• Entered engineering after completing the degree in June 1999
• Learned to relate drawings to working conditions
• Built technical experience before taking people and expense responsibility

Decisions in context

I joined Neqvori in July 1999 after completing mechanical engineering at Tezvashi Engineering College the previous month. The company employed 140 people and recorded ₹38 crore revenue for FY ending March 2000. I was one of six engineers reporting to the engineering manager, with no direct reports or expenditure authority. Early assignments required me to understand why a dimension or material requirement had been chosen and how the component would be used. I learned through review and correction rather than holding final programme approval. The experience established the beginning of a continuous engineering career and an interest in the conditions that make a technical result relevant. It also gave me a clear distinction between contributing to a design and being authorised to accept the complete product for its intended purpose.

Reason for the move

Promoted to senior engineer in June 2004