ZipRecruiter

Log In

1

Temporal Software Engineer Jobs in Toronto, ON (NOW HIRING)

Roadpost

Senior Software Engineer

Toronto, ON · On-site

As a Senior Software Engineer, you'll lead technically significant initiatives across the stack ... ECS, S3, and Temporal. You'll also shape the PostgreSQL schemas and queries behind them ...

Autodesk

Senior Software Developer

Toronto, ON · On-site

CA$107K - CA$157K/yr

In this role, you will build a multi-tenant durable workflow engine on top of Temporal IO that lets ... Understand and curiosity of SRE best practices, architectures, and methods * Good knowledge on ...

Paytm

Senior AI Engineer

Toronto, ON · On-site

What you'll bring * 5+ years in software engineering, with 3+ in AI systems or LLM applications ... Workflow orchestration (Temporal, Airflow, Prefect) for AI workloads; voice / multimodal / edge ...

Waabi

Research Engineer, World Models

Toronto, ON · On-site +1

CA$155K - CA$269K/yr

This role focuses on large-scale world models for temporal reasoning and generation, including ... Qualifications: - Strong software engineering and implementation: You have very strong Python ...

Td

Senior Java Developer, TD Securities

Toronto, ON · On-site

CA$102K - CA$125K/yr

Working knowledge of building Java services * 6+ years of experience as a software engineer working ... Experience working on big data sets with bi-temporal support * Working knowledge on middleware ...

next page

Showing results 1-20

All JobsTemporal Software Engineer JobsTemporal Software Engineer Jobs in Toronto, ON

Temporal Software Engineer information

What is a Temporal Software Engineer?

A Temporal Software Engineer is a developer who specializes in building, maintaining, and optimizing applications using the Temporal open-source workflow orchestration platform. Temporal enables engineers to manage complex, long-running, and distributed workflows in a reliable and scalable way. Temporal Software Engineers typically design workflows, implement fault-tolerant logic, and help teams automate business processes that require reliability and durability. Their expertise ensures that workflows can recover from failures, maintain state, and handle retries without losing data or process integrity.

What are the key skills and qualifications needed to thrive as a Temporal Software Engineer, and why are they important?

To thrive as a Temporal Software Engineer, you need strong software engineering fundamentals, proficiency in distributed systems concepts, and experience with languages like Go, Java, or TypeScript. Familiarity with Temporal's workflow orchestration platform, cloud infrastructure tools, and CI/CD systems is typically expected. Excellent problem-solving, collaboration, and communication skills help in designing resilient workflows and working with cross-functional teams. These skills are crucial for building reliable, scalable solutions that leverage Temporal for complex business processes.

What are some common challenges faced by Temporal Software Engineers when designing workflows, and how can they be addressed?

Temporal Software Engineers often encounter challenges such as managing complex workflow dependencies, handling failure recovery, and ensuring workflow scalability. These challenges can be addressed by leveraging Temporal’s robust retry mechanisms, designing idempotent activities, and breaking workflows into smaller, reusable components. Collaboration with DevOps and QA teams is also crucial to ensure workflows are resilient and thoroughly tested in distributed environments.

What is the difference between Temporal Software Engineer vs Cloud Software Engineer?

AspectTemporal Software EngineerCloud Software Engineer
Required CredentialsBachelor's in CS or related, experience with Temporal SDKsBachelor's in CS or related, cloud platform certifications (AWS, Azure)
Work EnvironmentDeveloping distributed, event-driven applications using TemporalDesigning and deploying cloud-based solutions across platforms
Industry UsageTech companies implementing workflow orchestrationBroad industry use, including SaaS, enterprise, and startups
Search & Comparison IntentFocus on Temporal-specific skills and workflowsBroader cloud infrastructure and deployment skills

In summary, a Temporal Software Engineer specializes in building and maintaining workflow orchestration using Temporal, while a Cloud Software Engineer works on deploying and managing cloud-based applications across various platforms. Both roles require strong programming skills, but their focus areas differ significantly.

How much does a Temporal Software Engineer make?

