Mulesoft Technical Lead

Omm IT Solutions•Genoa Township, OH

1d•Remote

About The Position

Lead the discovery, design, and delivery planning of enterprise integrations using MuleSoft. This role interfaces with product owners, business SMEs, enterprise architects, security, and source/target system teams to define integration requirements and translate them into a buildable MuleSoft backlog. The Technical Lead owns the integration solution design and provides day-to-day technical direction to an offshore delivery team, ensuring consistent implementation, quality, and operational readiness.

Requirements

Bachelor’s or Master’s degree in Computer Science, Information Systems, Finance, or related field
7+ years in integration engineering, including 3+ years leading integration delivery teams.
Strong hands-on MuleSoft experience (Anypoint Platform) with proven delivery of multiple production integrations.
Solid integration architecture skills: API-led design, system/process/experience layering, reusable asset strategy.
Strong API design and lifecycle management: contract-first thinking, versioning, backward compatibility.
Deep understanding of integration reliability concerns: retries, idempotency, messaging patterns, error handling, resiliency controls.
Experience coordinating across a geographically dispersed team (onshore/offshore), with strong backlog decomposition and technical review practices.
Strong stakeholder management: able to translate ambiguous requirements into actionable delivery plans and influence cross-team decisions.
Working knowledge of security and compliance requirements for integrations (authN/authZ, encryption, auditability).

Nice To Haves

Experience with CloudHub and/or Runtime Fabric, and the deployment/operating model trade-offs.
Familiarity with Anypoint governance (API Manager policies, Exchange asset lifecycle, platform standards).
Domain experience in wealth management / broker-dealer operations and advisor workflows.
Experience modernizing integration landscapes (reducing point-to-point, introducing canonical models/events, improving observability).

Responsibilities

Partner with business and technology stakeholders to understand end-to-end process flows, integration touchpoints, and system-of-record boundaries.
Elicit and document functional and non-functional requirements (volumes, latency/SLAs, availability, RPO/RTO, security, compliance, audit).
Inventory and validate integration dependencies: upstream/downstream systems, APIs/events/files, batch schedules, error handling expectations, and operational ownership.
Identify gaps in existing API contracts, data models, environments, access, and test data; drive actions to unblock delivery.
Define target-state integration architecture using MuleSoft (API-led connectivity where appropriate: Experience / Process / System APIs).
Produce architecture artifacts (context diagrams, sequence diagrams, interface contracts, error handling standards, and deployment view).
Design API specifications (RAML/OAS as applicable), versioning strategy, compatibility approach, and deprecation plan.
Define integration patterns per use case: Sync vs async, event-driven vs request/response, batch vs real-time.
Idempotency/deduplication, retries, DLQ/replay strategy, and exception routing.
Ensure security-by-design (OAuth2/mTLS, client management, policy enforcement, secrets handling, least privilege).
Define observability standards (correlation IDs, structured logging, dashboards/alerts, runbooks).
Decompose designs into epics/stories/tasks with clear acceptance criteria, test strategy, and definition of done.
Provide hands-on technical leadership to offshore developers: code reviews, design walkthroughs, implementation patterns, and troubleshooting.
Establish working norms for distributed delivery (handoffs, overlap hours, backlog grooming, and technical checkpoints).
Maintain delivery pace while protecting architectural integrity; manage technical debt consciously with transparent trade-offs.
Define and enforce MuleSoft development standards (naming, packaging, common libraries, error handling, logging, and performance).
Partner with QA on a layered test approach (MUnit, contract testing, integration testing, performance testing).
Support CI/CD and environment promotion practices (config separation, secrets, approvals, rollback strategy).
Drive production readiness: operational runbooks, monitoring/alerting, support model, and incident response approach.