Job description template

System Administrator

As a Mid-Level System Administrator, you’ll own the reliability of core infrastructure by monitoring services, addressing incidents, and implementing scalable operational improvements. You’ll work independently on well-defined tasks across servers, storage, networking, and identity systems, while partnering with engineering and security to keep systems secure and dependable.

Responsibilities

Monitor and maintain uptime for production systems and core services using logs, dashboards, and alerting signals
Diagnose and resolve incidents across operating systems, networking, and service dependencies, including documenting root causes
Manage system configuration and deployments for servers and services using automation and infrastructure tooling
Administer user access and permissions for systems and applications, ensuring least-privilege and timely deprovisioning
Maintain backup, restore, and disaster recovery readiness; validate that restores meet operational requirements
Collaborate on capacity planning and performance tuning to prevent bottlenecks and recurring failures
Coordinate maintenance windows and change management, ensuring safe rollout and rollback procedures

Must-have qualifications

Hands-on Linux system administration in production (server management, troubleshooting, performance tuning)
Experience implementing and operating monitoring/alerting for infrastructure and services
Proficiency with backup and restore practices, including disaster recovery readiness testing
Working knowledge of identity and access management concepts (authentication, authorization, least privilege)
Experience troubleshooting incidents using logs, metrics, and system/network understanding
Strong operational change management habits (documenting changes, safe rollbacks, following runbooks)

Nice to have

Experience with configuration management or automation tools (e.g., Ansible, Terraform)
Familiarity with container and orchestration platforms (e.g., Docker, Kubernetes)
Knowledge of network fundamentals (DNS, routing, firewalls, TLS)
Exposure to security hardening practices for Linux systems

What success looks like in 12 months

Stable production operations
Faster incident resolution
Improved monitoring coverage and signal quality
Backup and recovery confidence
Secure and well-governed access

Logistics

Full-time (40 hours a week), remote from Latin America.
Working hours overlap with US business hours.

About the company

[About your company: what you build, your stage and team size]

Want it tailored to your stack, seniority and time zone?

Customize with the free generator →

Interview scorecard

Score every candidate against the same bar

Keep production infrastructure reliable, secure, and recoverable by independently managing systems, diagnosing incidents, and improving operational processes.

Outcomes to measure

What this hire should deliver in the first year. Replace [N] with your own targets.

Stable production operations. Measure: Maintain service availability of [X]% across assigned systems for the 12-month period
Faster incident resolution. Measure: Reduce mean time to acknowledge and resolve incidents by [X]% over 12 months
Improved monitoring coverage and signal quality. Measure: Increase actionable alert coverage for critical systems by [X]% and reduce recurring false-positive alerts by [X]%
Backup and recovery confidence. Measure: Achieve successful restore test pass rate of [X]% for required systems, with documented results
Secure and well-governed access. Measure: Complete access reviews and implement least-privilege updates for [X] system/application scopes, with [X]% compliance to policy checks

Competencies and weights

What to evaluate, how much it counts and what a strong answer looks like.

Linux Operations · 24%
Core responsibility is administering and troubleshooting production Linux systems safely and efficiently. Evaluated in Round 1.

Weak: Can describe basic Linux commands but struggles to diagnose multi-step production issues using logs and system state
Meets the bar: Troubleshoots common Linux service and resource issues using logs/metrics and applies targeted fixes
Strong: Independently isolates root cause across service, OS, and dependency layers; applies durable fixes (config, permissions, tuning) and validates outcomes

Incident Troubleshooting · 20%
The role must resolve production incidents and communicate effectively about impact and next steps. Evaluated in Round 2.

Weak: Responds without structured diagnosis and may miss key log/metric indicators
Meets the bar: Leads troubleshooting using a repeatable approach; identifies likely causes, validates hypotheses, and records learnings
Strong: Drives calm incident workflows; coordinates mitigation, captures root cause, and prevents recurrence with specific action items

Monitoring and Alerting · 18%
Reliability depends on actionable signals; the role must tune monitoring to reduce noise and improve response. Evaluated in Round 1.

Weak: Can operate dashboards but relies on manual checks and can’t explain why alerts trigger
Meets the bar: Sets up and adjusts alerts/dashboards for services and correlates alerts to system symptoms
Strong: Designs monitoring changes that improve detection and reduce false positives; documents alert runbooks and ownership

