How You'll Be Assessed

Let's be transparent about how this works. This internship is a talent pipeline — the goal is to find people we want to keep. So it's worth knowing what "doing well" actually means here.

We measure trajectory, not trivia

You are not expected to master ten deep fields in twelve weeks — nobody does. What we're watching for is how you learn and operate:

• Do you make steady progress through the modules and assignments?
• Do the things you build actually work — and can you show them working?
• How do you handle being stuck — do you try, search, and read first, then ask a sharp question?
• Do you document and communicate clearly (your assignment notes, your checkpoint demos)?
• Are you curious — do you use the "Dig deeper" links, ask "why", go a step beyond the assignment?

A person who finishes Module 7 with shaky understanding looks weaker than a person who finishes Module 6 having truly got every piece. Depth of understanding beats racing ahead.

How it's checked

• Assignment acceptance criteria. Every assignment ends with a checklist of self-verifiable "done" conditions. Meet them honestly — the point is the skill, not the checkmark. Don't fabricate output.
• The weekly checkpoint. A short live demo of your latest working assignment + one thing that confused you. This is the main signal.
• The capstone (Week 12). The big one. It re-exercises every module: an app, containerized, deployed to the cluster through a pipeline, and observable in Grafana. A strong capstone is the clearest "yes" we can get.

What a strong finish looks like

By Week 12, a strong intern can independently take a small service from source code to running and observable on real infrastructure, explain every layer they used, and show good judgement about why each tool was the right choice. That's the bar for "we'd like to keep working with you."

Your part of the deal

• Be honest about what works and what doesn't — surfacing a problem early is a strength, not a weakness.
• Keep your work in the open (Git, your assignment notes) so progress is visible.
• Ask for help at the 30-minute mark — but bring what you tried.

That's it. Do the work, build real things, stay curious, communicate clearly. Now go open Module 1 — Networking Fundamentals.