1

Golang Temporal Jobs (NOW HIRING)

Temporal Architect

Monroe, LA · On-site

$60.50 - $79.75/hr

Java, Golang, TypeScript, Python, C#, or PHP. · Experience guiding teams through application fitment, architecture evaluation, and implementation considerations for Temporal platform adoption. · ...

New

Sr. Software Engineer - Golang

New York, NY · Remote

$125K - $165K/yr

Position: Sr. Software Engineer - Golang 100% Remote 6 month + Contract NOTES: * 5-7 yrs relevant ... Leverage Temporal for orchestrating distributed workflows and building robust automation solutions.

next page

Showing results 1-20

Golang Temporal information

See salary details

$64K

$139.8K

$190.5K

How much do golang temporal jobs pay per year?

As of Aug 6, 2026, the average yearly pay for golang temporal in the United States is $139,839.00, according to ZipRecruiter salary data. Most workers in this role earn between $120,500.00 and $156,500.00 per year, depending on experience, location, and employer.

What is the difference between Golang Temporal vs Golang Developer?

AspectGolang TemporalGolang Developer
Primary FocusWorkflow orchestration and microservices coordination using TemporalWriting, testing, and maintaining Go programming language code
Required SkillsKnowledge of Temporal SDK, distributed systems, and GoProficiency in Go, algorithms, and software development best practices
Work EnvironmentCloud-based, microservices architecture, often in DevOps teamsVaried environments including startups, enterprises, and open-source projects
Industry UsageTech companies implementing complex workflows and automationSoftware development across multiple industries

Golang Temporal specialists focus on implementing workflow orchestration with Temporal, while Golang Developers write general Go code for various applications. Both roles require Go expertise, but Temporal roles emphasize distributed systems and workflow management.

What is a Golang Temporal developer?

Golang Temporal developers are software engineers who specialize in building reliable, scalable, and distributed applications using the Temporal workflow orchestration platform and the Go programming language. They design workflows, manage state, handle retries, and ensure fault tolerance in complex systems. These developers leverage Temporal's capabilities to create robust backend services that require long-running or asynchronous tasks, such as payment processing, data pipelines, and microservices orchestration.

How does a Golang developer working with Temporal typically collaborate with other teams during a project?

As a Golang developer utilizing Temporal, you will frequently collaborate with DevOps, QA, and product teams to design, implement, and maintain robust workflow orchestration solutions. You'll work closely with backend engineers to define workflow requirements and troubleshoot issues, while also partnering with DevOps to ensure reliable deployment and monitoring of Temporal services. Regular communication with product managers and QA helps align workflow logic with business goals and ensures high-quality releases. This collaborative environment fosters knowledge sharing and often leads to opportunities for cross-functional skill development.

What are the key skills and qualifications needed to thrive as a Golang Temporal developer?

To excel as a Golang Temporal Developer, you need strong proficiency in Go programming, experience with workflow orchestration concepts, and a solid understanding of distributed systems. Familiarity with Temporal's SDK, cloud platforms (like AWS or GCP), and related CI/CD tools is typically required. Strong problem-solving, collaboration, and communication skills help in designing scalable workflows and working effectively with cross-functional teams. These competencies ensure robust, maintainable workflow solutions that drive reliability and efficiency in complex software environments.
More about Golang Temporal jobs
What cities are hiring for Golang Temporal jobs? Cities with the most Golang Temporal job openings:
What states have the most Golang Temporal jobs? States with the most job openings for Golang Temporal jobs include:
Infographic showing various Golang Temporal job openings in the United States as of August 2026, with employment types broken down into 91% Full Time, 1% Part Time, and 8% Contract. Highlights an 75% Physical, 5% Hybrid, and 20% Remote job distribution, with an average salary of $139,839 per year, or $67.2 per hour.

$60.50 - $79.75/hr

Other

This job post has expired 1 day ago. Applications are no longer accepted.


Job description

