MuleSoft Architect

As a MuleSoft Architect, you won't be handed a ticket queue or a seat at someone else's table. You own the integration platform for our clients, end to end — standing up the API-led foundation, shaping the solution from discovery through delivery, and building the AI systems that let a small team ship like a large one. You set the architectural direction, and you build the engine the rest of us deliver inside.

This is a seat for someone at the top of the craft: deep enough in MuleSoft to make the hard architectural calls, fluent enough in AI to build with it rather than around it, and credible enough in front of clients to turn a single engagement into a lasting partnership. If that's you, keep reading.

Remote (US). Raleigh–Durham a plus, not required. The ideal candidate will be based in Eastern or Central timezones. Must be US-based and authorized to work in the US; no sponsorship.

• The architecture. You design the target-state, API-led platform — system, process, and experience layers — set the standards and reusable templates teams actually use, and own the technical direction for your engagements. You make the calls; you don't wait for sign-off.
• The AI delivery engine. This is the differentiator. You don't just use AI tools — you build and direct the agentic systems that generate the bulk of our delivery, then bring the team along to work inside them. You prove what got faster.
• Our AI edge. Our internal agents, skills, and delivery process are only an advantage if they stay ahead of the field — and you own keeping them there. You fold in new techniques as models and tooling evolve, contribute agents and process improvements back to the team, and make sure the way we deliver keeps getting sharper rather than going stale.
• Discovery and the solution. You're the technical voice in the room from the first client conversation — assisting with discovery, and shaping the solution architecture, and reviewing, pressure-testing, and signing off on SOWs where architecture lands as a value narrative, not a tech briefing.
• Delivery and the relationship. You own scope, guard against creep, and drive milestones to the outcome. You surface risk early, before anyone has to ask, and turn one engagement into a long-term partnership.
• The engineering bar. CI/CD strategy, secure-by-default integration, and decisions documented so they're repeatable.
  

• Architect-level MuleSoft. Expert API-led design on Mule 4 / Anypoint — clean system/process/experience boundaries, DataWeave, CloudHub 2.0 / Runtime Fabric, Exchange-driven reuse and governance. You've owned target-state architecture and the trade-offs that come with it.
• A real AI build practice. You seek these tools out — Claude, Cursor, LLM-based assistants in your daily rotation — and you've built with them, not just used them. You can show where AI made delivery faster and where it falls down.
• Client-facing consulting depth. You've owned client engagements at a consultancy or SI — running discovery, aligning stakeholders from exec to dev, and contributing to LOE/SOW. Internal IT delivery doesn't translate.
• Delivery and DevOps fundamentals. You ship the way real engineering orgs do — branch strategy, peer review, automated deploys across environments on CloudHub 2.0 or Runtime Fabric, monitoring that surfaces issues before the client does, and security built in from the first commit (OAuth2/OIDC, mTLS, contract-first APIs, no secrets in source). The baseline you operate from, not a checklist you bolt on at the end.
• Direct, proactive communication. You say it in three sentences, not ten, and you surface risk before it surfaces you.
• MuleSoft architecture certification — Platform Architect or Integration Architect — or equivalent architecture depth you can demonstrate.

• Leading presales end to end — discovery through signed SOW
• Documented AI-acceleration work with real before/after delivery gains
• Cloud and networking depth on AWS/Azure you can defend on cost and performance
• Event-driven patterns (Anypoint MQ, Kafka)
• Based in the Raleigh / Triangle area — a plus given our hybrid future, but not required