The scope behind a career in engineering responsibility

Mandate

Make engineering behaviour and operating response support the lender's authorised business decisions

Outcomes

• Kept a generic schedule convention from becoming an unauthorised lending rule
• Completed a tested credential transition without disabling validation
• Narrowed routine diagnostics and revised event ordering and paging assumptions

Decisions in context

As CTO I lead engineering through five heads and report to the CIO, rather than holding the whole enterprise information remit. The fourteen contracted specialists remain separate from the 64 employees in my team account. I am responsible for the technical implementation and its evidence within an approved expense and capital envelope. Credit policy, lending terms and accounting remain with the appropriate owners. The cases show choices about calendar rules, authentication transitions, diagnostic purpose and the meaning of event and alert signals. Some delayed features or made investigation less convenient. I retain those costs because they explain what the company accepted. The role has also required me to change my own preference for broad paging when the response evidence showed how much interpretation it imposed on engineers. My board exposure remains executive presentation through the CIO, with no statutory appointment.

Reason for the move

Current appointment; considering a first outside contribution subject to fit and consent

Mandate

Coordinate delivery and maintenance while making the response work behind software changes explicit

Outcomes

• Added team and operating responsibility to the earlier architecture remit
• Examined the support and credential dependencies left after a technical release
• Developed the engineering-management perspective later carried into the CTO role

Decisions in context

The head-of-engineering appointment widened my responsibility from choosing an implementation approach to ensuring that teams could operate and maintain it. I led 36 engineers through four leads under the CIO, within a defined annual expense remit. A release could satisfy its functional test while leaving the next shift uncertain about an alert, a diagnostic request or an upcoming credential change. I wanted that response work included in the plan rather than described as an operational detail after delivery. The company had grown to ₹670 crore outstanding loans, but that figure did not confer lending authority on the engineering function. I worked with service and professional owners to keep the implementation connected to their decisions. The later CTO appointment added a wider investment and leadership remit, while retaining the need to explain the practical cost of the behaviour the teams were building.

Reason for the move

Promoted to CTO in February 2021

Mandate

Translate authorised lending and operating requirements into explicit, reviewable software behaviour

Outcomes

• Learned how technical defaults could acquire unintended business meaning
• Worked with credit operations and finance on the authority behind system rules
• Developed the sector understanding required for broader engineering leadership

Decisions in context

Moving to Nagpur brought me into a lender whose systems influenced the work colleagues performed for business customers. I led eighteen colleagues through two leads and reported to the CIO. The role required me to learn the business meaning behind schedules and status changes without pretending that engineering experience supplied credit or legal authority. A general-purpose component could perform its operation correctly while implementing the wrong convention for a particular product. I began to make the assumption visible in the design review, with examples that the responsible business owner could examine. The financial remit covered architecture and engineering work, not loan approvals or the portfolio itself. The promotion followed a broader ability to connect technical choices with their operating consequences, including the work that would remain when a specification could not yet give a complete answer.

Reason for the move

Promoted to head of engineering in June 2016

Mandate

Lead implementation teams while making specifications and continuing support assumptions reviewable

Outcomes

• Took people and expense responsibility beyond individual engineering work
• Asked teams to explain the business assumption behind a technical default
• Built the management experience used in a later financial-services architecture role

Decisions in context

The management appointment put me in charge of sixteen engineers through two leads, with an annual expense allocation under the head of engineering. I learned that a test can show agreement with a specification while leaving the specification's business assumption unexamined. That was particularly easy when a standard component supplied behaviour that everyone found familiar. I asked teams to describe the choice in ordinary language and identify the owner entitled to approve it. The approach did not remove the need for detailed engineering tests. It made those tests easier to connect with the client's intended result. I also began to see how maintenance and support effort could disappear from an estimate focused on the first release. The move into business lending followed an interest in work where the relationship between a software rule and its practical consequence needed especially careful explanation.

Reason for the move

Joined Qevruni in September 2009 and relocated to Nagpur

Mandate

Implement and test specified application behaviour under engineering supervision

Outcomes

• Built practical development and testing experience after the engineering degree
• Learned to distinguish a valid output from a correctly understood requirement
• Prepared for later team leadership without claiming early executive authority

Decisions in context

My first appointment began in July 1995 after the computer-engineering degree. I worked in a six-person development group under a team lead, without supervisory or spending authority. The job was to implement specified behaviour, reproduce faults and test the result. A technically valid output did not always settle whether we had understood the request correctly. I learned to preserve the example and ask about the intended business event before changing the code to make a demonstration look right. The client owner retained the decision about the requirement, while senior engineers reviewed the implementation. Those limits were useful training rather than constraints to hide in a later career account. The management promotion added responsibility for people and resources, but the underlying habit remained: a plausible technical answer needs a question whose meaning the responsible person has actually confirmed.

Reason for the move

Promoted to engineering manager in April 2002