Temporal Architect
Role Descriptions: Temporal Architect
Essential Skills: Temporal Architect
Skills: Oracle E-Business Suite (EBS) Developer - Technical
Experience Required: 4-6 Years
Temporal Architect / Solutions Architect
Required Information Details
1 Role Temporal Architect / Solutions Architect
2 Required Technical Skill Set Temporal.io, distributed systems architecture, cloud-native application design, Java/Golang/TypeScript/Python/C#/PHP, APIs, reliability/observability, security, performance, and production operations
3 No of Requirements 1
4 Desired Experience Range 10+ years overall application/platform architecture experience; 5+ years in distributed systems, workflow orchestration, cloud-native platforms, or Temporal-aligned architecture
Desired Competencies (Technical / Behavioral Competency)
Must-Have · Strong architecture experience in Temporal.io / workflow orchestration, including workflow design, activity design, task queues, workers, retries, timeouts, schedules, signals, queries, and versioning patterns. · Deep understanding of distributed system technologies, design principles, and best practices, including resilient microservices, event-driven architecture, failure handling, idempotency, consistency, and long-running transactions. · Hands-on ability to build prototypes and provide design, development, build, and deployment guidance using one or more Temporal-supported languages: Java, Golang, TypeScript, Python, C#, or PHP. · Experience guiding teams through application fitment, architecture evaluation, and implementation considerations for Temporal platform adoption. · Strong knowledge of production readiness: reliability, security, performance, cost management, operations, scaling, release management, and runbook/operational support models. · Cloud experience with at least one major provider and familiarity with commonly used application-development and production services. · Ability to position Temporal against alternative technologies and architectural patterns, and explain technical benefits and limitations clearly to customer engineering and architecture teams. · Experience with API/service integration, REST/gRPC, message/event platforms, CI/CD, containerization, Kubernetes, observability, monitoring, alerting, and logging practices. · Ability to conduct architecture workshops, whiteboarding sessions, code/design reviews, and technical risk assessments for enterprise migration or modernization programs. · Excellent technical communication skills, including presenting, whiteboarding, writing solution notes, and engaging engineering leaders and key technical decision-makers.
Good-to-Have · Experience in legacy BPMS / workflow platform modernization and migration programs, including BPMN/XPDL/XML-driven assessment or transformation approaches. · Exposure to Pega, Appian, IBM BPM/Savvion, Camunda, or similar workflow/BPM platforms and ability to map existing process patterns to Temporal-based implementations. · Experience supporting presales, proposal defense, demo/POC execution, estimation, solution shaping, and account planning with sales/account teams. · Client-facing consulting experience with onsite-offshore coordination, stakeholder management, and enterprise architecture governance. · Knowledge of domain-driven design, saga/compensation patterns, platform engineering, developer enablement, and reusable architecture assets/accelerators.
Desired Competencies (Technical / Behavioral Competency) · Ability to collaborate with developers, business analysts, QA, DevOps/SRE, platform teams, enterprise architects, and customer leadership. · Positive attitude, strong ownership, team orientation, and ability to quickly adapt to new technologies and ambiguous engagement models.
Background Engineering Graduate/Post-Graduate in any discipline (Computer Science preferred) or MCA with strong background in software development, distributed systems, cloud architecture, and technical consulting.
Others Temporal certification / training exposure, open-source contribution, cloud certification, or hands-on Temporal Cloud experience will be an added advantage.
Responsibility / Expectations from the Role
1 Assess customer applications/processes and determine fitment for Temporal platform adoption, modernization, or migration.
2 Own end-to-end Temporal architecture definition, including workflow/activity model, worker topology, task queues, integration patterns, resiliency, and operational guardrails.
3 Educate customer and internal engineering teams on the technical benefits, limitations, and implementation considerations of Temporal and Temporal Cloud.
4 Build prototypes/POCs and provide design, development, build, deployment, and code-review guidance using supported Temporal SDK languages.
5 Define production readiness approach covering reliability, observability, security, performance, scaling, cost, operations, incident handling, and release/versioning practices.
6 Support proposal solutioning, estimation, technical risk analysis, migration planning, and defense workshops for legacy BPMS-to-Temporal opportunities.
7 Partner with account/sales, delivery, enterprise architecture, DevOps/SRE, QA, and platform teams to develop adoption roadmaps and execute implementation plans.
8 Create reusable reference architectures, accelerators, implementation standards, enablement material, and knowledge repositories for Temporal delivery teams.
9 Work with stakeholders to identify adoption blockers, resolve complex technical issues, and guide teams toward stable production usage.
10 Provide strong stakeholder communication through presentations, whiteboarding, architecture documents, status updates, and executive-ready solution summaries.