Infrastructure Engineer (Temporal)

TEKsystems•Dallas, TX

4d•$50 - $70•Hybrid

About The Position

This is a platform engineer role focused on the open-source product Temporal, specifically Temporal Cloud, as a strategic offering. The individual will be a foundational member of the team, requiring hands-on operational experience with Temporal at scale. This role involves significant customer interaction, onboarding other development teams to the platform, and guiding them on best practices for using Temporal. The ideal candidate will possess strong communication and technical skills, with a requirement for hands-on experience administering or integrating the Temporal platform, not just building workflows against it. Experience is expected in cloud environments, Kubernetes/OpenShift, and integrating cloud services with identity providers. The role also includes some engagement on the workers' side internally.

Requirements

MUST HAVE TEMPORAL EXPERIENCE TO BE CONSIDERED
5+ years in platform engineering, SRE, or infrastructure engineering, with a track record of operating production distributed systems.
Deep, hands-on platform engineering experience across cloud, Kubernetes/OpenShift, or managed service environments.
Experience configuring enterprise SSO and integrating cloud services with identity providers, role mapping, service identities, and access controls.
Experience deploying and scaling containerized application runtimes on OpenShift or Kubernetes, including resource policies, autoscaling, networking, secrets, and GitOps promotion.
Strong understanding of distributed systems and durable data, including availability, consistency, backup and recovery, retention, and performance trade-offs.
Proficiency with Infrastructure as Code and GitOps (Terraform, Helm, ArgoCD or equivalent).
Production observability experience (Prometheus, Grafana, OpenTelemetry).
Comfort operating a service across internal and vendor-owned boundaries and defining clear operational responsibilities.
Excellent judgment on reliability, security, and irreversible design trade-offs; able to work independently as a founding team member.
Hands-on experience with Temporal (or a comparable durable-execution / workflow engine such as Cadence) — administering or integrating the platform, not just building workflows against it.
Experience running platforms as an internal shared service (multi-tenant, namespace isolation, developer enablement).
Proficiency in Go; familiarity with Temporal SDKs (Java, Go, TypeScript).
Cloud, enterprise networking, private connectivity, identity, and managed-service integration depth.
Experience establishing on-call practices and incident response for a new service.

Nice To Haves

Not self hosting, host it in your cloud– Temporal itself with integration with developer pipelines, not hands on infrastructure–
Containers, Kubernetes- eventing alerting, some scripting some development--
Some engagement on workers side – internally,

Responsibilities

Act as the face of the team, managing customer interactions.
Onboard other development teams to the Temporal platform.
Provide guidance on best practices for using Temporal.
Operate and administer the Temporal platform at scale.
Integrate Temporal with developer pipelines.
Deploy and scale containerized application runtimes on OpenShift or Kubernetes.
Configure enterprise SSO and integrate cloud services with identity providers.
Establish on-call practices and incident response for a new service.
Run platforms as an internal shared service (multi-tenant, namespace isolation, developer enablement).