/ TEAMS · Specialist engineering · ERP Integration
Source engineers experienced in ERP workflows, EDI, master-data mapping, reconciliation and reliable business integrations. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
ERP API contracts
EDI data exchange
master data models
event idempotency
reconciliation jobs
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior ERP Integration Engineer
Inquire availability10+ years of experience · Romania
ERP Integration Engineer with 10 years in production systems, focused on ERP API contracts and EDI data exchange.
Languages: Romanian, English B2+
Mid-level ERP Integration Engineer
Available3+ years of experience · Czechia
ERP Integration Engineer with 3 years in production systems, focused on EDI data exchange and master data models.
Languages: Czech, English C1
Mid+ ERP Integration Engineer
Inquire availability5+ years of experience · Lithuania
ERP Integration Engineer with 5 years in production systems, focused on master data models and event idempotency.
Languages: Lithuanian, English B2+
Senior ERP Integration Engineer
Inquire availability11+ years of experience · Poland
ERP Integration Engineer with 11 years in production systems, focused on event idempotency and reconciliation jobs.
Languages: Polish, English B2+
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of ERP API contracts, EDI data exchange, master data models helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
ERP Integration responsibilities include erp api contracts, related edi data exchange, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ERP Integration responsibilities include edi data exchange, related master data models, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ERP Integration responsibilities include master data models, related event idempotency, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ERP Integration responsibilities include event idempotency, related reconciliation jobs, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ERP Integration responsibilities include reconciliation jobs, related access governance, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ERP Integration responsibilities include access governance, related erp api contracts, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Synchronize stock and orders with ERP. Define constraints around erp api contracts, map dependencies and test how the proposed implementation behaves under real operating conditions.
Replace fragile nightly batch exports. Define constraints around edi data exchange, map dependencies and test how the proposed implementation behaves under real operating conditions.
Resolve cross-system data discrepancies. Define constraints around master data models, map dependencies and test how the proposed implementation behaves under real operating conditions.
Build auditable business workflow integrations. Define constraints around event idempotency, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving ERP API contracts and what evidence led to a fix.
Which decisions around EDI data exchange and master data models were you personally accountable for?
Describe a production issue involving master data models and what evidence led to a fix.
Which decisions around event idempotency and reconciliation jobs were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to ERP API contracts. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
