Skip to content
Aplazo

Lead DevOps Engineer

MexicoRemote · Mexico
Staff · FullTime · Engineering
POSTED 10 NOV
Apply Ask
Role
4 days opentrue age
Posted 10 Nov
CompanyAplazo →
8open roles
Opened · 30d
+0
Closed · 30d
−2
10d of snapshots · 30d window
Market
895open · Staff DevOps / SRE / Infra
Opened · 7d
+859% of open
All devops / sre / infra
6,930open
All tracked boards · live 15 Nov · n=895
AWSTerraformDistributed systems

About the role

Aplazo's mission is to empower financial access, opportunity, and freedom by connecting people and businesses in Latin America through fair, simple, and transparent financial solutions.

We are looking for a Lead DevOps Engineer to join our DevOps & SRE squad, the team that keeps Aplazo's core infrastructure reliable, scalable, and secure across ~150 microservices. This is a senior individual contributor role: you will own entire platform systems end-to-end, from CI/CD and infrastructure as code to observability and on-call tooling, and act as a technical leader for the squad. You are as comfortable leading a design review or mentoring a teammate as you are debugging a production incident or reviewing a Terraform change.

You are the engineer your squad trusts to set the technical bar, untangle the hardest problems in the platform, and connect day-to-day infrastructure work to why it matters for Aplazo's business. Depending on the squad's needs, you may also be designated its Tech Lead, working in partnership with the Tech Lead Manager.

What you'll work on

Owning one or more core platform systems end-to-end: CI/CD and deployments, IaC and multi-account governance, or observability and incident tooling

Driving the squad's roadmap pillars: security & infrastructure hardening, CI/CD & deployment excellence, reliability & incident management, AI platform infrastructure, and seasonality hardening

Leading incident response and post-mortems in the platform domain

Raising the engineering bar through design reviews, RFCs, hiring interviews, and mentoring E1–E3 engineers

Reducing toil by making keep-the-lights-on (KTLO) work visible and automating what actually eats the team's time

Partnering with requesting squads to turn their needs into well-scoped platform work

Key responsibilities

Technical Skills

Bring expert knowledge across multiple areas of the platform (cloud infrastructure, CI/CD, IaC, networking, observability) and of how application services run on top of them

Drive complex infrastructure design that anticipates scalability, failure modes, and regulatory impact

Align platform design with AWS Well-Architected principles: multi-account governance, safe release strategies, resilience, and cost

Master observability and cross-service debugging so others come to you for guidance

Use AI strategically for architecture exploration, large IaC refactors, and experiments; champion squad-level AI tooling such as smart alerting and automated triage

Get Stuff Done

Own large platform features or system improvements from idea to production

Structure ambiguous problems into milestones, dependencies, and risks, and deliver predictably

Lead incident response and post-mortems in the platform domain; strengthen runbooks, escalation paths, and reliability metrics

Close tasks regardless of security, networking, or cross-team dependencies

Remove squad impediments and escalate effectively when support or authority is required

Business Impact

Deliver platform projects that measurably improve key metrics (availability, DORA metrics, MTTR, cloud cost)

Understand Aplazo's business model, Mexican regulation, and LatAm credit dynamics well enough to weigh them in infrastructure decisions

Identify trade-offs that balance delivery speed against regulatory constraints (CNBV, Condusef, PCI, SOC 2)

Connect squad work to business outcomes: why it matters and how success is measured

Communication & Leadership

Act as a technical leader for the squad: design reviews, tech talks, hiring interviews, and mentoring E1–E3 engineers with demonstrable outcomes

Produce RFCs, ARRs, and design docs that make technical decisions and their rationale clear, reviewed, and discoverable

Communicate risks, dependencies, and trade-offs clearly across Engineering, Product, and leadership, challenging assumptions and proposing solutions

Ship with Datadog dashboards visible to all of engineering, plus a squad-owned runbook

Model psychological safety, constructive disagreement, and recognition in Tech All Hands, Demo Days, and Slack

Source · AplazoFirst seen 10 NovOriginal ↗