Build for the interruption, not just the demonstration

I am chief technology officer of Pelvori Embedded Systems in Nagpur. We write firmware and communications software for industrial equipment makers, including data recorders and diagnostic accessories. I lead 154 engineers through five heads, with ₹36.8 crore annual engineering expense and a separate ₹7.2 crore laboratory and equipment programme. Our clients manufacture the devices and retain final product acceptance. My team must explain what our software has been tested to do and what the result does not establish.

I began in 2000 programming small control-device applications, then moved into firmware services and embedded architecture. The most useful lessons came from conditions that a normal demonstration did not include: an interrupted write, a malformed message or a repeated transmission after a connection returned. I became Pelvori's head of engineering in 2016 and CTO in April 2022. The role now requires me to make the cost of those conditions understandable to commercial colleagues as well as to engineers.

The decisions on this site include accepting extra device memory to make an interrupted update recoverable, widening a message-parser test beyond the examples used to repair it, preserving record identity across an unreliable connection and declining a compression setting that saved transmission volume at an unacceptable processing cost. Each decision changed a delivery conversation. I want an engineering team that can explain the specific evidence behind its confidence without converting a successful test into a universal assurance.

Current focus

I am improving how project teams preserve the conditions of a test when its result reaches a release paper or customer conversation. A number should retain its workload, device configuration and remaining uncertainty, so that an engineering observation does not become a product promise through abbreviated reporting.

Conversations I welcome

I would consider a first external board role in a specialist engineering-services or industrial-software business, with a contribution to product-risk and technology-investment discussions. I have provisionally allowed eighteen days annually, subject to employer agreement, induction needs and a company-specific review of relationships and eligibility.