Edward Jones · Tempe, AZ

Salary
Posted
Jul 20, 2026
Location
Tempe, AZ
Last confirmed open
Jul 22, 2026

What this job asks for AI summary

A senior engineering role focused on owning the architecture, standards, and long-term roadmap of a MuleSoft integration platform — specifically Mule Runtime Fabric and Omni Gateway. Day-to-day work spans API governance, CI/CD and DevSecOps practices, cloud and hybrid deployment decisions, and cross-team collaboration on enterprise integration strategy. Best suited to an experienced MuleSoft platform engineer with deep API security and architecture knowledge.

Senior level · 5+ years · St. Louis, MO-IL · Full-time

Must have (13)
MuleSoft · 5+ yrsMule Runtime FabricOmni GatewayAPI ManagerAPI-led connectivitymicroservices architectureAWS, Azure or GCPOAuthmTLSZero TrustCI/CDDevSecOpsInfrastructure as Code
Nice to have (2)
Kubernetesservice mesh

“or” means any one of them counts — you don't need all of them.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

Roughly 20 people in the St. Louis, MO-IL area plausibly meet what this posting asks for (software developers). range 5–35

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What gives you an edge
Zero Trust3%

Rare in this occupation — lead with these, and say what you built with them.

What won't set you apart
CI/CD45%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $131,867 (middle half $103,906–$159,758).

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (7)

The posting lists two office locations — Tempe, AZ (CBSA 38060) and St. Louis, MO (CBSA 41180) — with an expectation of four days per week in-office for candidates within commutable distance; remote is not offered. St. Louis is listed first in the job description narrative context and is the firm's primary home office, so it is used as the primary CBSA, but Tempe, AZ is an equally valid work location.

The role is classified as Software Developers (15-1252) because the primary day-to-day work involves building, architecting, and evolving an integration platform (MuleSoft Runtime Fabric, Omni Gateway, CI/CD pipelines, IaC). 15-1299 (Computer Occupations, All Other) is noted as a runner-up given the strong enterprise/integration architecture framing.

The 5+ years figure is tied specifically to MuleSoft platform experience; no separate overall role-level experience floor is stated, so the overall years minimum is set to 5 to reflect this as the closest proxy for the role-level gate.

AWS, Azure, and GCP are listed together as 'AWS, Azure, and/or GCP' — indicating interchangeable cloud platform experience; AWS is used as the primary skill name with Azure and GCP as alternatives.

DCR (Dynamic Client Registration) is mentioned alongside OAuth and mTLS as a networking/security concept but is a sub-feature of OAuth flows rather than a distinct named tool; it is captured under the OAuth skill rather than emitted separately.

MuleSoft certifications (e.g., MuleSoft Certified Platform Architect) and experience with API governance/CoE and AI-driven integrations appear under 'What Will Set You Apart,' which is a clearly secondary/preferred section.

No compensation figures are provided in the posting.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