Seqera - Senior Software Engineer

• Build and own the integration between Seqera Intelligent Compute and the Seqera Platform. • Own Platform compute environments: let customers set up and run compute across AWS, Azure and GCP, Kubernetes, HPC schedulers, and GPU-enabled executions - and handle the ways those backends differ. • Build against cloud provider APIs and SDKs, and handle what the real world returns: partial failures, quota and permission errors, provider quirks that leak into the product. • Own the billing and pay-as-you-go path - metering usage accurately, keeping usage events and invoices reconcilable, and making the free-user onboarding journey work. • Design data models and APIs that stay consistent across services and releases. • Make failures legible: turn raw provider and scheduler errors into something a user can act on, and add the tests and observability that make the next incident faster to diagnose. • Work directly with the Platform and product teams, and with support on escalations from real customers. • Take design decisions within your scope and document the system so it is not dependent on any one person. • 4+ years building and operating production backend services, with real ownership of at least one. • Strong in Java and/or Groovy, with Micronaut, Spring Boot or similar. • Real hands-on experience with a major cloud provider's API - provisioning and managing resources programmatically, not just deploying to it. • Have worked with Kubernetes as somewhere workloads actually run. • You care about correctness. Ideally you have worked on billing, metering or other systems where wrong data has consequences - and if not, you bring the same rigour to data integrity anyway. • Comfortable designing REST APIs and data models, and keeping integrations working across versions and failures. • Have been accountable for something customer-facing in production. • Comfortable inheriting a system, asking questions, and writing down what was never documented. • Comfortable with ambiguity - you develop hypotheses with limited information, drive work independently, and reach out early to stay unblocked. • We use AI every day and expect engineers to use it extensively. You do not need to be an expert, but you must be genuinely open to it.