• *Role: MuleSoft QA**
• *Location : Remote**
• *Duration: Long Term Contract**
• *Note :**
• *This position supports a federal contract and requires U.S. citizenship and the ability to obtain and maintain a Public Trust determination as a condition of employment, in accordance with federal government requirements.**
• *Job Description:**
• *API Testing Fundamentals:**
· Solid grasp of REST API principles:
· Methods (GET, POST, PUT, DELETE)
· Headers, query params, path params
· Status codes (i.e. 500, 400, 401, etc.) and responses (200, 201, etc.)
· Understanding of SOAP (if used in legacy Mule services)
• *Technical Skills:**
· API Testing Tools (at least one):
· Postman – for manual API testing and collections
· SoapUI – for SOAP or more complex payloads
· cURL – for quick terminal-based tests
· JMeter – for performance/load testing
• *Testing Requirements:**
• *For APIs:**
· Validate:
· Input validation
· Response structure and content
· Error scenarios
· Authentication (OAuth, Basic Auth, etc.)
· Test various environments (DEV, QA, UAT, PROD)
• *For MuleSoft Scheduled Jobs**
:
· Know how and when scheduled jobs should run (cron expressions, triggers).
• *Ability to:**
· Validate time-based triggers
· Verify data processing after job completion
· Check for failures, retries, error handling
· Access to logs (Cloud Hub/Any point Monitoring) to confirm execution
· Access and Environment Setup
• *Access to:**
· Test environments (DEV, QA, UAT)
· Any point Platform Exchange for API specs (RAML/OAS)
· Any point Platform Runtime Manager (at least for viewing logs)
· Test data (or ability to generate it)
· Communication & Documentation
· Work closely with Developers, Integration Architects, and Product Owners
• *Be able to:**
· Understand API specifications (RAML/Open API)
· Write test cases/test plans
· Report bugs clearly with steps, logs, and screenshots
· Track issues in tools like Jira