Technical Architect - SAP ABAP with BTP CAPM

About the company

GyanSys is a global mid-market digital transformation and systems integration partner serving enterprise clients worldwide. The company delivers implementation projects, managed services, and data analytics across SAP, Salesforce, Microsoft, and other leading enterprise technology platforms. With a blended delivery approach and a team of more than 3,500 consultants, GyanSys supports over 350 enterprise customers across the Americas, Europe, and APAC.

Role overview

This position is for a senior SAP technical professional who can design, build, and support enterprise-grade solutions across SAP ECC and SAP S/4HANA, while also contributing to cloud-native development on SAP BTP. The role combines ABAP expertise, modern SAP development frameworks, integration work, UI development, and clean-core extensibility practices.

Key responsibilities

• Design and deliver custom solutions for SAP ECC and SAP S/4HANA using ABAP, ABAP OO, OData, CDS views, and RAP-based development.
• Work on ABAP proxies, web services, workflows, Smart Forms, Adobe Forms, SAP Scripts, SAP Fiori, RF screen programming, and SAP Notes implementations for localization needs.
• Develop cloud applications on SAP BTP using CAP, Node.js or Java, SAP HANA Cloud, and Fiori Elements with attention to scalability, security, and maintainability.
• Create and maintain integrations through SAP BTP Integration Suite, APIs, event-driven mechanisms, and other modern integration approaches aligned to clean-core standards.
• Build responsive Fiori/UI5 applications with a strong focus on user experience and design quality.
• Apply clean-core and extensibility-first methods to reduce core modifications in S/4HANA and improve cloud readiness.
• Partner with functional teams to convert business needs into technical designs and dependable solutions.
• Write automated unit tests, participate in code reviews, follow engineering standards, and maintain clear technical documentation.
• Improve the performance of ABAP programs, database queries, and integration flows for enterprise reliability.
• Develop reusable libraries, frameworks, and digital assets that speed up delivery across teams.
• Support 3PL and customer integrations using EDI, IDocs, ALE, and related interface technologies for secure and scalable data exchange.
• Assist with SAP upgrades, feature pack updates, and regression testing, including SPDD, SPAU, custom code alignment, and clean-core compliance.
• Build secure solutions following SAP security practices such as authorizations, CDS access control, OAuth/JWT for BTP, and identity authentication.
• Use DevOps tools for CI/CD, transport automation, repository-based development, and lifecycle management across on-premise and BTP landscapes.
• Keep up with emerging SAP technologies, including Joule, AI-based automation, generative AI extensibility, and BTP innovations.
• Collaborate with architects, product owners, and integration teams to design end-to-end solutions across ERP, BTP, cloud services, and non-SAP systems.

Candidate profile

• Hands-on SAP BTP development experience with CAP or RAP models, HANA Cloud, Cloud Application Programming, API management, and Integration Suite.
• Strong working knowledge of SAP Fiori design principles and responsive UI5 application development.
• Comfort with Git-based development, automated testing frameworks, CI/CD pipelines, and DevOps toolsets.
• Good understanding of SAP extensibility approaches, including in-app, side-by-side, and developer extensibility.
• Experience working in Agile or Scrum environments.
• Strong communication skills and the ability to work with global teams and translate functional requirements into technical solutions.
• Interest in newer SAP capabilities such as Joule, Business AI, process automation, and event mesh.
• Willingness to travel globally up to 25%.

Additional information

The role is based in Hyderabad, India. The hiring preference indicates a global travel expectation of up to 25%. No salary, stipend, or number of openings was specified in the source.