Most internships end when the calendar says summer’s over. Mine didn’t, and the extension changed what kind of work I was trusted with.
A three month internship gets you a well-scoped ticket. A year gets you a seat on a team that expects you to still be there when the decision you made last quarter comes back around.
The work
I’ve been on the DMS2 Admin Workspace team, building the internal tools that let other people at the company actually run the system underneath. React and TypeScript on the frontend, C# and .NET with Entity Framework and SQL Server underneath that, shipped through GitHub Actions into Kubernetes by way of Helm. It’s not the kind of work that produces a demo people clap for. It’s the kind that quietly stops being anyone’s problem once it’s done right.
The thing I didn’t expect to lead
Somewhere in my first few months, I noticed most people around me were using GitHub Copilot the way you’d use a search bar: type something, hope, move on. I’d spent enough time with it to know that’s a fraction of what it’s good for, so I started explaining it to whoever was sitting next to me. That turned into a real rollout. Over a hundred engineers, sessions on how to actually prompt it and when to trust it, and a noticeably different pattern of use across the team by the end.
Nobody assigned me that. It just needed doing and I was already doing a version of it for free.
What came of it
They asked me back for a second summer. That’s the part that actually tells me something, more than any single feature I shipped: on a year-long team, being invited to stay means the work held up over time, not just on the day it was demoed.