Free · takes a minute · your resume fills your profile
CoreHRx never asks candidates for money. If anyone does, .
Role at a glance
You will
Lead solution design and technical delivery for enhancements across ERP solutions, procurement workflows, invoice processing, supplier…
Design and improve API, event-driven, EDI and data integration patterns supporting internal systems and external partners.
Build reusable integration and partner-onboarding patterns that improve delivery speed, consistency, transaction traceability and…
Experience
8–10 years
Must-have skills
AWSETLNode.jsProcurementPythonReact
Work mode
On-site
How well do your skills match this job?
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Job description
Location: Hyderabad, India
Job Title: Supply Chain Technology Lead Work Location: Hyderabad Position: Fulltime Summary of role The Supply Chain Technology Lead provides hands-on technical leadership for the applications, workflows and integrations that support the end-to-end Procure-to-Pay (P2P) ecosystem. The role owns day-to-day technical delivery and continuous improvement across ERP applications and partner integrations, working closely with Finance, Procurement, Operations, technology teams and vendors.
Core activities
Act as the day-to-day technical owner for the P2P application and integration landscape, maintaining a clear technical roadmap aligned with the broader technology strategy.
Lead solution design and technical delivery for enhancements across ERP solutions, procurement workflows, invoice processing, supplier onboarding and partner digital integrations.
Translate business requirements into pragmatic, secure and supportable technical designs within agreed enterprise architecture and engineering standards.
Remain hands-on with solution analysis, design reviews, integration troubleshooting, code and configuration reviews, and the resolution of complex production issues.
Design and improve API, event-driven, EDI and data integration patterns supporting internal systems and external partners.
Build reusable integration and partner-onboarding patterns that improve delivery speed, consistency, transaction traceability and reconciliation.
Improve observability across the P2P estate through effective logging, monitoring, alerting, runbooks and root-cause remediation.
Identify and deliver practical automation opportunities across P2P workflows, including intelligent document processing, exception handling and AI-assisted operations.
Coordinate internal engineers, delivery partners and vendors, setting technical direction and assuring the quality, maintainability and supportability of delivered solutions.
Partner with Finance, Procurement and Operations stakeholders to prioritise work, explain technical options and risks, and support adoption of delivered capabilities.
Embed security, privacy, resilience and data-governance requirements into solution design and operational practices.
Coach developers and technical contributors, progressively building the leadership and architecture capability required to take broader ownership of the Core Systems domain.
Skills and Experience
8-10 years of experience in software engineering, enterprise applications or systems integration, including at least 2-3 years operating as a Senior Developer or Technical Lead.
Strong hands-on capability in full stack custom application design, integration engineering and the support of business-critical systems using Python, react.js, node.js and AWS cloud stack.
Experience with Camunda, Cleo and Netsuite or similar solutions highly desirable.
Experience working with ERP, finance, procurement or supply-chain platforms and an understanding of end-to-end Procure-to-Pay processes.
Experience leading mid-level and junior developers situated on-site and offshore.
Practical experience with APIs, messaging, ETL, event-driven integration or EDI patterns, including monitoring and production troubleshooting.
Experience delivering solutions across cloud and SaaS environments using modern software development and release practices.
Ability to translate business needs into clear solution designs and make sound technical trade-offs within enterprise standards.
Strong analytical and problem-solving skills, with accountability for seeing issues through from diagnosis to sustainable resolution.
Confidence working directly with business stakeholders, vendors and delivery partners, supported by clear written and verbal communication.
Ability to lead through influence, coach others and balance hands-on technical work with delivery coordination and stakeholder engagement.
Tertiary qualification in computer science, software engineering, information systems or a related discipline, or equivalent practical experience.
Key Stakeholders
Within the team: Chief Data & Technology Officer, Core Systems contributors, Data & AI Engineering, Platforms, Digital Resilience and Business Partnering.
Within the business: Finance, Procurement and Operations stakeholders who own P2P processes, priorities, controls and adoption.
Delivery partners and vendors: application, implementation, support and integration partners engaged across the P2P estate.
External partners: suppliers, logistics providers and other connected organisations involved in partner onboarding and transaction flows.
This page is for Indian job seekers preparing for cloud engineer, DevOps, backend and solutions architect roles that list AWS as a skill, whether you are a fresher with a first certification or an experienced engineer moving into a senior role. It covers 60 questions in three levels: core services and concepts, then design and configuration choices for one to three years of experience, and finally scenario, security, cost and troubleshooting questions asked in senior rounds. Read each answer, explain it aloud in your own words, and try the CLI commands in a practice account with a billing alert set.
Questions you may be asked
What is the difference between an AWS Region and an Availability Zone?
Explain the AWS shared responsibility model.
What is Amazon EC2, and how do you read an instance type name like m7g.large?
What is Amazon S3, and what are its main storage classes?