Senior Middleware Engineer (Azure)

TL;DR

Senior Middleware Engineer (Azure/RabbitMQ/Redis): Designing and operating enterprise messaging and distributed systems integration with an accent on event-driven architecture and high availability. Focus on performance tuning of brokers, ensuring end-to-end observability, and implementing robust disaster recovery strategies.

Location: Remote (Must be based in Colombia, Brazil, Mexico, Argentina, Uruguay, or Bolivia)

Company

hirify.global provides mission-critical applications requiring high-performance distributed systems integration.

What you will do

• Architect, deploy, and operate middleware platforms including RabbitMQ, Redis, and Azure Service Bus across all environments.
• Design and govern event-driven integration patterns such as pub/sub, saga/choreography, and request-reply.
• Lead performance engineering by tuning broker configurations, cluster topology, and partitioning.
• Implement High Availability (HA) and Disaster Recovery (DR) using mirrored queues and geo-redundancy.
• Establish end-to-end observability using OpenTelemetry, Prometheus, and Grafana.
• Drive Infrastructure-as-Code (IaC) adoption for middleware provisioning using Terraform, Bicep, or Ansible.

Requirements

• 7+ years of software engineering experience, with 4+ years specifically focused on middleware.
• Expert-level proficiency with RabbitMQ, Redis, and Azure Service Bus in production enterprise environments.
• Strong understanding of distributed systems fundamentals (eventual consistency, idempotency).
• Proficiency in at least one language: C# (.NET), Java, Python, or Go.
• Hands-on experience with Kubernetes, Helm, and IaC tools like Terraform.
• Must be based in Colombia, Brazil, Mexico, Argentina, Uruguay, or Bolivia.

Nice to have

• Experience with Apache Kafka or Azure Event Hubs for high-throughput streaming.
• Familiarity with Apache Camel, MuleSoft, or Azure Integration Services.
• Microsoft certifications AZ-204 or AZ-305.
• Experience with service mesh technologies like Istio or Linkerd.
• Exposure to CQRS, Event Sourcing, and Outbox Pattern implementations.