MuleSoft expertise needed
Budget: ₹12,500 – ₹37,500 INR
I need an experienced MuleSoft engineer who can work alongside me on our complex API landscape. The engagement is simple: be available Monday through Friday from 3 pm to 6 pm IST, jumping in only when there is actual work to tackle. If either of us has to skip a weekday session, we will catch up on the nearest weekend so that we never fall behind on deliverables. On quiet days with no pending tasks, you are free to stay offline.
The work itself ranges from reviewing and enhancing existing Mule flows to troubleshooting production issues and designing new integrations when required. You should already be comfortable with hands-on development in Mule Runtime and Anypoint Studio, creating and modifying policies, handling dataweave transformations, and generally keeping APIs performant and secure.
Orchestrate Salesforce batch processing, bulk inserts, and other API connections.
Each time we collaborate I will outline the day’s objective, share the relevant repositories and specifications, and expect concise progress notes or code commits by the end of the slot. Clear communication during the three-hour window is essential so that blockers are surfaced early.
If you thrive on complex API challenges and can reliably cover this IST time slot with the agreed flexibility, I would like to start as soon as possible.
The work itself ranges from reviewing and enhancing existing Mule flows to troubleshooting production issues and designing new integrations when required. You should already be comfortable with hands-on development in Mule Runtime and Anypoint Studio, creating and modifying policies, handling dataweave transformations, and generally keeping APIs performant and secure.
Orchestrate Salesforce batch processing, bulk inserts, and other API connections.
Each time we collaborate I will outline the day’s objective, share the relevant repositories and specifications, and expect concise progress notes or code commits by the end of the slot. Clear communication during the three-hour window is essential so that blockers are surfaced early.
If you thrive on complex API challenges and can reliably cover this IST time slot with the agreed flexibility, I would like to start as soon as possible.