- Location
- Hyderabad Knowledge Park Tower 2, India
- Workplace
- Hybrid
- Type
- Full-time
- Department
- Engineering
- Closing date
- Today
- Source
- Workday
Description
End Date
Thursday 23 July 2026We Support Flexible Working – Click here for more information on flexible working options
Flexible Working Options
Hybrid WorkingJob Description Summary
Level 5 will have all traits from Level 4 but sometimes will lead technical development on product/team/domain level. They may start taking responsibility for overall tech delivery & app ownership alongside their own software engineering output. They are experts of parts of the domain and technology used.Job Description
Job Profile Summary
Software Engineer will lead technical development and delivery at Team and sometimes Lab level. They can be a Line Manager who will act as co-lead with the Team PO for overall delivery. In these cases, they will be responsible for overall tech delivery, line management & app ownership alongside their own software engineering output. Others will operate as Individual Contributors, who are specialists in particular technology areas.
In addition, the role provides end-to-end ownership of Power Platform (Power Apps, Power Automate, Copilot Studio) solutions, aligning delivery to business priorities, enterprise architecture, and Modern Workplace strategy.
Job Description
- Grows own capabilities and develops others, providing specialised training in Power Platform and promoting reusable components and best practices.
- Identifies improvements to processes and systems, shaping Power Apps and Copilot use cases into a prioritised delivery pipeline.
- Supports secure data access, connectors, and compliance across Power Platform environments.
- Builds and deploys Power Apps (Canvas and Model-driven) aligned to business processes and user needs.
- Owns end-to-end delivery lifecycle (design, build, test, deployment, adoption) for Power Platform solutions.
- Manages performance and delivery, ensuring application ownership, stability, and continuous improvement.
- Translates business requirements into scalable Power Platform solutions.
- Designs solutions integrated with enterprise systems (e.g. APIs, D365, SharePoint).
- Applies Responsible AI governance, data policies, and security controls.
- Implements automation and integrations using Power Automate.
- Defines UAT, testing and validation for apps and Copilot agents.
- Contributes to platform roadmap, adoption strategy, and value tracking through analytics.
Additional Role Context
Together we'll make it possible...So what can we offer you in return?
We deeply value diversity and are proudly committed to being an equal opportunity employer. If this is you, come and join our inclusive, values-led culture passionate about making a difference.
Our continued dedication to helping Britain prosper means that as a colleague you can make a difference to customers, businesses and communities.
Though this role description is drafted as if it is part of the Client Experience & Data Platform and recruited in the UK, it is actually for an LTC role which will support that platform from India, reporting from a line management perspective into LTC. So, the role provides technical and change services to the UK platform and while the activities and responsibilities of the role holder can be assignment managed (i.e. day to day task direction) as the platform requires, the role holder remains an LTC colleague and their line management remains in LTC.
Regardless of anything to the contrary in the Role Description, while LTC Role holders can be tasked to lead aspects of the technical and practical delivery and performance of platform’s objects, ultimate accountability, responsibility and ownership must rest with a UK-located platform decision maker. So, any reference to leadership, line management or supervision of teams in the role description can only refer to the line management of LTC based colleagues, or the provision of services to the platform. Any reference to customers refers to the business the platform supports (or the needs of that business’s customers), not customers of the platform. Refer to the LB UK/LTC Roadmap if in any doubt.