Please mention DailyRemote when applying
AI Summary
About the Role
We’re looking for a DevOps Engineering Intern who wants to improve how systems are built, tested, and shipped—not just maintain pipelines.
You’ll work on CI/CD, infrastructure-as-code, release automation, and developer tooling in a fast-moving environment where systems and workflows evolve constantly. This means building reliable pipelines, improving deployment safety, and enabling engineers to move faster without breaking things.
You’ll collaborate closely with founders and engineers to shape how software is delivered in production. Your work will directly impact developer velocity, system reliability, and release confidence.
If you enjoy automating workflows, fixing bottlenecks, and improving how teams ship software, this role will push you to grow quickly.
What You Will Do
Design, implement, and maintain CI/CD pipelines (GitHub Actions or GitLab CI)
Manage build, test, and release workflows across services
Work with infrastructure-as-code tools (Terraform or Pulumi)
Improve Docker-based build and deployment processes
Implement safe rollout strategies (canary, blue-green, feature flags)
Integrate quality, security, and observability checks into pipelines
Build internal tools to improve developer productivity
Document pipelines, environments, and operational runbooks
What We’re Looking For
Familiarity with CI/CD tools like GitHub Actions or GitLab CI
Basic understanding of Docker and container workflows
Exposure to infrastructure-as-code concepts (Terraform or Pulumi)
Understanding of Git workflows and release practices
Interest in improving developer experience and automation
Ability to operate in fast-changing, ambiguous 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.
Automatically Apply to the Best Remote Jobs
Stop the endless job search. Our AI finds and applies to the best jobs for you.
