Platform operations engineer in AI products

We're growing Platform Operations and building a system that can detect failures automatically, run proven recovery procedures, and bring engineers in when their expertise is needed. Our goal is a platform that runs reliably with minimal manual work. To get there, we're looking for a Platform Operations Engineer who will learn how the platform works, investigate failures, restore services, and help turn practical experience into runbooks, checks, and automation.

Detect and investigate problems. Respond to alerts, E2E check results, and requests coming in via Telegram, Slack, and email. Clarify symptoms, assess user impact, analyze logs, service state, and configuration, test hypotheses, and pin down the failure. Restore the platform. Execute proven runbooks within the access you've been granted, including restarts, redeployments, and failover to backup resources. Confirm that the product is working again.

Escalate to specialist teams when needed. Bring in Dev Ops, SRE, SIP engineers, and developers promptly when their expertise is required, when no suitable runbook exists, or when a procedure didn't produce the expected result. Hand over the facts you've gathered, the actions you've taken, and your diagnostic findings. Own the incident from the first signal to closure. Record the timeline and the outcome of each action, keep the status current, track next steps, and keep everyone involved informed of progress.

Write postmortems and turn findings into improvements. Work through causes and consequences with the people involved, and assess how well diagnosis and recovery went. Turn the results into bug reports and fix tasks, write and update runbooks, and help automate checks and recurring operations.

Linux and the command line. Navigate the file system, read and filter files, inspect processes, available resources, and environment variables. Application troubleshooting. Reproduce a problem, gather facts, test a hypothesis, and narrow the search. Know how to tell an application bug from a misconfiguration, an unavailable dependency, or a lack of resources. Working with logs. Find events by timestamp, request , or other markers, correlate entries across several services, and pull out the data that's actually useful for diagnosis.

Monitoring and metrics. Hands-on experience with Grafana or similar tools. Understand availability, error rate, response time, and resource consumption, notice changes, and connect them to incidents. Networking and HTTP/APIs. Understand the basics of DNS, IP addressing, ports, and HTTP. Check whether a service is reachable, send a request with curl or Postman, and work out a status code, timeout, or authorization error.

Application configuration. Read YAML and JSON, check environment variables, and compare settings across environments. Understand how configuration affects connections and application behavior. Executing technical procedures. Follow a runbook, verify preconditions before running a command and the result afterward. Know the limits of your access, when to stop, and how rollback and escalation work. Technical curiosity. A drive to understand how the system is built and why it behaves the way it does, to pick up new tools, and to put what you learn to use.

English. Read technical documentation, handle written communication, and discuss technical matters with colleagues and users. Asking good questions. Clarify symptoms, context, and the expected outcome to get to the heart of a problem faster. Clear communication. Describe a problem in a structured way, pass on context when escalating, and explain the current status to people with different levels of technical background.

Independence and ownership. Organize your own work,…