Senior Site Reliability Engineer

Techunting; Buenos Aires; Remote; ARS 136,310,000 - 196,892,000; Full time

Job summary

Techunting is hiring a hands-on Senior Site Reliability Engineer to keep FileScience reliable for customers. You will define SLIs/SLOs, build monitoring, and lead incident response while improving production reliability and backup integrity.

You will collaborate with product engineers to automate recurring operational work, expand observability, and ensure safe deployments with rollback paths. This role is remote across LATAM, with opportunities to influence service reliability at scale.

Responsibilities

• Define reliability metrics with SLIs/SLOs for product availability and backup jobs.
• Add logs, metrics and traces to identify the affected customer and job.
• Lead incident response with runbooks, escalation paths and post-incident follow-ups.
• Check that backups run when expected and test recovery with product engineers.
• Automate recurring operational work and ensure safe deployments with rollback paths.

Job description

Location: LATAM (remote)

The role

We're hiring a hands-on Senior Site Reliability Engineer to keep FileScience reliable for customers. Some of the hardest failures are quiet ones: a backup stops making progress, finishes with files missing, or reports success when it shouldn't. You'll work with our engineering team to catch these problems, improve monitoring and incident response, and fix reliability issues in production code and infrastructure.

What you will do

01 Define how we measure reliability. Set service-level indicators and objectives (SLIs/SLOs) for product availability and backup jobs. Show what we can and cannot yet measure, and use the results to decide what to improve first.

02 Make failures easier to find. Add logs, metrics and traces that identify the affected customer and job. Build useful alerts, reduce noise, and regularly check that monitoring works and alerts reach the right person.

03 Lead incident response. Maintain incident tools, escalation paths and runbooks. Diagnose problems, keep people informed, confirm service has recovered, and follow through on fixes that prevent repeat incidents.

04 Check that backups actually work. Build checks for whether each customer's backups run when expected, capture the expected data and can be restored. Work with product engineers to compare source and backup data and test recovery.

05 Automate recurring operational work and ship reliability fixes. Work with product engineers on safer deployments, growing workloads, queue backlogs and third-party API failures. Test changes before rollout, keep a rollback path where possible and verify the result.