I build the internal systems on which a technology company's promises depend.

I am the CIO of Rujantra Systems, an Indian enterprise application engineering and support business. My remit is the technology through which my colleagues work: assignment records, internal applications, development environments, access and the allocation of shared services. I do not own every client solution merely because it contains software. Delivery leaders remain responsible for their commitments, and customer requirements may limit the environments their teams can use. My contribution is to make those boundaries visible before an internal process turns an assumption into an apparent fact.

I learnt this distinction through thirty-three years of work that began with internal deployment records. A staffing screen can show a named engineer against a project without establishing the person's readiness, the engagement's authority or the customer's permission. A common development environment can be useful without being appropriate for every contract. I prefer to show the unresolved conditions beside the achieved result. That can make a programme less impressive at its first presentation, but it gives colleagues a better basis for the decision they must actually make.

Today I lead 212 employees through six direct reports, with fifty contracted specialists counted separately. My FY2026–27 technology authority is ₹128 crore: ₹82 crore for continuing operations and ₹46 crore for change. I report to the CEO and present selected investment and operating matters to the board; I am not a director. The scale of my role matters because these choices affect an enterprise of 8,400 people. It does not remove my obligation to distinguish what a pilot established from what still needs to be learnt.

Current focus

I am improving the connection between internal technology evidence and the operating decisions it supports. This includes clearer project authority, better records behind shared-cost allocation and more disciplined evaluation of developer tools. I want delivery colleagues to be able to question the assumptions behind a system result without needing to reconstruct its entire technical history.

Conversations I welcome

I welcome conversations about internal CIO responsibilities, responsible use of developer tools and a carefully assessed external board contribution. My present executive duties continue; any appointment would require consent, conflict review and an agreed time commitment.