Senior Engineer - Frontend and Solace

About the role

We are looking for an Engineer – Frontend and Solace to build, administer, and support event‑driven messaging capabilities across integrated platforms, focusing on Solace configuration, queue/topic design, message delivery reliability, and production support in a Kubernetes/OKE environment. The role also serves as the Domain SME for the Solace messaging layer, handling both platform administration and messaging design best‑practice contributions.

Key responsibilities

• Develop and support front‑end applications with Solace integration.
• Build and maintain event‑driven messaging services using Solace.
• Perform Solace administration: configuration, maintenance, patching, upgrades, and queue/topic design.
• Troubleshoot message delivery failures, integration issues, and messaging bottlenecks.
• Collaborate with application teams to define messaging SLAs for critical payment and onboarding flows.
• Support design reviews, operational readiness, deployment validation, and production support.
• Maintain documentation for queue/topic configurations, support procedures, known issues, and handover.
• Contribute to enterprise messaging and event‑architecture best‑practice frameworks.
• Act as Domain SME, defining reusable queue/topic patterns and design standards.
• Provide design input and participate in review sessions for new messaging requirements.
• Own platform administration standards, including runbooks, SOPs, and backup/DR readiness.

Required profile

• Strong analytical and troubleshooting abilities.
• Excellent communication and documentation skills.
• Ability to work independently and within cross‑functional teams.
• Willingness to learn and adapt to new technologies.

Required skills

• Solace Administration – configuration, maintenance, patching, upgrades, queue/topic design.
• Frontend Technologies – NextJs, NestJs, Angular, React.
• Messaging Support – troubleshooting delivery failures and bottlenecks.
• Platform Operations – Kubernetes and OKE operational awareness.
• Collaboration and SLA Definition – defining messaging SLAs.
• Tools and Documentation – creating operational docs, troubleshooting notes, handover procedures.
• Design & Best Practices – messaging design standards, reusable patterns, runbooks, SOPs, backup/DR.
• Good to have: experience with payment/transaction processing systems, Mulesoft ESB, Anypoint Platform, Camunda BPM.