Job Requirements

Senior Integration Engineer — Boomi & Business Central

- The primary job is twofold: build and maintain the Boomi integrations between Business Central and the rest of the stack, and own the operational side of transaction flow — finding, explaining, and resolving missing or failed transactions, and running dead letter queue (DLQ) operations so nothing quietly disappears.
- This is a hands-on engineering role, not an oversight role. You will be the person who gets paged when a day’s postings don’t reconcile, and the person who makes sure that stops happening.

Boomi ↔ Business Central integration
- Own, extend, and maintain Boomi processes moving financial and membership data into and out of Business Central.
- Build current integrations and modify existing ones as source systems change (Chargebee/Stripe billing events, Salesforce records, downstream Fabric/OneLake pipelines).
- Manage Boomi Event Streams topics, subscriptions, and environment configuration, including keeping test and production cleanly separated.
- Take over the existing integration codebase and documentation from our implementation partner, and get it to a state where we can support it without them.

Missing transactions and DLQ operations




- Run day-to-day DLQ operations: triage failed messages, diagnose root cause, correct, and replay.
- Build and maintain idempotency and duplicate-prevention controls so replays and reruns of financial data cannot double-post.
- Build silence and flow detection — alerting when an expected volume of transactions doesn’t arrive, not just when something errors.
- Investigate reconciliation breaks between Chargebee/Stripe and Business Central, trace them to the responsible hop, and drive them to zero.
- Maintain reconciliation reporting so Finance can see daily transaction counts and dollar totals matched across systems.
- Write and maintain runbooks so this work is repeatable by someone else, including handoff to teammates in other time zones.

Reliability and engineering practice
- Instrument the integration layer: logging, monitoring, alerting, and error classification that distinguishes retryable failures from ones needing human decisions.
- Improve error handling patterns rather than patching individual failures — retry policy, backoff, poison message handling, partial-failure semantics.

Work Experience 7-10Years

📌 Lead Software Engineer (Hyderabad)
🏢 Virtusa
📍 Hyderabad