Professional Services Engineer at Seqera

Seqera builds the modern biotech stack. Nextflow orchestrates the pipelines, Seqera Platform runs and governs them at scale, and a growing set of AI tools speeds up the work around them. Tens of thousands of bioinformaticians already build on Nextflow, and the world's leading pharma and biotech teams run production science on the Platform.

You will join Professional Services, the team that owns a client's path from first deployment to running science in production. You will onboard clients to Seqera Platform (Cloud and Enterprise), and make things work within each client's own security and compliance posture.

You are a technical generalist with areas of specialization. You will deploy cloud infrastructure, build the tools that make it repeatable, and sit across the table from a client to work out what they actually need. One week you are deep in a client's network and certificate setup, the next you are automating a deployment or drawing a real requirement out of a half-formed one. If that range sounds energizing rather than daunting, the role fits: every part of it is core, and we will expect you to work across all of it and keep sharpening the areas you know least.

What the job is really like

We sit at the front line of client delivery. No team spends more time inside real client implementations, so we are first to learn what production actually demands. You take what Engineering ships and make it land cleanly in environments richer and more constrained than any lab. You also leave it easier to deploy for the next client.

On calls, you are the steady technical presence in the room. Clients are intelligent and deeply engaged, but much of a Seqera deployment sits outside their specialty, and they look to you. You answer most questions from a strong base of knowledge and handle the rest with composure. When you need to verify something, you say so plainly and then follow through, so everything we tell a client holds up.

You will work with a wide range of people: scientists and bioinformaticians who prototype fast in the open, client engineers picking up infrastructure alongside their research, and seasoned IT and DevOps teams. You help carry fast-moving ideas into robust, production-ready implementations. You meet each audience at their level, make hard topics approachable, and explain the reasoning behind a recommendation, not just the recommendation itself.

What You'll Do

• Technical onboarding - Lead client implementations across cloud, hybrid, and on-prem environments, from requirements to a working Seqera Platform deployment.

• Infrastructure deployment - Stand up the environment the Platform runs in and the compute it dispatches to, including networking, DNS, TLS, private CAs, IAM and secrets, container runtimes, and the storage that pipelines depend on.

• Working within client constraints - Deliver whether you have full account access or almost none, guiding the client's own IT through each change while respecting their security and compliance posture.

• Tooling and automation - Build the tools that make deployment repeatable and safe for non-experts. Give them pre-flight checks, clear failures, tests, and documentation so they keep working long after handover.

• Pre-sales and proof of concept - Partner with Sales and Scientific Development to shape solutions and run proof-of-concept deployments.

• Escalation and pattern-spotting - Act as a senior escalation point, turning recurring client problems into lasting fixes alongside internal teams.

About You

• Cloud depth. You are already strong in at least one of AWS, Azure, or GCP. Multi-cloud expertise is a real advantage. Exposure to HPC schedulers such as SLURM or Grid Engine is welcome.

• Networking and security. You are confident across networking, TLS and certificate management (public and private), IAM, and access control. You have the judgment to work within a client's security and compliance constraints, and you can explain any of it to a non-expert.

• Infrastructure as Code. Terraform is a must. Familiarity with other IaC (CloudFormation, Pulumi, Ansible) is a bonus.

• Containerization. Docker and Kubernetes are expected. Helm is a strong plus.

• Building, not just scripting. You have built and shipped tools that other people depend on, structured and commented for readers who are not you. You are comfortable in Python and Bash. You treat tests, scanning, and documentation as part of shipping.

• Workflow fluency. You understand how a workflow engine runs against remote compute, storage, and container runtimes.

• Client-facing instinct. You can run technical onboarding and pre-sales, elicit real requirements, navigate ambiguity, and stay credible with both scientists and DevOps engineers.

• Self-sufficient, and a natural sharer. You research your own way out of unfamiliar problems, and you take real satisfaction in explaining what you have learned so the whole team levels up.

• Grit in the face of adversity. When things are difficult you are motivated to work harder, dig deeper, and find the right answer, not the easy one.

• Bringing people together. When there is disagreement on the approach, you look past the surface-level differences to find the shared goal underneath, and shape a path forward that everyone can stand behind.

Nice to Have

• Life sciences, bioinformatics, or scientific computing background.

• Technical pre-sales experience.

• Nextflow experience.

• Startup experience.

How We Use AI

AI is woven through how Seqera operates. Software, infrastructure, testing, and documentation all move faster because we put strong AI tooling in the hands of skilled people, and you will have multiple vendors and models to draw on. This is a deliberately AI-forward environment, and doing well here means bringing real fluency with these tools and the judgment to direct them.

The Professional Services team is firmly pro-AI, and equally firm that a person owns the outcome. An agent can draft Terraform, scripts, runbooks, and diagrams in moments, and we make good use of that. The part that matters is what you do next: you review it critically, picture how a less technical consumer will read and run it, adjust it so it holds up in their hands, and support it after release. We treat the people who consume our work as first-class, and we value the judgment to get that right over the speed of a first draft.