1

Temporal Software Engineer Jobs in Minnesota (NOW HIRING)

... developer day‑to‑day Fluent English. Strong Advantage * Direct Temporal.io production ... software platform. Gain visibility by application type and have the power to white list ...

Engineer - IoT Platform

Minneapolis, MN · On-site

$75K - $135K/yr

You are passionate about the quality of software and balance between speed of delivering new ... Temporal, Camunda Core responsibilities of this job are described within this . Job duties may ...

Manages the technical, operational, and temporal details of each intervention in agreement and ... Troubleshooting software and electrical systems; Wiring 3 phase motors, 120vac power/communication ...

Manages the technical, operational, and temporal details of each intervention in agreement and ... Troubleshooting software and electrical systems; Wiring 3 phase motors, 120vac power/communication ...

Manages the technical, operational, and temporal details of each intervention in agreement and ... Troubleshooting software and electrical systems; Wiring 3 phase motors, 120vac power/communication ...

Manages the technical, operational, and temporal details of each intervention in agreement and ... Troubleshooting software and electrical systems; Wiring 3 phase motors, 120vac power/communication ...

Manages the technical, operational, and temporal details of each intervention in agreement and ... Troubleshooting software and electrical systems; Wiring 3 phase motors, 120vac power/communication ...

Manages the technical, operational, and temporal details of each intervention in agreement and ... Troubleshooting software and electrical systems; Wiring 3 phase motors, 120vac power/communication ...

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 Minnesota?

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

What job categories do people searching Temporal Software Engineer jobs in Minnesota look for?

The top searched job categories for Temporal Software Engineer jobs in Minnesota are:

What cities in Minnesota are hiring for Temporal Software Engineer jobs?

Cities in Minnesota with the most Temporal Software Engineer job openings:

Workflow & Provisioning Lead

Webbing

Finland, MN • On-site

$90 - $120/hr

Other

Posted 5 days ago


Job description

  • Deploy and configure Temporal/Camunda or similar Workflow Engine on Kubernetes (self-hosted, production-grade).
  • Design and implement SIM Activation workflow: activities for HSS, OCS, PCRF, Inventory update.
  • Implement SIM Deactivation workflow with compensation and rollback logic.
  • Implement Plan Change workflow (OCS quota update + PCRF policy change).
  • Define workflow versioning strategy (Temporal GetVersion API or similar) — foundational for long-term stability.
  • Lead another developer on development tasks and code reviews from week one.
  • Order-triggered workflows: Order DB → Temporal/similar signal handler.
  • Network trigger handling: location updates → workflow signals via Kong API Gateway.
  • Retry policies, dead-letter handling, and alerting per workflow type.
  • Temporal production cluster operations and HPA configuration.
  • nd-to-end integration testing, load testing, runbook authoring.
  • Post go-live hypercare and continuous improvement.
REQUIREMENTS
  • 4–6 years backend software development experience.
  • Required: Hands‑on experience with a workflow orchestration engine.
  • Temporal.io strongly preferred — production experience with workers, activities, signals, timers.
  • Camunda, Apache Airflow, or equivalent accepted if strong fundamentals.
  • Go or Java — must be comfortable building production services in at least one.
  • REST API design and implementation (designing APIs consumed by Kong API Gateway).
  • PostgreSQL — schema design, indexes, query optimisation for large datasets (10M+ rows).
  • BSS/OSS domain knowledge: provisioning flows, SIM lifecycle, telecom service activation.
  • Kubernetes — deploying and operating workloads on K8s (not just writing YAML).
  • Experience with event‑driven architectures using RabbitMQ, Kafka, or Redis Pub/Sub.
  • Experience designing for failure: retry policies, idempotency, compensation logic, DLQ.
  • Ability to lead a junior/mid developer day‑to‑day Fluent English.
Strong Advantage
  • Direct Temporal.io production experience (SDK, worker configuration, namespace management).
  • Diameter protocol (Ro/Gy/Gx) — even basic familiarity is valuable.
  • Experience with mock‑first development and contract testing.
  • Prometheus + Grafana — instrumenting and monitoring workflow engines.
Nice to Have
  • Experience at a telecom operator, MVNO, or telecom vendor (Ericsson, Nokia, Huawei, etc.).
  • Knowledge of eSIM / GSMA SGP.22 standard.
  • Python — for tooling, scripting, test automation.
ABOUT WEBBING

Founded in early 2010, Webbing is a global data MVNO that delivers enterprise grade, global connectivity and IoT services across more than 200 countries and 600+ mobile carriers' networks. Webbing's secured network delivers network protection and web content intelligence.

Enterprise customers can manage, monitor, and optimize data usage in real‑time with Webbing's powerful software platform. Gain visibility by application type and have the power to white list applications and limit non‑business applications with the click of a button, saving money and improving compliance.

WHAT WE OFFER
  • Fully remote
  • The opportunity for professional development within a reputable international innovative and growing company.
  • An exciting and challenging greenfield platform with great skill and knowledge development opportunities.
  • The opportunity to join a team of highly professional specialists in an international environment.
#J-18808-Ljbffr