I'm a second-year computer science student hoping to move toward DevOps, cloud, or platform engineering. Since pure DevOps internships can be difficult to find, I've also been applying for software engineering internships, but I was rejected during CV screening by every company and didn't receive any interviews.
I currently have basic experience with Docker, Git, operating systems, Terraform, and infrastructure as code. I'm also considering studying for the AWS Solutions Architect Associate certification this summer. I have a home lab PC available for hands-on work.
I suspect my CV lacks a substantial project that demonstrates what I can actually build and operate. What projects or skills would be most valuable to develop this summer, and how can I present them effectively when applying for internships?
5 Answers
Your project idea is probably more valuable than the AWS certification at this stage. The cert can help demonstrate fundamentals, but it usually won’t compensate for a CV that lacks evidence of practical work. Keep the project focused and iterate on it over several months. Include a clean README, architecture diagram, screenshots or dashboards, meaningful commit history, and a short explanation of the tradeoffs you made.
Don’t restrict your search to roles with DevOps in the title. Look at backend, cloud support, infrastructure, build and release, site reliability, and junior systems administration internships. Early experience with Linux, networking, scripting, troubleshooting, and automation can all lead toward platform engineering. A small company or volunteer project can also give you real requirements and users instead of another tutorial project.
Make the project solve a real problem rather than building infrastructure for its own sake. You could create a service that deploys automatically, runs health checks, rolls back an unhealthy release, tracks resource usage, and sends cost or availability alerts. Even a home-lab deployment is fine if you explain the design, limitations, security choices, and how you tested failures. That gives interviewers concrete topics to discuss.
Build one small system end to end instead of collecting more isolated tool skills. For example, create a useful web app or service, containerize it, deploy it with Terraform, add CI/CD, monitoring, logs, alerts, backups, and a clear recovery process. Document how someone can rebuild it from scratch and what happens when a deployment or health check fails. A project that shows reliability, observability, and maintenance will stand out more than simply listing Docker and Terraform.
Also review the CV itself. Tailor it to each type of internship, put the strongest project near the top, describe what you built and the outcome instead of only naming technologies, and link directly to a polished repository. If possible, ask a professor, career adviser, or experienced engineer to critique the document. Screening failures can come from presentation and keyword mismatch as much as from a lack of ability.
Systems administration can be a useful starting point, but treat it as one possible route rather than assuming those jobs are widely available. Apply broadly and focus on roles where you’ll get hands-on experience with systems, automation, and production support.