We are looking for a Client Infrastructure Architect to take technical ownership of Quanloop’s client-facing production infrastructure architecture.

This is not a people management role. It is a senior technical role for someone who can act as the architecture authority for Client Infrastructure, work closely with DevOps, SRE, infrastructure, and engineering colleagues, and bring structure to production infrastructure decisions.

The focus is on infrastructure that supports Quanloop’s client services and production systems. This is not an enterprise IT role, and it is not about workplace infrastructure, laptops, office networks, helpdesk, endpoint support, or internal business applications.

DORA is mandatory for this role. Infrastructure architecture must support operational resilience, incident follow-up, change discipline, evidence, documentation, and practical control in a regulated environment.

You will work with the CTO and technical teams to make infrastructure decisions more consistent, easier to review, easier to operate, and easier to evidence when required.

Operational support: occasional on-call or after-hours support may be required where production infrastructure issues need senior technical follow-up.

What you’ll be responsible for

• Own architecture decisions around Kubernetes and similar platform technologies, including container orchestration, service runtime environments, ingress, scaling, deployment patterns, and production operations.
• Define infrastructure architecture standards, patterns, and technical principles for the Client Infrastructure team.
• Guide DevOps, SRE, infrastructure, and engineering colleagues on infrastructure design, implementation trade-offs, production readiness, and operational risk.
• Review architecture decisions for environments, runtime platforms, deployment flows, observability, alerting, access control, backup, recovery, and operational tooling.
• Make sure infrastructure decisions support DORA-related operational resilience requirements, including documented processes, incident learning, resilience testing, continuity, and control evidence where relevant.
• Work with Engineering, Risk, Compliance, Security, and Operations where infrastructure architecture affects client services, regulatory obligations, or production stability.
• Reduce fragile manual work, hidden dependencies, unclear ownership, and infrastructure decisions that are difficult to operate or audit.
• Strengthen architecture documentation, decision records, diagrams, runbooks, and technical standards so teams can work from shared context.
• Support incident reviews and make sure root causes lead to practical infrastructure improvements, not only short-term fixes.
• Evaluate infrastructure tools and approaches with a focus on operational value, security, resilience, maintainability, and cost.
• Act as the senior technical reference point for client infrastructure architecture without becoming a line manager.

What success looks like in the first 3-6 months

• The current client infrastructure architecture is clearly mapped, including key dependencies, risks, ownership gaps, and improvement priorities.
• DevOps, SRE, and engineering teams have clearer standards for production infrastructure decisions.
• DORA-related infrastructure expectations are reflected better in architecture documentation, resilience planning, incident follow-up, and operational evidence.
• Production infrastructure decisions become more consistent, easier to review, and easier to support.
• Weak points in observability, deployment architecture, access control, backup, recovery, or operational readiness are identified and prioritised.
• Collaboration between Engineering, Infrastructure, Risk, Compliance, and Security improves around production readiness and resilience.

What we’re looking for

• Proven experience designing and improving production infrastructure for client-facing, business-critical, or regulated systems.
• Deep practical knowledge of DevOps, SRE, reliability engineering, infrastructure operations, and deployment architecture.
• Strong hands-on production experience with Kubernetes is required. You should understand cluster architecture, networking, ingress, scaling, deployment patterns, observability, security controls, and operational failure modes.
• Strong understanding of operational resilience requirements, with mandatory experience or strong working knowledge of DORA in a technology or infrastructure context.
• Experience with infrastructure as code, automation, CI/CD, environment design, and production change discipline.
• Strong knowledge of Linux-based production environments and modern cloud or platform infrastructure.
• Experience with monitoring, logging, tracing, alerting, incident response, and operational readiness.
• Good understanding of infrastructure security controls, including access management, secrets, network boundaries, auditability, backup, recovery, and change control.
• Ability to make architecture decisions that balance reliability, security, compliance, delivery speed, cost, and operational complexity.
• Ability to guide senior technical discussions, challenge weak designs, and explain trade-offs clearly.
• Clear written and spoken communication in English, including the ability to document architecture decisions and operational standards in practical language.
• Comfortable working on site as part of an office-first team.

What this role is not

• It is not a people management role.
• It is not an enterprise infrastructure role.
• It is not focused on laptops, office networks, endpoint support, helpdesk, or corporate IT systems.
• It is not a hands-off architecture role where diagrams are created and handed over to others.
• It is not a role for someone who wants to stay away from production details.

Before you apply

If you want more context before applying, the pages below may be useful:

• Benefits and rewards — details on health cover, time off, learning support and role-dependent bonus arrangements
• Our offices — information on our office-first model and locations
• Teams at Quanloop — an overview of how teams work and where this role sits
• Our story — background on the company and the way we work

This is optional reading, but it should give you a better sense of what to expect before you apply.

How to apply

Apply with your CV. A short note is welcome, but not required.