Director, I&T Plasma Engineering

The Director, I&T Plasma Engineering leads engineering and owns architecture governance across all CSL Plasma digital product domains. This role is internally focused on how the organization builds. Defining and owning the engineering standards, practices, and technology platform strategy that all development teams, managed service providers, and external vendors are held to. This role is also responsible for governing Artificial Intelligence (AI) and Generative AI in production across CSL Plasma. This spans AI features inside donor-facing and operational products, AI-assisted software development inside the engineering team, and the operational discipline required to run AI reliably at scale.

The Director, I&T Plasma Engineering is distinct from product delivery coordination (owned by the Delivery Manager) and product strategy (owned by Sr. Directors and Product Owners). This role owns the technical foundation: the quality bar, the architectural patterns, the cross-cutting engineering capabilities, and the security and compliance posture that make reliable, scalable digital product delivery possible.

This is a technical leadership role. The Director stays close enough to the work to be credible with the engineers doing it, contributes personally where judgment is required, and delegates confidently everywhere else.

This position reports to: Senior Director, Plasma I&T Applications & Operations
Reporting to this position: Plasma Business Architect, AI/ML Product Engineer, Automation Engineer, Data Engineer, SRE/DevOps Engineer, UX Designers

Principal Accountabilities

1. Engineering Standards & Practices

·Own and define the 'how we build' standards across all five Plasma digital product domains: coding standards, testing standards, security standards (in formal matrix partnership with the CSL Cyber organization), DevOps and CI/CD practices, and architectural patterns.

·Set the technical quality bar that all internal delivery teams, managed service providers, and to which external vendors are contractually and operationally held.

·Enforce standards primarily through the shared engineering platform, automated quality gates, and review of significant technical designs. Architecture review boards are reserved for genuinely novel decisions, not routine sign-off.

·Reviews and approves significant technical designs personally, particularly those setting patterns others will follow.

2. Architecture Governance

·Set and enforce integration standards, data architecture, and cross-product technical decisions across the full Plasma digital ecosystem.

·Serve as the formal interface with the CSL Enterprise Architecture organization. Establish and maintain the cadence with the CSL Enterprise Architecture team, represent Plasma architecture upward, and bring enterprise decisions back to the Plasma team. Approve significant architectural decisions personally; delegate routine architecture work to domain technical leads with clear guardrails.

·Manage and develop the Plasma Business Architect, who executes day-to-day architecture work, alignment reviews, and architecture documentation.

·Owns the target-state architecture for the Data Backbone as an early priority given its role as the foundation for the AI, analytics, and operational data roadmap.

3. Cross-Domain Team Leadership

·Provide direct people leadership for cross-domain enabling functions: Plasma Business Architect, QA Lead, QA Automation Engineers, AI/ML Product Engineer, Automation Engineer, Data Engineer, SRE/DevOps Engineer, and UX Designers.

·Own hiring standards, role design, career development frameworks, and succession planning for the cross-domain engineering team.

·Set and hold a culture of technical excellence, accountability, psychological safety, and continuous learning across the engineering organization.

·Given the transformation of Plasma IT, personally interviews technical leads across the broader net-new hires, not only direct reports, to hold the hiring bar across the Plasma technology team.

4. Technology Platform Strategy

·Own the engineering tooling, platform, and capability roadmap — including the Data Backbone architecture, Middleware integration standards, cloud infrastructure direction, and the DevOps toolchain — in conjunction with enterprise capability owners.

·Ensure the technology platform evolves in step with the Plasma product roadmap, anticipating capability needs 12–24 months ahead.

·Evaluate build vs. buy vs. partner decisions for platform capabilities; provide technology investment recommendations to senior leadership.

·Owns the shared engineering platform that every Plasma product team builds on. This covers service templates, CI/CD pipelines, deployment patterns, observability, and security guardrails, delivered as a coherent product with a roadmap, an internal customer base across the domains, and adoption as the measure of success. …