From explaining a dimension to owning the product account

Mandate

Connect equipment development to the installation, maintenance, recovery and future-use conditions the enterprise is prepared to support.

Outcomes

• Retained separate engineering dispositions within a cassette-recovery programme.
• Required acoustic evidence for the assembled proposition.
• Connected co-developed package reuse to its actual permission account.
• Brought the delivery route into the assembly-design decision.

Decisions in context

Since July 2020 I have led forty-six engineering employees through four leads, with six external specialists counted outside that team. I report to Feroz and carry ₹11.4 crore annual operating authority plus a distinct ₹4.6 crore laboratory and qualification capital programme. The enterprise has 320 employees and ₹186 crore FY 2026 revenue; it supplies equipment rather than owning the customers' energy assets. The remanufacturing, acoustics, collaboration and delivery cases show how technical responsibility extends beyond the first performance demonstration. Qualified design, quality and site owners retain actual acceptance and safe-work responsibilities. My 0.15% total-equity holding sits within the employee vehicle, and I have no statutory seat. A first outside opportunity would require a specific relationship and time review, with the unfinished proficiency assessment made clear rather than hidden behind the CTO title.

Reason for the move

Current role; examining preparation and fit for a first outside contribution.

Mandate

Develop equipment propositions with a defensible account of performance, installation and service requirements.

Outcomes

• Approved a compact layout without sufficient removal evidence.
• Owned the subsequent eighteen-unit review and its seven affected arrangements.
• Kept revised-layout approval distinct from completed physical work.

Decisions in context

The product-engineering director role carried thirty-four colleagues and ₹7.8 crore annual expenditure. It was a functional appointment, not a statutory directorship. Customers' limited floor space made compact layouts a legitimate design objective, and I supported that objective too readily when a removal task remained unexamined. Hema had identified the difference between reaching the cassette and taking it out. The later review found adequate provision in eleven of eighteen delivered units and a problem in seven. I supported the ₹1.2 crore response and retained my approval in the account. Five affected arrangements later received approved revised layouts; two remained pending. The promotion to CTO followed that period without rewriting it as an uninterrupted record of correct decisions. The experience changed the evidence I expected before a design advantage became a customer proposition.

Reason for the move

Promoted to CTO with broader responsibility for technical strategy and development investment.

Concurrent appointment

The director title described the product-engineering function only; no statutory appointment accompanied it.

Mandate

Develop an equipment design account that recognises the customer's process, physical setting and responsible engineering owners.

Outcomes

• Moved from general thermal engineering into a heat-recovery equipment business.
• Developed closer design discussion with service and site colleagues.
• Built broader responsibility before the product-engineering director appointment.

Decisions in context

I joined Jezqavthi with a twenty-two-person design team and ₹4.3 crore annual expenditure. The company then employed 126 people and recorded ₹37 crore FY 2009 revenue, substantially smaller than the business described on my current profile. Heat recovery required me to understand the customer's process and physical constraints while keeping specialist design and site responsibilities explicit. The product was not simply a drawing to be released; it would be installed, serviced and sometimes adapted within another organisation's work. I developed a closer conversation with colleagues who saw those later stages, although that experience did not prevent my subsequent compact-layout error. The role expanded my ability to explain technical assumptions to commercial sponsors. It also taught me to distinguish an equipment supplier's scope from the customer's authority to operate the wider installation.

Reason for the move

Promoted into enterprise product-engineering leadership as the business expanded.

Mandate

Coordinate design decisions across manufacture, installation and the intended service route.

Outcomes

• Took on staff and expenditure responsibility beyond individual design work.
• Examined how factory choices could create work at a customer site.
• Built experience explaining technical trade-offs before the move to heat recovery.

Decisions in context

In March 2001 I moved into a management role with twelve colleagues and ₹2.1 crore annual function expenditure. The wider company's 190 people and ₹48 crore revenue described enterprise scale, not my own team or budget. I began coordinating decisions that affected different stages of an equipment's use. A manufacturing simplification could change installation work, while a service instruction could depend on space that an earlier layout no longer allowed. The engineering account needed to describe those consequences before one stage's convenience became another stage's unexplained burden. I reported to the engineering director and had no board appointment. After more than seven years, the heat-recovery opportunity offered a larger team and a closer connection to the industrial context in which the equipment would be expected to perform and remain serviceable.

Reason for the move

Joined a specialist heat-recovery enterprise for a broader design remit.

Mandate

Prepare and examine mechanical design work with its assumptions visible to the responsible engineering lead.

Outcomes

• Learned to distinguish a component dimension from the task around it.
• Developed care in explaining assumptions before drawing release.
• Built supervised engineering experience before taking on a product team.

Decisions in context

My career began in June 1994 after the mechanical-engineering degree completed that May. I worked under a product lead in an eighty-eight-person company, without delegated spending or people-management responsibility. The early work taught me to explain the assumption behind a design detail so another engineer could examine it. A drawing needed to be understandable beyond the person who produced it, including the limits of the task it represented. I learned that the physical component was only part of the work someone would later have to perform. I did not yet own the wider product proposition or the commercial consequences of a release. Keeping that modest scope in the chronology matters: it shows how responsibility developed and makes the later removal-space error an accountable judgement, rather than an implausible claim that a long career had eliminated every blind spot.

Reason for the move

Promoted into product-engineering management after sustained design and coordination work.