Head of Platform Engineering

• We are seeking a leader for our Platform Infrastructure team. This role owns infrastructure at Seqera in both directions: the internal platform our engineers build on, and the infrastructure we ship to customers
• A large share of our customers experience Seqera through the infrastructure your team produces, which means much of this work is a product surface held to a product’s quality bar
• You will lead a team of DevOps and security engineers, and you will be a key member in our architecture review process, where infrastructure, security, and operability are weighed at design time alongside every other significant technical decision
• You will report to the CTO
• Own the reliability, security, and cost-effectiveness of our cloud infrastructure, and the ongoing health of the platform - what gets maintained, upgraded, and retired, not only what gets built
• Lead the technical launch of our dedicated single-tenant hosting offering: tenancy and isolation model, provisioning, upgrade and patching strategy across many customer instances, operational tooling, and the per-tenant cost model it will be priced against
• Own our Helm charts and Terraform provider as products - versioned, documented, and tested against supported deployment topologies, with the compatibility obligations that customer-deployed infrastructure carries
• Own CI/CD, infrastructure-as-code, and the supported path from empty repo to production, so that teams get pipelines, deployment standards, and observability defaults without assembling them each time
• Make cloud cost an engineering discipline: attribution by team and by tenant, anomaly alerting, an efficiency backlog with quantified savings, and cost as an input at design time rather than a surprise after the fact
• Lead our security posture in practice - security architecture applied during design review, and the security story we present to enterprise and life-sciences customers
• Own our formal incident response: severity definitions, an incident commander rotation, runbooks for our top failure modes, and blameless postmortems that change something
• Define what production-ready means at Seqera - tests, observability, documentation, runbooks - and hold the bar consistently across teams
• Grow and develop the Platform Infrastructure team, including active hiring at the senior engineer level and active mentorship and career planning for the whole team
• Partner with engineering, product, and customer-facing teams to bring infrastructure expertise into decisions early

Benefits

• Continuous Learning: We believe in empowering our people to expand their knowledge and be their best selves. That’s why you have a budget dedicated to being a life-long learner.
• Make yourself at home: Whether in our office in Barcelona or from home, we want you to make yourself comfortable to reach your full potential.
• Healthcare: We take care of your health and offer comprehensive packages for all our employees, no matter where they are located.
• Take ownership: Use your initiative to work on new ideas and pursue them. Receive support and encouragement in doing so with maximum freedom.
• Team events: We gather have weekly team lunches, bi-weekly social events, annual department offsites and annual company-wide retreats.
• Employee ownership: We value employee ownership and actively support everyone to participate in our overall long-term success.- You have real security depth. You can lead a security architecture conversation rather than coordinate one
• You have deep Kubernetes, Helm, and Terraform experience in enterprise settings, and strong opinions about infrastructure-as-code earned from operating it
• You have led infrastructure, platform, or SRE teams with direct accountability for production reliability, and you are still close enough to the work to review it, set the standard, and make architectural calls yourself
• You have built incident response rather than just carried the pager, and you have handled complex incidents including those involving customer infrastructure
• You treat cloud cost as an engineering responsibility, and you can build cost models that stand up to commercial scrutiny
• You write things down. We are moving deliberately from knowledge held by individuals to standards that are explicit, teachable, and enforceable
• You have shipped infrastructure that customers deploy and run themselves. You know that charts and modules used by people you will never meet is a different discipline from internal IaC - versioning, backward compatibility, upgrade paths, and support all become your problem
• You are comfortable as a technical peer with senior engineers who will challenge you, and equally comfortable presenting to leadership and customers
• You are comfortable with ambiguity, and you would rather define a platform than operate one that already exists
• His is a leadership role for someone who wants to define how a growing engineering organization builds, ships, and operates
• Experience with single-tenant, dedicated, or customer-isolated deployment models - fleet provisioning, upgrade orchestration across many instances, isolation guarantees
• Developer productivity or internal developer platform experience
• Scientific, research, or high-performance computing environments; large-scale batch and data-intensive workloads
• Experience with multiple cloud providers
• Release engineering experience
• Familiarity with compliance frameworks relevant to enterprise life-sciences customers
• Open-source community exposure - much of what we build is used in the open