Director of Engineering

Required Director of Engineering
So, whats the role all about?
The Director of Technology and Architecture owns the technical vision that holds this portfolio together. The mandate is to ensure that a wide-ranging set of products remains coherent, secure, scalable, and economical to build and operate regardless of where and how it is deployed. This is a hands-on leadership role at the intersection of deep technical authority and enterprise strategy: you will set architectural direction, resolve the hardest cross-cutting trade-offs, and raise the engineering bar across the organization.
This is the most senior individual-contributor-plus-leadership technical role in the company. You will be a trusted advisor to the executive team and the final technical authority on architecture decisions that span products.
How will you make an impact?
Architectural Vision & Strategy:
Define and own the multi-year target architecture across the entire product suite, balancing product autonomy with shared platform leverage.
Establish an architecture strategy so that products can be delivered on-premise, in private cloud, in public cloud, or as pure cloud SaaS.
Drive the platform and shared-services strategy (identity, data, integration, observability, deployment tooling) that reduces fragmentation across products.
Help architects translate business and product strategy into technical roadmaps; advise the executive team on build-vs-buy, modernization, and major technology bets.
Design abstractions and packaging models that let a single product run reliably across heterogeneous environments with differing scale, network, data residency, and operational constraints.
Establish reference architectures and patterns for tenancy, configuration management, release/upgrade cadence, and feature parity across on-premise and cloud-hosted deployments.
Security, Compliance & Resilience:
Embed security, privacy, and regulatory compliance into the architecture by design - addressing the standards relevant to financial services (e.g., data protection, auditability, segregation, encryption, and regional data residency).
Define non-functional requirements and architectural guardrails for availability, disaster recovery, transactional integrity, performance, and observability appropriate to mission-critical financial systems.
Partner with Security, Risk, and Compliance leadership to ensure the architecture withstands audit and regulatory scrutiny across jurisdictions.