Location: Oslo, Norway | Trondheim, remote
Type: Part-time during studies (8–10 hours/week, with flexibility to scale during breaks)
Cloudgeni builds AI agents for CloudOps and platform teams. Our focus is practical: turn infrastructure findings (drift, misconfig, security gaps, cost issues) into reviewable, governed Infrastructure-as-Code changes delivered as pull requests in the workflows teams already use.
We work primarily with Terraform/OpenTofu (and related IaC ecosystems), and integrate with common CI/CD and code review systems. The product is built for developer self-serve velocity while maintaining enterprise-grade security and auditability (PR-first, guardrails, no “auto-merge to prod”).
We’re a small team with real customer traction and paid pilots, and we move fast. This internship is for someone who wants to ship meaningful product, not “watch and learn.”
Build core components of our AI-driven CloudOps agent: repo analysis, change generation, guardrails, and PR workflows.
Work with IaC (Terraform/OpenTofu) and cloud primitives (AWS/Azure/GCP) to model infrastructure changes safely.
Implement and improve automation pipelines (e.g., plan/test/policy checks) so generated changes are verifiable before review.
Help design secure execution patterns (sandboxed runs, least privilege, safe handling of credentials and artifacts).
Collaborate directly with founders on product and technical decisions; you’ll have real ownership.
Solid programming fundamentals; comfortable shipping production-quality code.
Experience with Python and/or TypeScript (you don’t need to be senior, but you must be able to deliver).
Basic familiarity with at least one of:
Terraform/IaC
Cloud platforms (AWS/Azure/GCP)
CI/CD (GitHub Actions, Azure DevOps, etc.)
Able to work independently, communicate clearly, and ask for help early when blocked.
Time: 8–10 hours/week consistently; option to increase during summer/school breaks.
Compensation: Competitive hourly pay; opportunity for full time employment upon satisfactory performance.
Start: As soon as possible (we prioritize execution over long hiring cycles).
Send:
A short note/link on what you’ve built (projects, GitHub, coursework, shipped systems)
Your availability (hours/week + start date)