Senior Software Engineer - Orchestration & Execution

Senior Software Engineer – Orchestration & Job Execution (Cloud Platform)

Alteryx is looking for a Senior Software Engineer to join our cloud platform engineering team. In this role, you will design, build, operate, and evolve backend services that coordinate how work moves through Alteryx Cloud, focusing on orchestration, job execution, workflow runtime services, and reliable service‑to‑service coordination.

• Design and deliver backend services, APIs, workers, and shared libraries that power cloud platform capabilities.
• Build and improve systems for orchestrating work across services, including job submission, execution tracking, status propagation, retries, cancellation, results, and operational visibility.
• Develop reliable asynchronous and event‑driven systems using queues, messaging, background workers, and durable state.
• Work on distributed execution flows across platform services, including service‑to‑service communication, routing, acknowledgements, and failure recovery.
• Build and maintain cloud‑native runtime infrastructure using containers, Kubernetes, deployment automation, and related platform tooling.
• Integrate platform services with persistence layers, event streams, REST APIs, and internal service contracts.
• Improve production reliability through metrics, tracing, structured logging, health checks, dashboards, alerting, runbooks, and incident follow‑up.
• Lead technical design for ambiguous or cross‑service work, review code with a systems mindset, and mentor engineers on distributed‑system and production‑engineering practices.
• Collaborate with partner teams to turn product requirements into incremental, testable, and operable platform capabilities.
• Use AI and modern development tools to improve engineering productivity, code quality, and delivery speed.

• Core
  
  Experience:
  
  5+ years (minimum 4 years) of professional software development, with ownership of production backend services, cloud platform capabilities, or distributed systems.
• Backend Ecosystem: Strong experience building services with Type Script/Node.js, or core systems languages such as Go, Java, or Rust, with a willingness to code primarily in Node.js.
• Systems Engineering: Experience designing and operating asynchronous, queue‑driven, or event‑driven systems, including patterns such as retries, cancellation, idempotency, concurrency, ordering, timeouts, and failure handling.
• Integrations: Experience with durable persistence, service contracts, RESTful APIs, and integrations across multiple services or platform components.
• Cloud‑Native Infrastructure: Experience with production systems including containers, Kubernetes, service health, scaling behavior, and operational debugging.
• Production Practices: Strong ownership of testing, observability, structured logging, metrics, tracing, incident response, and continuous reliability improvement.
• Leadership Maturity: Ability to lead design discussions, communicate technical tradeoffs, mentor engineers, and drive cross‑team work through ambiguity with an ownership‑oriented mindset.
• Nice to Have
  
  Experience:
  
  
  • Workflow engines, orchestration systems, job runners, task execution platforms, or runtime infrastructure.
  • Kubernetes deployment patterns, Git Ops, multi‑cluster environments, cloud platform operations, or infrastructure automation.
  • Messaging systems, event contracts, schema management, asynchronous notification pipelines, or distributed service coordination.
  • Real‑time communication, long‑lived connections, service‑to‑service messaging, or coordination across unreliable networks.
  • Secure service‑to‑service authentication, token handling, secrets management, authorization boundaries, or customer‑scoped execution contexts.
  • Log collection, streaming, distributed workload observability, operational dashboards, or production support tooling.
• Bachelor’s degree in Computer Science, Engineering, or equivalent practical experience.

• Within 30‑60 days:
  Understand the cloud platform architecture, trace work across key services, and ship focused improvements with clear tests and operational awareness.
• Within 90+ days:
  Own senior‑level work streams across service…