A Temporal Software Engineer's salary typically ranges from $100,000 to $160,000 annually, depending on experience, location, and company size. Skilled engineers with expertise in distributed systems and workflow orchestration tools like Temporal are often compensated at the higher end of this range.

What are popular job titles related to Temporal Software Engineer jobs in Toronto, ON?

For Temporal Software Engineer jobs in Toronto, ON, the most frequently searched job titles are:

What job categories do people searching Temporal Software Engineer jobs in Toronto, ON look for?

The top searched job categories for Temporal Software Engineer jobs in Toronto, ON are:

Temporal Software Engineer jobs near you
Infographic showing various Temporal Software Engineer job openings in Toronto, ON as of August 2026, with employment types broken down into 1% As Needed, 87% Full Time, 8% Part Time, and 4% Contract. Highlights an 85% Physical, 6% Hybrid, and 9% Remote job distribution.

Senior Software Engineer

Toronto, ON • On-site

ZoomInfo Technologies LLC
Software Development • 1 - 5K employees

8.9

Company rating: 8.9 out of 10

Based on 8 frontline employees who took The Breakroom Quiz

39th of 246 rated software companies

Good employer

Respectful managers

Learn new skills

Learn more about ZoomInfo Technologies LLCexternal

Full-time

Re-posted 23 days ago

Job description

What You'll do:

  • Own a production GitOps deployment API and CLI (TypeScript/Node, NestJS) that a large share of our services depend on to ship-operating it reliably, evolving its capabilities, and being the engineer teams turn to when a deploy doesn't go as planned.
  • Maintain and extend self-service deployment tooling built on ArgoCD ApplicationSets and Helm that rolls services out to GCP Cloud Run, including its manifest schema, chart, and ApplicationSet integration.
  • Own a shared internal TypeScript package ecosystem (an Nx monorepo) consumed across dozens of services, plus the application ingress / edge-routing layer and its Helm charts-keeping consumers unblocked and the contracts stable.
  • Build high-performance internal tools and APIs in Go (Golang) to manage infrastructure metadata and lifecycle.
  • Design complex, long-running workflows using durable execution frameworks (like Temporal) to orchestrate tasks across Git, cloud providers, and CI/CD pipelines.
  • Develop and implement Model Context Protocol (MCP) servers and Agentic AI workflows to automate the creation, upgrading, and auditing of infrastructure configurations.

What you bring:

  • 8+ years of software engineering experience, or equivalent, including building and operating infrastructure, platform, or delivery systems that other teams depend on.
  • Strong experience in at least one of the following:
    • Delivery / GitOps tooling - ArgoCD (ideally ApplicationSets), Helm, GitHub Actions, and the GitOps model of declarative, Git-driven deployment
    • Backend services & shared libraries at scale-building APIs and reusable packages that many other services consume
  • Proficiency in Go or TypeScript/JavaScript, with hands-on experience in-or a genuine willingness to ramp quickly on-the other. The delivery systems you'll inherit are TypeScript/Node (NestJS, in an Nx monorepo); our automation platform core is Go. We'll support you getting strong in your second language.
  • A demonstrable understanding of software architecture, design patterns, and building scalable RESTful APIs.
  • Experience with Kubernetes (K8s), serverless runtimes (GCP Cloud Run or equivalent), and major cloud providers (GCP and AWS).
  • Comfort inheriting an unfamiliar, production-critical system from a transitioning team-prioritizing, asking the right questions before the original owners leave, documenting as you go, and stabilizing before reshaping.

Bonus Point:

  • Experience operating a deployment platform that other teams depend on.
  • Experience with Temporal (or similar workflow engines like Cadence or Airflow) for stateful distributed systems.
  • Proficiency with Terraform, including modular, reusable modules.
  • Practical experience with Agentic AI, MCP (Model Context Protocol), or A2A (Agent-to-Agent) frameworks.

#LI-RA1

What ZoomInfo employees say

Pay

Benefits

Hours and flexibility

Workplace

Get the full story on Breakroom

Apply