Senior MuleSoft Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Qualifications, Benefits, maybe Pay? The posting includes "Compensation & Benefits" but says salary range is estimate, actual may vary. It says "Compensation & Benefits" includes salary range estimate, benefits package. We need to include Pay section only if posting actually states them. It says "In accordance with applicable law, the salary range provided is Verndale's reasonable estimate of the salary for this role. The actual amount may vary..." It does not give actual numbers. It says "Compensation & Benefits" includes salary range estimate but not actual numbers. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since salary range is not provided (just says estimate but not numbers), we should not create Pay section. Benefits: they mention benefits: "competitive benefits package", "top-of-the-line Health Insurance, plus monthly perks", "generous paid company holidays, vacation, and paid sick time", "RRSP savings plan", "ample company paid holidays and personal time off", "remote work possibility". Those are substantive benefits. So we can include Benefits section. Schedule: not mentioned. So omit. We need sections: About the role (but we already have a heading "About The Role" in the posting). We should use

for section headings. The page already shows job title, so we don't repeat it. So we output:

About the role

... (the paragraph about role)

Then Responsibilities:

Responsibilities

• ... each bullet. Qualifications:

  Qualifications

  • ... each bullet. Benefits:

    Benefits

    • ... each bullet. We must preserve all substantive information, not invent or summarize away detail. Need to include details like Expected Contract Duration: 3 months. Where to put? Could be in About the role paragraph or maybe a separate metadata paragraph. Since we cannot create a heading for minor metadata, we can fold into a short

      after About the role or within About the role. Probably include a short paragraph after About the role:

      Expected contract duration: 3 months.

      We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Ten Great Reasons to Work at Verndale" which is basically benefits/ culture. We need to extract benefits from that. Also there is "Compensation & Benefits" paragraph. We'll combine. We must not repeat job title as heading. Not include Job ID/requisition numbers. Now let's extract content. About the role paragraph: "The Senior MuleSoft Developer / Integration Engineer will design, develop, test, deploy, and support enterprise integrations using MuleSoft Anypoint Platform. The role will implement API-led solutions across Experience, Process, and System API layers while maintaining clear separation between channel-facing services, business orchestration, and backend system connectivity. The developer will be responsible for delivering secure, scalable, reusable, and observable integrations that follow established MuleSoft architecture, development, testing, security, and DevOps standards." We can keep that. Responsibilities list: many bullet points. Need to capture each as
    • . Let's list them: - Build and maintain MuleSoft applications across the API-led architecture. - Experience APIs: Public and authenticated front end facing contracts. - Process APIs: Business validation, orchestration, transformation, idempotency, authorization context, and cross-system coordination. - System APIs: Salesforce, SMB connector, file services, and other approved backend connectivity. - Design and maintain RAML/OAS API specifications, reusable data types, examples, traits, security schemes, error models, and API versioning standards. - Implement Salesforce integrations using the MuleSoft Salesforce Connector, including data retrieval and updates, object operations, queries, authentication, and integration with approved Salesforce objects and business processes. - Support Salesforce authentication and integration patterns including OAuth/JWT, REST APIs, and event-driven integration where Platform Events or similar mechanisms are required. - Implement secure files and document retrieval using MuleSoft SMB/File connectors, allowlisted paths, read-only credentials, controlled binary streaming, and secure error handling. - Integrate with backend HTTP/REST-based services to retrieve and process data, metadata, documents, and other content as required. - Implement Microsoft Entra ID integration for API authentication and authorization using OAuth 2.0 / OpenID Connect patterns. - Configure MuleSoft APIs to validate Entra ID-issued JWT access tokens, scopes, roles, audiences, issuers, and claims as required by the security design. - Support Entra ID client-credentials flows for system-to-system integrations and authorization-code/OIDC patterns where authenticated user context must be propagated. - Configure and apply API Manager policies including OAuth/JWT validation, client ID enforcement, rate limiting, throttling, CORS, IP restrictions, SLA policies, and other required security controls. - Implement consistent correlation IDs, canonical error handling, structured logging, retries, timeout handling, and dependency-health monitoring. - Develop comprehensive MUnit test suites covering positive scenarios, validation failures, downstream failures, error scopes, connector mocking, transformations, and edge cases. - Support CI/CD through Azure DevOps or equivalent tooling, including Git branching, pull requests, Maven builds, automated MUnit execution, artifact creation, configuration management, and environment deployments. - Support deployment and operational readiness through Anypoint Monitoring, Runtime Manager, API Manager, dashboards, alerts, and application/dependency monitoring. Qualifications list: - 5+ years of enterprise integration development experience, with approximately 3–5+ years of strong hands-on MuleSoft/Mule 4 experience and demonstrated ownership of production integrations. - Strong hands-on experience with MuleSoft Anypoint Platform and Mule 4, including Anypoint Studio, Design Center, Exchange, API Manager, Runtime Manager, Anypoint Monitoring, and CloudHub/CloudHub 2.0 or Runtime Fabric. - Strong experience with API-led connectivity, DataWeave 2.0, and RAML/OAS design, including Experience, Process, and System APIs, reusable API specifications, transformations, validation, error handling, and API versioning. - Hands-on experience with Salesforce integrations using the MuleSoft Salesforce Connector, including REST APIs, OAuth/JWT authentication, Salesforce data models, and preferably Platform Events. - Experience implementing Microsoft Entra ID integration and API security, including OAuth 2.0, OpenID Connect, JWT validation, client credentials, scopes/roles/claims, and API Manager security and rate-limiting policies. - Experience with SMB, File, FTP/SFTP, and external REST/SOAP integrations, including secure file access, binary/PDF/image streaming, large-file handling, and secure credential management. - Strong MUnit testing experience, including connector/process mocking, DataWeave testing, positive and negative scenarios, error-path testing, and appropriate code coverage. - Hands-on CI/CD and DevOps experience, preferably Azure DevOps, including Git/PR workflows, Maven builds, automated MUnit execution, artifact management, secure configuration, and deployments across DEV, QA, UAT, and Production. - Strong understanding of production-ready MuleSoft development, including API policies, TLS/certificates, secure properties, structured logging, correlation IDs, PII masking, monitoring, alerts, retries, timeout handling, troubleshooting, and production support. - Strong experience with production-grade MuleSoft API development, including API performance optimization, pagination, caching, idempotency, concurrency handling, resilient integration patterns, Salesforce query/API-limit management, secure binary streaming, and reusable error models. - Ability to configure and troubleshoot Anypoint Monitoring, API Manager policies, runtime alerts, dependency thresholds, private connectivity, and production operational controls. Benefits: from "Ten Great Reasons to Work at Verndale" and "Compensation & Benefits". Let's extract substantive benefits: - Rapidly growing company, scrappy and entrepreneurial culture since 1998. - Relentlessly curious, enthusiastically solve clients’ complex business problems through technology, data, and design. - Culture enabling every person to do the best work of their career. - Regular training and professional development to move careers forward. - Client and employee satisfaction are top business metrics. - Celebrate and champion diversity, equity, and inclusion. - Generous paid company holidays, vacation, and paid sick time from day one. - Top-of-the-line Health Insurance, plus monthly perks customized to meet individual employees’ needs. - Support healthy work/life balance. - Fully remote enabled, embracing evolving definition of workplace. - Competitive compensation and comprehensive coverage for medical, dental, life, disability and an RRSP savings plan offered to all salaried, full-time employees. - Ample company paid holidays and personal time off make work-life balance possible. - For some roles, remote work is a definite possibility; we believe in hiring the best and keeping our own happy and motivated. We need to avoid filler like "competitive compensation" without numbers? It's okay as it's a benefit statement. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits section is okay because they state benefits. Even if some statements are vague like "competitive compensation", that's not filler like "varies". It's okay. We should not include the EEO boilerplate. Now produce HTML. Structure:

      About the role

      The Senior MuleSoft Developer / Integration Engineer will design, develop, test, deploy, and support enterprise integrations using MuleSoft Anypoint Platform. The role will implement API-led solutions across Experience, Process, and System API layers while maintaining clear separation between channel-facing services, business orchestration, and backend system connectivity. The developer will be responsible for delivering secure, scalable, reusable, and observable integrations that follow established MuleSoft architecture, development, testing, security, and DevOps standards.

      Expected contract duration: 3 months.

      Responsibilities

      • Build and maintain MuleSoft applications across the API-led architecture.
      • Experience APIs: Public and authenticated front end facing contracts.
      • Process APIs: Business validation, orchestration, transformation, idempotency, authorization context, and cross-system coordination.
      • System APIs: Salesforce, SMB connector, file services, and other approved backend connectivity.
      • Design and maintain RAML/OAS API specifications, reusable data types, examples, traits, security schemes, error models, and API versioning standards.
      • Implement Salesforce integrations using the MuleSoft Salesforce Connector, including data retrieval and updates, object operations, queries, authentication, and integration with approved Salesforce objects and business processes.
      • Support Salesforce authentication and integration patterns including OAuth/JWT, REST APIs, and event-driven integration where Platform Events or similar mechanisms are required.
      • Implement secure files and document retrieval using MuleSoft SMB/File connectors, allowlisted paths, read-only credentials, controlled binary streaming, and secure error handling.
      • Integrate with backend HTTP/REST-based services to retrieve and process data, metadata, documents, and other content as required.
      • Implement Microsoft Entra ID integration for API authentication and authorization using OAuth 2.0 / OpenID Connect patterns.
      • Configure MuleSoft APIs to validate Entra ID-issued JWT access tokens, scopes, roles, audiences, issuers, and claims as required by the security design.
      • Support Entra ID client-credentials flows for system-to-system integrations and authorization-code/OIDC patterns where