Infrastructure Lead

ABOUT US
CarDoctor is a pioneer in applying AI to optimize vehicle care and automotive operations. The CarDoctor ecosystem connects drivers, garages, and partners within an intelligent platform that delivers convenience, safety, efficiency, and cost savings for users.
Aggregatori Capaci is the core technology development company behind CarDoctor, building its technology ecosystem from the ground up with AI-first architecture and emerging technologies at its core.
Working Location: 5BT2, Me Tri Ha Urban Area, Tu Liem Ward, Hanoi
Working Hours: 08:00 AM - 05:30 PM | Monday - Friday
JOB PURPOSE
Own the strategy, architecture, and operating model for the company's infrastructure (cloud + on-premise), and be accountable for its reliability, security, and cost to the CTO/Management.
Build, lead, and grow the Infra team (5-7 engineers): hiring input, mentoring, performance management, and career development.
Own the infrastructure budget and vendor relationships (cloud providers, data center/colocation, network); make and defend the build vs. buy, cloud vs. on-prem calls for the company.
KEY RESPONSIBILITIES
A. Ownership & Architecture Decisions
Own the hybrid infrastructure architecture end-to-end (cloud AWS/GCP + on-premise data center); decide, workload by workload, what runs where, based on cost, performance, compliance, and data-residency requirements - and own the consequences of that call.
Set the company's standards for infrastructure design, security, and operations, and hold the team and other engineering teams accountable to them.
Own capacity planning and the 12-24 month infrastructure investment roadmap (hardware + cloud); present and defend it to the CTO/Management.
Own the company's HA/DR strategy: define RPO/RTO per service tier, and be the escalation point when a major incident threatens business continuity.
B. Team Leadership & People Management
Hire, onboard, mentor, and manage the performance of the Infra team; set individual growth plans and run regular 1:1s and reviews.
Assign ownership of platform areas (cloud, on-prem, data/middleware, security) to team members; review their designs and unblock them on hard technical and organizational problems.
Build the team's on-call structure, incident escalation path, and knowledge-sharing practices (runbooks, documentation).
C. Budget, Vendor & Cross-functional Accountability
Own the infrastructure budget (cloud OPEX + on-prem CAPEX); track spend against plan and report variances to the CTO/Management.
Own vendor relationships and contracts (cloud providers, data center/colocation, network, monitoring tools); negotiate terms and evaluate new vendors.
Be the infrastructure counterpart to Backend, QA, Security, and Product leads: agree on release/rollback standards, security requirements, and reliability targets (SLAs) the whole engineering org is held to.
Report infrastructure health, risks, incidents, and roadmap progress to the CTO/Management on a regular cadence.
D. Technical Baseline (delivered through the team, not solo)
Ensure the team delivers and operates: Kubernetes (EKS + on-prem) at scale, CI/CD and IaC (Terraform, Helm, GitOps), observability (Prometheus/Grafana/ELK) with enforced SLIs/SLOs, and security controls (IAM/RBAC, secret management) across both environments.
Step in hands-on for the hardest architecture or incident problems the team cannot resolve alone.