Integration & Eventing
Hire Integration Engineers
MuleSoft, Kafka, APIs and the spine between systems.
Integration is where enterprise programmes fail quietly. Nothing errors. The same order is simply counted twice, or a status update lands out of order and a shipment shows as delivered before it was picked. Both are discovered in a reconciliation weeks later rather than in a log the same afternoon.
That shapes the work: contracts agreed before code, idempotency treated as a requirement rather than a defensive measure, ordering guarantees stated rather than assumed, and a dead-letter path a human can actually work through. The tooling — MuleSoft, Kafka, an API gateway, a middleware somebody chose in 2016 — matters less than whether the person has had to explain a reconciliation break to finance.
MuleSoft Developers
MuleSoft developers who design the contract before the flow, and build for the second delivery of the same message.
Apache Kafka Engineers
Kafka engineers who treat topic design, ordering and replay as decisions to be made rather than defaults to be inherited.
Elasticsearch Engineers
Elasticsearch engineers who treat the mapping and the relevance as the product, not the cluster.
What to look for when hiring
Ask what happens when the same message is delivered twice, four hundred milliseconds apart. If the answer is a uniqueness constraint and nothing else, ask what the caller sees.