Mulesoft Architect

About This Role The Architect designs the full solution end to end. Not a flow in isolation, but the whole journey: the front-end button a user presses, the questions it asks, the automation it triggers in the backend, and the output it produces.

An Architect’s solution design (designing smaller experiences well) is the skill that gets you into this level; solution architecture (designing holistic client experiences well) is the skill you master inside it.

The Architect is the minimum builder level on every standard Delegate engagement. The architect runs sprint meetings without a Principal in the room, and works in two modes on every piece of work: hands on keyboard directly, delegating/teaching the work to an Engineer and checking the returned work against the design before it goes live.

What You Own

• Solution architecture for your engagements: the full experience, what the users experience when interacting with your solutions to what the solutions actually do behind the curtain.
• Definition of done for every task on your sprints, and the scope cutoffs that keep iterations honest
• Sprint leadership: facilitating sprint meetings and planning, owning the cadence, with the Engagement Manager handling scheduling and communications around it
• Build-or-delegate decisions: executing heavy or novel work yourself, or assigning work to Engineers with teaching where needed, and evaluating assigned work against the design before it ships
• Client working sessions: sitting alongside client users and working through it live
• User feedback: listening to what the user says and architecting for it, not defending how it was technically built
• UI/UX of the solutions you design
• Sprint demos
• Business process design, in tandem with the Engagement Manager: the EM facilitates the conversation, you do the design work
• Backlog synthesis: turning what accumulates into a coherent, prioritized picture
• Quality of everything that ships under your design, whether you or an Engineer built it

The Value You Drive The Architect is where you own and deliver on the clients trust of our commitment to deliver what matters to them. You run the sprint that provides the deliverable. You outline the practical value and impact of the deliverable and the design of solutions that hold up end to end, scale past go-live, and make a measurable difference in how the client operates. The strategic intent of the level is multiplication: one Architect having more impact on more accounts, through Engineers who build alongside you and grow under you.

Working Structure

• Reports to a Principal with escalations and updates; perfectly capable on your own, which is exactly why the reporting is light
• Typical load: 4-6 engagements across sectors, in a mix of hands-on and delegate-and-evaluate modes
• Directs the Engineers on your engagements, keeps them client-facing alongside you, and flags pairing risk to the Principal before it becomes build-quality risk
• Floats across sectors and practices; sector alignment begins at the Principal level
• Growth path: Architect to Principal, confirmed by leadership judgment on top of full L1/Tier 2 mastery

Requirements

• Experience and certification in Mulesoft
• End-to-end Salesforce solution architecture: a requirement carried from front-end interaction through backend automation to final output, every layer yours
• Strong hands-on build skill; you have not stopped building just because you design
• Sprint leadership: running a sprint meeting with a client in the room, setting the agenda, keeping it moving without technical backup
• Scope judgment: definition of done, cutoffs, and iterative breakdown under real scope-creep pressure
• Delegation judgment: scoping work clearly enough that an Engineer can execute it, teaching where needed, then evaluating the result against the design rather than redoing it
• Stakeholder fluency: working directly with clients who know what they want, and when needed, working with the client on possible alternate approaches to solutions if you see issues with their current proposed solution.
• User-feedback discipline: hearing the user out and architecting for them. Remember, they are the person working with your solution day-in and day-out.
• Fluency with AI tooling as a design and build accelerator

Nice to Have

• Experience and/or certification in CPQ or RevCloud
• Experience across more than one sector or practice area; this role floats rather than specializes
• A track record of designs other builders executed without you in the room
• Experience mentoring or directing other builders’ work
• Data model design, data migration, and integration architecture experience