About the Role

We’re looking for an SRE / Reliability Engineering Intern who wants to own how real systems stay up—not just respond when they break.

You’ll work on defining and improving reliability practices across production systems, including monitoring, alerting, incident response, and resilience. This means operating in an environment where systems are evolving quickly, and reliability needs to be built—not inherited.

You’ll collaborate closely with engineering and infrastructure teams to ensure systems are observable, resilient, and continuously improving. Your work will directly impact uptime, performance, and user experience.

If you enjoy thinking in systems, debugging complex issues, and preventing problems before they happen, this role will push you to grow fast.

What You Will Do

Help define SLOs, SLIs, and error budgets for core systems
Set up and tune monitoring and alerting (Prometheus, Grafana, OpenTelemetry)
Participate in incident response, retrospectives, and follow-ups
Contribute to capacity planning and resilience testing
Automate repetitive operational workflows using scripts or tools
Work with engineering and infra teams on reliability improvements
Document runbooks, reliability practices, and incident learnings

What We’re Looking For

Familiarity with Linux and basic system operations
Exposure to Kubernetes or container-based systems
Basic understanding of monitoring and observability concepts
Comfort with scripting (Python, Bash, or similar)
Ability to debug issues across systems and services
Willingness to operate in ambiguous, fast-moving environments

Founding Mindset

You think in terms of user-perceived reliability, not just dashboards
You ask “what does good reliability look like?” before adding metrics
You take ownership of uptime and graceful degradation
You balance speed of change with system stability
You proactively identify reliability gaps before they cause incidents

Bonus

Experience with observability tools like Prometheus, Grafana, or OpenTelemetry
Exposure to incident management or on-call workflows
Experience with resilience testing or chaos engineering
Familiarity with tracing and structured logging

What Success Looks Like

Within 4–6 weeks, you should be able to:
Own monitoring and alerting for a subset of services
Reduce noisy alerts and improve signal quality
Contribute to incident retrospectives with actionable insights
Improve reliability, visibility, or response time in a measurable way

What You’ll Get

Hands-on experience building reliability practices from the ground up
Direct collaboration with founders and core engineering teams
Real ownership beyond a typical SRE internship
A portfolio of dashboards, runbooks, and system improvements
A strong pathway into SRE, platform, or production engineering roles

Who This Is Not For

If you want predictable systems with no incidents to handle
If you avoid ambiguity or cross-team problem solving
If you prefer rigid, siloed environments with predefined processes

Who Will Thrive Here

Builders who want to actively own system reliability
Engineers who think in terms of end-to-end systems
Calm debuggers of intermittent and complex failures
High-agency individuals who care about keeping systems running reliably

About the Company

We’re building the speech intelligence layer for Southeast Asia—turning real-world, accented, code-switched speech into structured, usable outputs for businesses.