Technical Lead MuleSoft/Cloud Technologies

Technical Lead – MuleSoft and Cloud Technologies

This is not a project-level lead. It is a cross-scenario, cross-domain leadership role responsible for ensuring coherence, integrity, and forward alignment across:

• Portal migration and modernization
• CRM selection and implementation
• Data & insights capability development
• Enterprise integration and SaaS enablement
• Cloud architecture, DevSecOps, and observability

The ATL operates at the intersection of architecture, engineering, product, risk, and governance. The primary objective is to ensure that client transformation delivers stability today, optionality tomorrow, and scalable differentiation long term.

Core Responsibilities

1. Architectural Accountability Across the Ecosystem

• Own the end-to-end target architecture vision across portal, CRM, data, integration, and cloud.
• Ensure all solution decisions align to API-first, event-driven, domain-oriented design principles.
• Prevent architectural fragmentation across agile pods and vendors.
• Define and enforce integration standards, canonical models, and system boundaries.
• Serve as final technical escalation point for cross-domain conflicts.

1. Strategic Technical Leadership

• Translate client product-led operating model ambition into technical architecture and delivery guardrails.
• Guide build vs. buy vs. refactor decisions using structured evaluation criteria.
• Ensure long-term scalability, compliance, and SaaS-readiness are embedded early.
• Balance modernization velocity with operational risk and regulatory constraints.

1. Governance, Risk & Compliance Integration

• Participate in executive governance and risk forums.
• Oversee SOC 2 continuity and transition considerations during portal migration.
• Ensure DevSecOps practices, identity controls, logging, and auditability are embedded from day one.
• Align AI-enabled features with responsible AI governance and human-in-the-loop controls.
• Maintain architectural risk register and mitigation roadmap.

1. Multi-Vendor & Internal Collaboration

• Act as as technical counterpart to client Enterprise Architect and CTO organization.
• Coordinate with third-party platform vendors (e.g., CRM, ERP, DAF administration partners).
• Clarify technical ownership boundaries between Orion and other ecosystem players.
• Drive shared accountability without duplication or architectural drift.

1. Engineering & Delivery Oversight

• Ensure agile pods remain aligned to shared architectural standards.
• Review major technical designs (HLD/LLD) before implementation.
• Champion CI/CD maturity, automation, test coverage, and observability.
• Promote AI-assisted engineering practices where appropriate (e.g., code generation, testing automation).
• Support capacity planning and sequencing across phases (Stabilize → Modernize → Optimize).

1. Capability Building & Transition

• Mentor client architects and senior engineers.
• Ensure documentation, runbooks, and architectural rationale are captured continuously.
• Support progressive transition of ownership to client internal teams.
• Design for reduced long-term vendor dependency.

Required Experience

Experience Profile

• 12–18+ years in enterprise architecture or senior technical leadership roles.
• Proven leadership in complex, multi-system transformations.
• Experience in regulated environments (financial services, fintech, wealth management, philanthropy, or adjacent).
• Demonstrated success leading cloud-native, API-first modernization programs.
• Experience operating within or enabling product-led delivery models.

Technical Depth

The ideal candidate will have hands-on familiarity (not necessarily day-to-day coding) with:

• Cloud platforms (Azure preferred; AWS strongly valued)
• API-first and event-driven architectures
• Integration platforms (e.g., Mulesoft or equivalent)
• Modern frontend + backend patterns (microservices, containerization)
• CRM ecosystems (Salesforce Financial Services Cloud or equivalent)
• Data platforms (Snowflake, modern ELT stacks)
• DevSecOps, CI/CD, infrastructure-as-code
• Observability tooling (e.g., Datadog or similar)
• SOC 2 and cloud security control frameworks

Leadership Characteristics

• Executive presence; comfortable engaging C-level stakeholders.
• Structured decision-maker who thrives in ambiguity.
• Balances pragmatism with long-term architectural thinking.
• Able to influence without authority across pods and vendors.
• Transparent, low-ego, collaborative.
• Comfortable managing tension between speed and risk.

What Success Looks Like (12–24 Months)

• GivingPoint successfully migrated with architectural integrity and compliance continuity.
• New portal and CRM initiatives launched without creating new technical debt silos.
• Integration backbone clearly defined, reusable, and owned.
• Data, CRM, and portal domains operate with clear boundaries and alignment.
• Client teams demonstrate growing architectural independence.
• Executive stakeholders express confidence in architectural direction and risk posture.

Scope & Time Commitment

• Dedicated to client engagement.
• Embedded in weekly governance forums.
• Active participant in quarterly roadmap and prioritization planning.
• Available for executive escalations and major decision checkpoints.