Senior Architect - Email & Collaboration Security

Responsibilities

• Lead from Problem Space, Not Solution Space
• Own Integration Contracts as Product Artefacts
• Build the Architectural Context Engineering Teams Operate Inside
• ADRs, service interaction patterns, NFR targets, and data contracts are not documentation - they are the substrate that lets engineering teams and AI-assisted development workflows make consistent decisions at scale. The artefacts produced in this role are clear, reasoned, and durable.
• Govern Without Blocking
• Reason About Cost and Unit Economics
• Infrastructure choices are sized, cost trajectories modelled for new architecture work, and unexpected spend is flagged with a proposed remediation. The frame is cost per outcome - per protected mailbox, per remediated incident - not just monthly AWS spend.
• Communicate at Every Altitude

Requirements

• Breadth Over Depth - and Knowing the Difference
• 10+ years building and operating production SaaS systems, with at least 3 years in a Solutions Architect, Principal Engineer, or equivalent role carrying product-shaping responsibility
• A genuinely broad architectural lens - thinking about system shape, data flows, and organisational constraints rather than reaching for the nearest deep technical rabbit hole
• Comfort operating across cloud-native patterns (AWS, Kafka, managed services, distributed event architectu

Additional Information

Senior Solutions Architect - Email & Collaboration Security - London UK Why This Role Exists The Email & Collaboration Security (ECS) product line sits at the intersection of some of the most consequential challenges in enterprise security today: AI-augmented threats, sprawling collaboration surfaces, multi-cloud delivery complexity, and the expectation that detection and response capabilities keep pace with a threat landscape that does not wait. This architecture is not greenfield. It carries two decades of accumulated product decisions, integration contracts, and operational constraints. The right candidate understands why that history matters before proposing how to move beyond it. Reasoning about legacy shape and evolutionary trajectory simultaneously is not optional; it is the job. The successful candidate will serve as connective tissue across product management, engineering, and the broader Architecture Leadership Team - turning customer and business problems into coherent, deliverable technical direction, and owning the decisions that give ECS engineering teams a stable foundation to move fast with quality. AI-First Ways of Working Mimecast is an AI-first engineering organisation. This is not a cultural aspiration - it is an operating expectation. The person in this role is expected to use AI tools as a genuine, daily part of how they work: for design exploration and iteration, documentation, analysis, prototyping, and research synthesis. This means having a real, practised opinion on where AI tooling accelerates quality decisions and where it introduces risk. It also means designing systems that incorporate AI components thoughtfully: understanding the implications of LLM integration, agent boundaries, prompt and data-contract stability, and evaluation coverage for AI-driven features. Candidates who treat AI tooling as optional or experimental are not the right fit for this role. The expectation is fluency and daily practice, not passing familiarity. The ECS Domain ECS covers the following product and capability areas: Email threat detection and prevention Email security efficacy Collaboration security DMARC analyzer Data platform and observability Analysis and Response End user application integration Internal operations enablement

Your Match

How well this role fits your profile.

Company Intel

What employees say

Worked at mimecast? Share your experience