About the role

What we do Megazone US is a cloud Managed Service Provider. Companies hand us the cloud environments that run their business — applications, databases, networks — and we keep them running, secure and affordable across AWS, Azure and Google Cloud. In practice that means: monitoring customer systems 24x7 and responding to alerts; patching, backups and tested restores; reviewing accounts against security baselines and supporting audits such as SOC 2; analysing cloud bills and cutting waste (FinOps); automating repetitive work with scripts and infrastructure-as-code; and explaining all of it clearly to the customer. Our parent company is Korean and our customers are global, so you also see how a real follow-the-sun operation runs. What you would do - Work a real ticket queue alongside a mentor engineer — access requests, monitoring changes, inventory and tagging clean-up — owned end to end. - Run scheduled health checks, patching windows and backup verification with an engineer. - Pull cloud cost and usage reports and flag waste; help build the savings case. - Write and improve runbooks and knowledge-base articles the whole team uses. - Build one automation — a script or dashboard — that removes a recurring manual task. - Second-block co-ops go further: incident response, migration support, and Terraform contributions under review. What we will teach you - Cloud platforms: core AWS services (EC2, S3, IAM, VPC, RDS, CloudWatch) and their Azure and Google Cloud equivalents; how enterprise cloud is really organised — many accounts, landing zones and guardrails. - Operations: Linux and Windows administration, monitoring and alerting with Datadog and CloudWatch, incident and change management in Jira Service Management, backup and disaster recovery. - Automation: Python or Bash against cloud APIs, Terraform, Git and code review, an introduction to containers and Kubernetes. - Security and cost: least-privilege access, cloud security baselines, what a SOC 2 audit asks for, and how to read and reduce a cloud bill. - Professional: writing updates a customer will read, running a handover, and working with colleagues in other countries. - Certification: we pay the exam fee and give study time for AWS Cloud Practitioner — and Solutions Architect Associate for a strong second block. Most co-ops leave certified. Who we are looking for - Required: enrolled in Computing & Information Technologies, Information Sciences, Computer Science, Computer Engineering, Cybersecurity, Networking & Systems Administration, Software Engineering, MIS or similar; at least one year of study completed, including coursework in programming, networking, operating systems or databases; comfortable at a command line and willing to learn Linux; clear written English; dependable and detail-oriented — in operations, following the procedure and recording what you did matters more than being clever; willing to ask for help early rather than guess on a production system. - Helpful, not required: any hands-on cloud exposure at all, including a free-tier account or a class lab; scripting in Python, Bash or PowerShell; a home lab, help-desk job or anything you kept running for someone else; AWS Cloud Practitioner or CompTIA; Korean language ability. Working pattern - Full time during the block, standard business hours in your office’s time zone. Laptop and tooling provided. - Occasional evening or early-morning work for maintenance windows and calls with our Korean colleagues — planned in advance, infrequent, never overnight. Co-ops are not on the on-call rotation and travel is not expected. - Onsite or hybrid so you sit near your mentor. Strong co-ops are offered a returning block and are our first pipeline for full-time Cloud Operations Engineer roles. For faculty and career services Work is supervised and mapped to a learning plan agreed at the start of the block, with a named mentor, a mid-block check-in and an end-of-block evaluat