Head of Technology and Operational Efficiency
About the role
iLEAD runs 19 undergraduate and postgraduate programmes across business, media, animation, IT and allied health sciences. As the institution has grown, so has the number of software systems, tools and manual processes in daily use across departments. Several of these are underused, poorly integrated, or worked around rather than worked with.
This role exists to change that. The person we are looking for will take ownership of how technology is chosen, implemented and actually used across iLEAD, and will work with each department to find where better use of technology and clearer measurement can improve output and reduce cost. This is not a software-building role. It is a role about making the systems we have, and the ones we adopt next, deliver real value in the hands of the people who use them.
It is important to be clear about the balance of this work. The technical side matters, but it is the smaller part. The larger and harder part is getting people across a busy institution to adopt new systems and new ways of working, and to keep using them after the novelty fades. As a rough guide, expect around two thirds of the role to be people, change and coordination across departments, and about one third to be technical. The right person is comfortable with both, and is drawn to the harder two thirds rather than hiding in the easier one third.
What you will own
ERP rollout, adoption and maintenance
- Take end-to-end ownership of the institution's ERP: implementation, integration, maintenance, rollout, and day-to-day usage across departments.
- Resolve outstanding integration gaps so that data flows cleanly between systems instead of being re-entered by hand, working with the relevant departments to agree the workflows that make this possible.
- Bring the institution's core administrative processes onto the system in a way that is accurate, trackable and reliable, so that leadership has a dependable picture of operations and finances.
- Make sure departments use the ERP as intended, not partially or reluctantly, and hold the standard once it is set.
Communication and collaboration platforms
- Introduce, roll out and embed communication and collaboration platforms across the organisation.
- Design the adoption plan, run the training, and follow up until the new way of working has replaced the old one in practice, not just on paper.
KPI and KRA implementation
- Build and own a KPI and KRA framework, and roll it out across departments so that each function has clear, measurable outcomes.
- Work with department heads to understand what each team actually does day to day, and turn that into a shared, visible picture that closes the gap between departments and leadership.
- Provide leadership with clear reporting on how the organisation is performing at department and institution level, so that decisions rest on evidence rather than impression.
Efficiency and Cost
- Work department by department to understand how work gets done today and where technology and better process can improve output, remove duplicated effort, and reduce cost.
- Review the software, tools and subscriptions the institution pays for, identify what is unused or overlapping, and consolidate where it makes sense.
- Bring findings to leadership with clear numbers and a practical plan, including the difficult findings, presented with judgement and discretion.
Technology Direction
- Advise leadership on which tools and platforms iLEAD should invest in, extend, or retire, with a clear read on cost versus value.
- Identify where AI-enabled tools can genuinely improve efficiency in administrative and support functions, and introduce them where they earn their place. AI is one tool among several here, not the purpose of the role.
- Set basic standards for data quality, access and security across the systems in use.
What we are looking for
Essential
- Experience owning or driving the implementation, rollout and adoption of business systems such as ERP, and getting non-technical teams to use them properly.
- A track record of change management: introducing new tools, systems or measurement across an organisation and making the change stick against resistance.
- Experience defining and rolling out performance measurement such as KPIs or KRAs across multiple teams.
- The standing and maturity to work with senior, long-serving colleagues, and to be firm and diplomatic at the same time, including when the message is not one people want to hear.
- A strong understanding of how technology, data and process connect, with enough technical depth to hold vendors and internal teams to account.
- Comfort with data: able to build or direct the reporting that shows leadership where effort and money are going.
- Clear, concise written and spoken communication, and the confidence to present uncomfortable findings to leadership.
Desirable
- Experience in a multi-department, service-oriented organisation, and exposure to the education sector.
- Hands-on experience with AI-enabled tools and workflows in an operational setting.
- Experience with software licensing or cost and subscription rationalisation.
- Familiarity with common ERP suites, collaboration platforms, and modern data and reporting tools.
What success looks like in the first year
These are deliberately practical targets for the first twelve months. The value of this role compounds over time as adoption deepens.
- Months 1 to 3: A clear picture of the systems, tools and processes in use across iLEAD, what they cost, and where they are underused or duplicated.
- Months 3 to 6: ERP integration gaps closed and a working adoption plan in place for the departments not yet using it as intended, with core administrative and financial processes moving onto the system.
- Months 6 to 9: Communication platform rolled out and in regular use across the organisation, and the KPI and KRA framework agreed and beginning to roll out.
- Months 9 to 12: A first set of efficiency and cost findings delivered to leadership, with agreed actions, and clearer visibility between departments and leadership than the institution has today.
Who this role suits, and who it does not
- This role will suit someone who takes satisfaction in making systems and people work well together, and who is willing to be the person who asks why a process exists at all. It involves sustained work across departments, some of it against resistance, and it rewards patience, follow-through and clear judgement more than technical brilliance alone.
- It will not suit someone looking to build software products, lead a large engineering team, or work primarily in code. It will also not suit someone who is strong on analysis but light on the human and organisational side, because that human and organisational side is the larger part of the job. iLEAD is an education institution, not a software company. The work here is a better-run, more efficient organisation.
How to apply
Please send your CV and a short note on a system, tool or measurement you introduced somewhere, and how you got people to actually use it, to [email protected]
Pay: ₹80,000.00 - ₹120,000.00 per month
Work Location: In person