Backup and Recovery · 16%
Operational success requires confidence in restores and disaster recovery readiness. Evaluated in Round 2.

Weak: Understands backups conceptually but can’t explain restore workflow or validation steps
Meets the bar: Executes/monitors backup and restore processes and verifies restore outcomes against requirements
Strong: Improves DR readiness by identifying gaps in restore reliability/timings; automates or standardizes restore validation and reporting

Change Management Discipline · 12%
Safe changes and rollbacks protect uptime and reduce operational incidents. Evaluated in Round 3.

Weak: Makes changes without clear documentation or rollback planning
Meets the bar: Follows runbooks, documents changes, and performs safe rollbacks when needed
Strong: Improves change procedures (templates, checklists, verification steps) and reduces risk through well-defined rollout plans

Access Governance · 10%
Least-privilege access management reduces security and operational risk. Evaluated in Round 3.

Weak: Understands permissions at a high level but can’t map identity changes to system access outcomes
Meets the bar: Manages users/roles/permissions, ensures timely deprovisioning, and verifies access changes
Strong: Implements least-privilege controls, reviews access proactively, and detects/rectifies privilege creep with evidence

Interview questions

Questions for every interview round

Each round has an owner, a time box and questions that test the competencies above.

Round 1: Infrastructure fundamentals
System Engineering Lead · 45 min

Walk through a recent production Linux incident you handled end-to-end: what symptoms you saw, what logs/metrics you checked, and what you changed to fix it.
Describe how you set up or tuned monitoring/alerting for a critical service. What data sources did you use, and how did you decide alert thresholds and routing?
Tell me about a performance bottleneck you diagnosed on Linux. What was your approach and how did you confirm the system was healthier after the change?

Round 2: Reliability and troubleshooting
Site Reliability Engineer · 45 min

Describe a time you led troubleshooting during an outage or degraded performance. How did you structure the investigation and communicate status/impact?
How do you ensure backup and restore processes are reliable? Walk through your approach to testing restores and verifying they meet operational requirements.
Tell us about a recurring incident pattern you helped eliminate. What was the root cause and what operational change prevented it from happening again?

Round 3: Security and operational execution
Security/IT Operations Manager · 45 min

Explain how you implement identity and access governance for systems you administer. How do you apply least privilege and handle onboarding/offboarding?
Give an example of a change you executed in production using a runbook/checklist. What did you verify before, during, and after—and how did you plan/perform rollback if needed?
Discuss a situation where you identified monitoring or access gaps that increased risk. What evidence did you use and what specific changes did you make?

Red flags to watch for

Relies on manual troubleshooting without using logs/metrics to drive decisions
Cannot describe how backup/restore is verified (only mentions backups exist, not restore testing)
Makes production changes without runbooks, documentation, or rollback planning
Shows limited understanding of least-privilege access management or offboarding hygiene
Treats incidents as isolated events without implementing prevention through concrete follow-ups

How much does it cost to hire a System Administrator in Latin America?

In 2026, a senior System Administrator in Latin America costs $6,750 to $7,750 a month all-in, versus $14,625 in the US: up to 54% less. Mid-level starts at $4,500.

Country

Mid-level

Senior

Argentina

$4,500

$6,750

Brazil

$5,000

$7,500

Colombia

$4,500

$6,750

Mexico

$5,250

$7,750

United States

$11,875

$14,625

Monthly cost in USD, all-in: the talent's salary plus Teilur's flat 20% fee, from our 2026 rates. The United States row shows what the same role typically costs there.

Compare costs in the calculator →

Frequently asked questions

What does a System Administrator do?

Typical responsibilities include: monitor and maintain uptime for production systems and core services using logs, dashboards, and alerting signals; diagnose and resolve incidents across operating systems, networking, and service dependencies, including documenting root causes; manage system configuration and deployments for servers and services using automation and infrastructure tooling. The full list is in the template above.

How much does it cost to hire a System Administrator in Latin America?

In 2026, a senior System Administrator in Latin America costs $6,750 to $7,750 a month all-in, versus $14,625 in the US: up to 54% less. Mid-level starts at $4,500.

Can I customize this System Administrator job description?

Yes. Teilur's free Job Description & Scorecard Generator rewrites it for your stack, seniority, time zone and hiring urgency in about 15 seconds. No sign-up needed.

Book a Free Consultation

System Administrator Job Description Template