Team Leader, SRE
AI summary
Remote is hiring a Team Leader for its Site Reliability Engineering team in Nairobi. This is a 60% individual contributor and 40% leadership role covering Kubernetes, AWS, PostgreSQL, CI infrastructure, observability, and reliability practices. The position involves people leadership, career development, and hands-on technical direction as the company's reliability practice matures.
- Hybrid role: 60% IC and 40% people leadership
- Owns Kubernetes, AWS, PostgreSQL, CI and observability stack
- Responsible for career development and performance of reports
- Reliability practice is maturing with open, interesting problems
- Requires production Kubernetes and meaningful-scale AWS experience
AI job guide
Use this guide to check salary signals, requirements, documents, application steps and safety before you apply.
AI salary guide
Not enough public dataNot enough public salary data is available for this exact role. Before applying, prepare to ask about gross pay, benefits, contract length, probation period, transport and any allowances.
Can you qualify for this role?
- UnclearRelated work experienceThe text mentions experience, but the exact level should be confirmed at source.
- PreferredPractical evidence in security, entregador, segurancaThe tags and summary point to skills connected with this role.
- RequiredAvailability to work in NairobiThe vacancy is associated with this location.
- UnclearComfort with the Full Time contract termsConfirm hours, duration, probation and benefits at the original source.
Documents to prepare
- Likely requiredUpdated CV
- Role specificCover letter or short employer message
- OptionalProfessional references
- VerifyID or passport only after verifying the employer
Application tips for this job
- Place your strongest Team Leader, SRE evidence in the first half of your CV.
- In your cover letter or employer message, connect your experience to Remote and the role in Nairobi.
- Add concrete examples related to security, entregador, seguranca, ideally with measurable outcomes or clear responsibilities.
- Follow the instructions from JobWeb Kenya; avoid sending documents to unofficial contacts or copied links.
- Confirm the deadline, interview location and employer contact before sharing personal documents.
- Prepare a polite question about pay, benefits and contract terms for later interview stages.
Source and safety check
- JobWeb Kenya
- Original source link available
- Application method is clear
- Deadline not specified
- No major risk signal was detected in the captured text.
Never pay for interviews, shortlisting, medical checks, uniforms, or job placement. Confirm every application at the original source before sharing personal documents. Report suspicious listing.
Interview preparation
- What experience makes you a strong fit for this Team Leader, SRE role in security, entregador?
- How have you handled responsibilities similar to those in this job post?
- Are you available to work in Nairobi under the listed contract or schedule?
- Prepare examples with clear responsibilities, tools used and measurable outcomes.
- Review the source and research Remote before the interview.
Ask what the first priorities will be in the role and how success will be measured.
Similar jobs to consider
Use AI to apply better
After confirming the original source, use Career Assistant to check role fit, tailor your CV and prepare a cover letter or employer message.
Original source description
What this job can offer you
Remote’s SRE team exists so that our engineers can move quickly and our customers get a product that stays up. The team owns Kubernetes, AWS, PostgreSQL, CI infrastructure, our observability stack and the reliability practices that sits on top of all of it.
We are looking for a Team Leader to run that team. This is a 60% IC, 40% leadership role. You will own the career development of your reports, steer the teams focus using judgment against the company goals, and you will be the spokesperson for the team across engineering. You will also stay close enough to the technical work to set direction with credibility and to know when something is going wrong before it is escalated to you.
Reliability practice at Remote is maturing rather than mature. Our SLO framework is live on its first few teams and needs to reach the rest, there is real work to do on how we balance operational load against project delivery. If you want a team where the foundations are in place and the interesting problems are still open, this is that team.
What you bring
People leadership
You have led an SRE, infrastructure or platform engineering team, and you have owned your reports’ growth, performance and career progression rather than just their sprints.
You coach both craft and the soft skills, you can point to people who grew because of it.
You handle underperformance directly and early, with clarity and empathy.
You have hired engineers, and you can tell the difference between a good interview and a good engineer.
You read team dynamics well and you resolve conflict rather than routing around it.
You have a natural talent fostering commitment to the goals of the company.
Technical depth
A hands-on background in site reliability, DevOps or cloud infrastructure engineering, deep enough that you can review your team’s work, challenge a design and be taken seriously in an incident.
Kubernetes in production, including the operational reality of it rather than the happy path.
AWS at meaningful scale.
Hands on AI building, enablement, scaling AI infrastructure.
Solid o11y practices and principles,
Infrastructure as code with Terraform.
CI/CD systems such as GitLab CI, GitHub Actions or Jenkins.
Docker and shell scripting.
You have run a reliability practice: incident response, on-call, SLOs and error budgets, and the discipline of turning incidents into changes that stick.
Understanding and history of working in regulated environments.
Ways of working
You prioritise exceptionally well when operational load and project work compete, and you protect your team’s focus without dropping the operational commitment.
You write clearly. Remote is fully distributed and async, so most of your leadership will happen in writing.
You build relationships across teams. A lot of SRE’s value comes from being the team others bring problems to early.
Nice to have
Working knowledge of a backend language, ideally Elixir, or otherwise Java, Clojure, Node.js, Python or similar.
Depth in modern observability: OpenTelemetry, distributed tracing, and tools such as Honeycomb.
Database operations experience, particularly PostgreSQL or Aurora performance, connection pool health and query tuning.
Running and configuring Linux systems outside a cloud environment.
Security capability from both a defensive and an offensive standpoint.
Cloud cost management and FinOps.
Experience growing a team from a small base, including building the hiring bar as you go.
Key Responsibilities
- Your people
- The full career lifecycle of your reports: onboarding, feedback, performance assessment, progression and hiring.
- Team health, dynamics and the retrospective habit that keeps them honest.
- Being the team’s spokesperson to the rest of engineering and to senior leadership.
- Delivery
- The SRE goals: what the team commits to, in what order, and why.
- The support rotation and on-call model.
- The platform
- Remote’s core infrastructure: Kubernetes, AWS, PostgreSQL, DNS and TLS, CI infrastructure.
- The reliability practice: SLOs, error budgets, incident response and the observability stack.
- The partnership with our Security team on threats, patching and infrastructure controls, including our audit and compliance obligations.
- The vendor relationships that sit behind the platform, including renewals and commercial conversations with support from your Director.