Technical Operations Coordinator

CourtAvenue; Deutschland; Vor Ort; EUR 42.000 - 64.000; Vollzeit

Zusammenfassung

Jobtailor is seeking a hands-on IT operations professional to keep live systems running smoothly. You will own ticket flow across projects, coordinate with clients and engineers, and ensure issues are resolved before impacting guests.

You’ll work with Linux systems, Docker containers, and runbooks to diagnose and fix problems in real time. In this role you’ll maintain clean documentation, post-mortems, and action items, while prioritizing work across multiple engagements and escalating when

Qualifikationen

• 1–3 years in IT operations, systems administration, service desk, or technical project support, in a tech/IT-ops environment or on a technical team inside an agency or studio, where you’ve owned tickets and incidents end-to-end in a real ticketing system.
• Solid fundamentals in Linux or similar systems: comfortable navigating the filesystem, managing permissions and processes, starting/stopping/inspecting services (e.g., systemd), and applying updates with a package manager (e.g., apt, yum, or dnf).
• Practical troubleshooting instincts: know how to investigate issues through logs (journalctl, tail/grep, or structured-log tools), use CLI utilities like curl or wget for diagnostics, and operate Docker containers by reading logs, monitoring health, and restarting unhealthy containers. You won’t write production code or author images, but you will operate live systems daily.
• A strong operational backbone: clean ticket hygiene, sharp documentation, current runbooks, useful post-mortems and after-action reports, and a reputation for keeping details from falling through the cracks.
• Clear communication under pressure: explain a technical incident to a non-technical client without losing accuracy, and deliver hard news while protecting trust.
• Sound judgment across competing workstreams: prioritize, switch context, keep momentum, and know when to escalate before a small issue becomes a larger one.
• Fluency with ticketing and project tools such as Jira, ServiceNow, ClickUp, or similar. The habit of working cleanly in the system matters more than the specific tool.

Aufgaben

• Help keep immersive guest experiences running reliably once they’re live in the world.
• Connect clients, vendors, project managers, engineers, and creative leads so tickets move, deployments land, and issues get resolved before they become guest-impacting.
• Own the flow of support tickets across multiple live engagements, ensuring every issue has a clear owner, next step, and path to resolution.
• Get hands‑on with live systems: restart services, monitor and restart containers, apply patches, run documented deployments, follow runbooks, and troubleshoot issues before escalating to engineers.
• Help launches and updates land cleanly by coordinating deployment windows with engineering, clients, and vendors, including the occasional off‑hours windows required for park downtime.
• Keep teams aligned through weekly ticket reviews and support check‑ins, capturing action items, confirming owners and due dates, and following through until work is complete.
• Make operational knowledge easy to act on by keeping runbooks, after‑action reports, deployment plans, and client documentation current, accurate, and easy to find.
• Protect project health by tracking support‑contract hours and retainer usage, flagging scope creep early so leadership can make timely decisions on change orders.

Kenntnisse

End-to-end ticket ownership

Linux fundamentals

Troubleshooting using logs/CLI

Documentation and runbooks

Communication under pressure

Prioritization and multitasking

Jira/ServiceNow/ClickUp familiarity

Tools

Docker

systemd

curl

wget

Package managers (apt, yum, dnf)

Jobbeschreibung

Responsibilities

• Help keep immersive guest experiences running reliably once they’re live in the world.
• Connect clients, vendors, project managers, engineers, and creative leads so tickets move, deployments land, and issues get resolved before they become guest-impacting.
• Own the flow of support tickets across multiple live engagements, ensuring every issue has a clear owner, next step, and path to resolution.
• Get hands‑on with live systems: restart services, monitor and restart containers, apply patches, run documented deployments, follow runbooks, and troubleshoot issues before escalating to engineers.
• Help launches and updates land cleanly by coordinating deployment windows with engineering, clients, and vendors, including the occasional off‑hours windows required for park downtime.
• Keep teams aligned through weekly ticket reviews and support check‑ins, capturing action items, confirming owners and due dates, and following through until work is complete.
• Make operational knowledge easy to act on by keeping runbooks, after‑action reports, deployment plans, and client documentation current, accurate, and easy to find.
• Protect project health by tracking support‑contract hours and retainer usage, flagging scope creep early so leadership can make timely decisions on change orders.

Requirements

• 1–3 years in IT operations, systems administration, service desk, or technical project support, in a tech/IT‑ops environment or on a technical team inside an agency or studio, where you’ve owned tickets and incidents end‑to‑end in a real ticketing system.
• Solid fundamentals in Linux or similar systems: comfortable navigating the filesystem, managing permissions and processes, starting/stopping/inspecting services (e.g., systemd), and applying updates with a package manager (e.g., apt, yum, or dnf).
• Practical troubleshooting instincts: know how to investigate issues through logs (journalctl, tail/grep, or structured‑log tools), use CLI utilities like curl or wget for diagnostics, and operate Docker containers by reading logs, monitoring health, and restarting unhealthy containers. You won’t write production code or author images, but you will operate live systems daily.
• A strong operational backbone: clean ticket hygiene, sharp documentation, current runbooks, useful post‑mortems and after‑action reports, and a reputation for keeping details from falling through the cracks.
• Clear communication under pressure: explain a technical incident to a non‑technical client without losing accuracy, and deliver hard news while protecting trust.
• Sound judgment across competing workstreams: prioritize, switch context, keep momentum, and know when to escal­ate before a small issue becomes a larger one.
• Fluency with ticketing and project tools such as Jira, ServiceNow, ClickUp, or similar. The habit of working cleanly in the system matters more than the specific tool.