

Mule Developer
β - Featured Role | Apply direct with Data Freelance Hub
This role is for a Mule Developer on a 6-month contract, starting WC 07/07/2025. Key skills include 3+ years in MuleSoft, API development, and Java proficiency. Remote work is available, with experience in CI/CD and production environments required.
π - Country
United Kingdom
π± - Currency
Β£ GBP
-
π° - Day rate
-
ποΈ - Date discovered
June 7, 2025
π - Project duration
More than 6 months
-
ποΈ - Location type
Remote
-
π - Contract type
Fixed Term
-
π - Security clearance
Unknown
-
π - Location detailed
England, United Kingdom
-
π§ - Skills detailed
#Agile #Elasticsearch #Database Management #Debugging #Monitoring #Jira #Programming #GIT #Documentation #Regression #Python #Version Control #API (Application Programming Interface) #Deployment #Migration #Elastic Stack #Java #MySQL #Computer Science
Role description
Mule Developer
6 Month Contract
Can be based across any of our Regional Centres
Must be able to start WC 07/07/2025
About the Role
:We are seeking a skilled Mule Developer to join our Check Challenge Appeal (CCA) development team. We are a dedicated, friendly team made up of product roles and technical developers/testers β delivering in an Agile manner to passionate and interested customers on behalf of the Value Office Agency (VOA). The ideal future colleague will be part of a Team of Developers/Testers responsible for our upgrade to Mule 4.
4Responsibilities
:The Mule developer will be responsible for the following tasks
β’ :Upgrade of APIs
β’ :Rebuild existing Mule 3.x APIs in Mule 4.4 adhering to updated best practice specifications
β’ .Development of New APIs: Build other required APIs in Mule 4.4 to best practice specifications as directed
β’ .Testing and Validation
β’ :Collaborate with testers to ensure APIs meet functional, non-functional, and performance criteria
β’ .Debug, resolve issues, and conduct regression testing as necessary
β’ .Collaboration with Team
β’ :Work closely within the wider team of CCA developers and testers to ensure consistency and quality in deliverables
β’ .Documentation
β’ :Document processes, updates, and lessons learned to provide a reference for future upgrades
.Deliverables
β’ :Upgraded/enhanced CCA APIs compatible with Mule 4.4
β’ .Comprehensive testing results and documentation
β’ .Deployment-ready APIs ensuring smooth production transition
β’ .Technical documentation for the APIs rebuilt/enhanced during the work
β’ .Ongoing/Continuous Improvement
β’ :Identify opportunities for process and code improvements within the production environment
β’ .Proactively engage in troubleshooting, optimising, and scaling backend services to support growing business needs
.Performance Metrics
β’ :Successful migration of all identified Mule 3.x APIs to 4.4
β’ .Development and deployment of new APIs within defined timelines
β’ .Zero critical defects in production post-deployment
β’ .Positive feedback from stakeholders and users regarding the upgraded APIs
.Technologies
β’ :Mule ESB (Enterprise Service Bus) - Key integration platform for managing and orchestrating service connectivity and data flows between applications
β’ .Mule Anypoint Studio - Primary development environment for designing and debugging Mule ESB flows
β’ .RabbitMQ - messaging bus that facilitates communication between different services/components in the system by reliably queuing, routing, and delivering messages
β’ .Java - Core language for backend services, necessary for writing, maintaining, and troubleshooting applications that integrate with Mule ESB
β’ .MySQL Database - Database management and querying, essential for accessing, updating, and managing application data
β’ .Elastic Stack (Elasticsearch, Kibana) - Primarily used for monitoring and log analysis; leveraging this stack to diagnose production issues, track service performance, and support troubleshooting
β’ .Bamboo CI/CD - Continuous integration and deployment tool for automating builds, testing, and deployments in both dev and production environments
β’ .Stash (Git) - Version control for managing and tracking code changes, supporting collaboration across the development team
β’ .Jira - Issue and project tracking tool, used to coordinate production support requests, development tasks, and release management
.Qualifications
β’ :Bachelorβs degree in Computer Science, Engineering, or a related field, or equivalent experience
β’ .3+ years of Mule: confident understanding of MuleSoftβs Anypoint Platform, including API development, integration patterns and Mule 4 architecture
β’ .Upgrading knowledge: Experience upgrading from Mule x to Mule 4.4 including migration of code, connectors, and dependencie
β’ sConnector Upgrades: Familiarity with updating legacy connectors to Mule 4 compatible versions building bespoke or migrating to new connectors
β’ .Proficiency in backend programming languages such as Java, Python, Node.js, or similar
β’ .Familiarity with production environments and CI/CD pipelines
β’ .Experience with service monitoring, debugging, and troubleshooting tools
β’ .Ability to work collaboratively in a fast-paced environment, balancing multiple priorities
.
Mule Developer
6 Month Contract
Can be based across any of our Regional Centres
Must be able to start WC 07/07/2025
About the Role
:We are seeking a skilled Mule Developer to join our Check Challenge Appeal (CCA) development team. We are a dedicated, friendly team made up of product roles and technical developers/testers β delivering in an Agile manner to passionate and interested customers on behalf of the Value Office Agency (VOA). The ideal future colleague will be part of a Team of Developers/Testers responsible for our upgrade to Mule 4.
4Responsibilities
:The Mule developer will be responsible for the following tasks
β’ :Upgrade of APIs
β’ :Rebuild existing Mule 3.x APIs in Mule 4.4 adhering to updated best practice specifications
β’ .Development of New APIs: Build other required APIs in Mule 4.4 to best practice specifications as directed
β’ .Testing and Validation
β’ :Collaborate with testers to ensure APIs meet functional, non-functional, and performance criteria
β’ .Debug, resolve issues, and conduct regression testing as necessary
β’ .Collaboration with Team
β’ :Work closely within the wider team of CCA developers and testers to ensure consistency and quality in deliverables
β’ .Documentation
β’ :Document processes, updates, and lessons learned to provide a reference for future upgrades
.Deliverables
β’ :Upgraded/enhanced CCA APIs compatible with Mule 4.4
β’ .Comprehensive testing results and documentation
β’ .Deployment-ready APIs ensuring smooth production transition
β’ .Technical documentation for the APIs rebuilt/enhanced during the work
β’ .Ongoing/Continuous Improvement
β’ :Identify opportunities for process and code improvements within the production environment
β’ .Proactively engage in troubleshooting, optimising, and scaling backend services to support growing business needs
.Performance Metrics
β’ :Successful migration of all identified Mule 3.x APIs to 4.4
β’ .Development and deployment of new APIs within defined timelines
β’ .Zero critical defects in production post-deployment
β’ .Positive feedback from stakeholders and users regarding the upgraded APIs
.Technologies
β’ :Mule ESB (Enterprise Service Bus) - Key integration platform for managing and orchestrating service connectivity and data flows between applications
β’ .Mule Anypoint Studio - Primary development environment for designing and debugging Mule ESB flows
β’ .RabbitMQ - messaging bus that facilitates communication between different services/components in the system by reliably queuing, routing, and delivering messages
β’ .Java - Core language for backend services, necessary for writing, maintaining, and troubleshooting applications that integrate with Mule ESB
β’ .MySQL Database - Database management and querying, essential for accessing, updating, and managing application data
β’ .Elastic Stack (Elasticsearch, Kibana) - Primarily used for monitoring and log analysis; leveraging this stack to diagnose production issues, track service performance, and support troubleshooting
β’ .Bamboo CI/CD - Continuous integration and deployment tool for automating builds, testing, and deployments in both dev and production environments
β’ .Stash (Git) - Version control for managing and tracking code changes, supporting collaboration across the development team
β’ .Jira - Issue and project tracking tool, used to coordinate production support requests, development tasks, and release management
.Qualifications
β’ :Bachelorβs degree in Computer Science, Engineering, or a related field, or equivalent experience
β’ .3+ years of Mule: confident understanding of MuleSoftβs Anypoint Platform, including API development, integration patterns and Mule 4 architecture
β’ .Upgrading knowledge: Experience upgrading from Mule x to Mule 4.4 including migration of code, connectors, and dependencie
β’ sConnector Upgrades: Familiarity with updating legacy connectors to Mule 4 compatible versions building bespoke or migrating to new connectors
β’ .Proficiency in backend programming languages such as Java, Python, Node.js, or similar
β’ .Familiarity with production environments and CI/CD pipelines
β’ .Experience with service monitoring, debugging, and troubleshooting tools
β’ .Ability to work collaboratively in a fast-paced environment, balancing multiple priorities
.