About the role:

Builds and runs software products for logistics, healthcare and enterprise clients — operational platforms, an Azure-based integration middleware, and the managed IT services around them. Our engineering team is small by design, with no layers between engineers and the people who use what they build.

This role owns our integration platform: the middleware and API layer through which our products, our clients’ systems and third-party services exchange data. You will build it, run it, and be the reason there is one integration platform across our products instead of one per project.

What “Solution Engineer” means here

You own a business process end to end — from the requirement to a business API running in production. We don’t hand work between someone who understands, someone who designs, someone who builds and someone who runs it. You do all of it, with support and with AI doing the typing.

- Understand — take the business requirement from the account manager, sit with the people who use the product, and write the process and its acceptance measure in their words.
- Design — produce the solution architecture document with our architecture agent: business API contract first, business rules second, data model third, UI or feed wiring last. Signed off by the Tech Lead and the account manager before code.
- Build — direct coding agents against our instruction sets and lint rules; review what they produce; consume the shared API store, gateway and UI packages rather than rebuilding them. .NET services and APIs on Azure, with tests.
- Test — against your own acceptance criteria before QA sees it.
- Deploy — through the pipeline to UAT and production; publish the API to the store. You ship your own work.
- Operate — first responder in production until the process meets its measure.




- Prove — demo the working process with its number, not a slide.

Time with users is planned into your sprint, not squeezed around it. You capture what users ask for.

What you’ll own

- The integration platform and API catalogue used across all products — contracts, versioning, idempotency, reconciliation
- Integrations between our products and client systems: ERP and accounting (QuickBooks, SAP, Dynamics or similar), EDI and partner feeds, healthcare data exchange (HL7/FHIR), identity and M365
- Data-posting flows where “zero duplicates, zero re-keying” is the acceptance standard
- Changes to shared packages by pull request to the Architecture Council — you make the change, they review; nobody waits

Must have:

- 5+ years building production services in C# / .NET (8 or 10) on Azure — App Service or Functions, Service Bus/Event Grid, Logic Apps, Key Vault, managed identity, API Management
- Integration engineering depth: idempotency, retries, dead-lettering, reconciliation, contract versioning — you can explain why a record was posted twice and design so it can’t happen again
- API-first design: you define the business contract before the screen, and you can defend a transaction boundary from the business process, not from the UI
- Works with AI coding agents daily — writes the instructions, reviews the output, owns the result.

Azure DevOps pipelines end to end
- Can sit with a non-technical user, write their problem in their words, and turn it into a design another engineer could build from
- Comfortable being on point in production for what you built

Valuable to have:

- EDI (X12/EDIFACT), HL7/FHIR, or any ERP/accounting integration
- Exposure to more than one domain — you’ll move between logistics, healthcare and enterprise IT clients
- Experience in a small team where you owned the outcome, not the ticket

📌 Solution Engineer - Integration Platform (.NET / Azure) (Hyderabad)
🏢 Eazyclosure
📍 Hyderabad