What you’ll do
Design the integration and event backbone that makes dozens of systems behave as one.
Key Responsibilities
- Design and build the integration layer across an enterprise service bus, API gateways, and an event streaming backbone
- Architect event driven integration: publish and subscribe, streaming, and change data capture for real time data movement
- Design API first contracts, with versioning, schema governance, and a developer portal
- Connect modern services and decades of legacy and government systems, cleanly and securely
- Engineer for resilience: idempotency, retries, dead letter handling, backpressure, and guaranteed delivery
- Implement B2B and EDI exchanges for cross entity document and data flows
- Build in security, observability, and distributed tracing so every message is auditable end to end
- Set integration standards and reusable patterns, and mentor engineers on them
What makes you a fit
- You have built enterprise integrations that moved real volume between real systems, in production
- You are fluent across an ESB, API management, and event streaming such as Kafka and webMethods
- You think event first and asynchronous, and you know when synchronous is the wrong choice
- You design for failure: idempotency, retries, dead letters, and exactly once where it matters
- You speak both modern API and legacy protocol, and you make them agree
- You hold a Bachelor's or higher in Computer Science, Software Engineering, or a related field
- You document clearly and leave patterns others reuse
- Bonus points for government or large enterprise integration landscapes
- Fluent English required; Arabic is a valuable advantage
If making systems agree is your kind of puzzle, we have the hardest one. Apply.
#IntegrationEngineering #APIs #EventStreaming #GovTech #Hiring