SAP Integration Engineer

Experience: 4–8 years

Location: Bangalore (in-office)

Stack: SAP S/4HANA, SAP ECC, OData/BAPI/IDoc, Java 17, Spring Boot, PostgreSQL

Reports to: CTO

Zenalyst builds an enterprise agentic execution layer for the CFO's office — treasury, procure-to-pay and collections automation for large organisations. Our customers run SAP, and our value depends entirely on being able to read from and write to it reliably.

You will own SAP integration end to end: the connector, the field mappings, the posting logic, and the conversations with customer SAP teams that make deployments actually happen. When a payment succeeds in our system and has to post correctly to the customer's ledger, that is your code and your responsibility.

This role sits between engineering and the customer. You need both.

Integration engineering

• Build and own SAP connectors for S/4HANA and ECC — extraction, posting, and reconciliation
• Work across SAP integration surfaces: OData/API, BAPI/RFC, IDoc, CPI/PI, and file-based interfaces where that is what the customer has
• Build auto-triggered ERP posting flows: payment success in our system to a correctly posted document in the customer's ledger, with idempotency and no duplicate postings
• Map SAP master data and transactional structures to our domain model — vendors, GL accounts, cost centres, company codes, profit centres, payment terms, document types
• Handle the FI/CO, MM and TR-CM objects our products touch: vendor invoices, payment runs, bank statements, clearing, open items
• Build reconciliation and exception handling — what happens when a posting fails, partially succeeds, or is reversed on the SAP side
• Write the Java/Spring Boot service layer around the connector; this is not a pure SAP role

Customer-facing

• Work directly with customer SAP teams, basis teams and integration partners during implementation
• Scope integrations during pre-sales and pilots; produce technical documents customers teams will review
• Resolve production integration issues with the customer on the call
• Support security and technical due diligence questions on ERP connectivity

Essential

• 4–8 years working on SAP integrations, from the integration side rather than as a functional consultant
• Hands-on with SAP S/4HANA and ECC — you have actually posted documents, not just read master data
• Practical knowledge of at least two of: OData/RESTful ABAP APIs, BAPI/RFC, IDoc, SAP CPI/PI
• Working understanding of SAP FI, and ideally MM or TR-CM — you should know what a document type is and why the wrong one is a problem
• Programming ability in Java or Python; you will write and own production code, not just configure middleware
• Experience with authentication and connectivity in enterprise SAP landscapes — SNC, OAuth, principal propagation, Cloud Connector
• Strong written communication and comfort in front of a customer's technical team

Strongly preferred

• Spring Boot, REST API design, PostgreSQL
• Experience integrating SAP with third-party financial products, banks or payment systems
• ABAP reading ability — enough to understand a customer's custom Z-table or user exit
• Exposure to other ERPs: Oracle EBS/Fusion, Microsoft Dynamics, Tally
• Experience with idempotency and reconciliation in financial posting flows

Nice to have

• SAP BTP experience
• Real estate, infrastructure or construction sector SAP implementations
• Exposure to LLM APIs or agent frameworks

Someone who has been on the receiving end of a failed month-end close and understands why ERP integration is unforgiving. You should be equally comfortable reading an IDoc payload and telling a customer's SAP lead, politely, that their proposed approach will not work.

This is not a functional consulting role or a configuration role. If your experience is customising SAP for internal users rather than integrating it with external systems, this will not suit you.

• Full ownership of the ERP integration layer — one of the two or three things our product depends on most
• Direct customer exposure at enterprise scale, with founders in the room
• Real engineering work, not middleware configuration
• Direct access to the CTO; short decision cycles
• Competitive fixed compensation plus ESOP

• Send your CV to [HIDDEN TEXT] with the subject line SAP Integration Engineer — [Your Name]. Tell us about one SAP integration you built and what broke in production.