Software Developer Intern Review

As a Software Developer Intern at Costain, I owned the end-to-end development of a new internal web application that automated a previously manual job-tracking workflow. Day-to-day, this involved designing the system architecture, building a Flask backend and frontend (HTML/CSS/JS), implementing a SQL database schema, and developing a modular data-scraping engine. I worked in short iteration cycles for gathering requirements directly from stakeholders, translating them into technical tasks, and delivering features rapidly.
I also set up GitLab pipelines for automated testing and deployment, and carried out security testing, resolving issues to align with internal Zero-Trust standards. My role combined hands-on development, architecture decision-making, documentation, and regular progress reviews with non-technical users to ensure the product shipped, worked, and actually delivered value.

Yes, more than a typical intern. I was given full ownership of a real internal product from day one. That included designing the system architecture, building the entire web application, creating the database schema, implementing automation, and setting up CI/CD. I was responsible for gathering requirements directly from stakeholders, agreeing timelines, delivering features on schedule, and ensuring the final system was secure and deployable.

Full-stack delivery under real constraints - I’d built projects before, but this was the first time I had to design, build, and ship an end-to-end system that real users depended on. I developed stronger architectural judgement, cleaner abstraction habits, and a better sense of how to balance speed with maintainability.
Security and reliability fundamentals - Running OWASP ZAP and fixing issues like missing CSP headers, clickjacking protection, and input-validation gaps forced me to understand practical web security rather than just textbook concepts. I also improved my CI/CD skills by setting up automated testing and deployment in GitLab.
Stakeholder and requirements management - I learned how to translate vague operational problems into concrete technical tasks, negotiate priorities, and iterate based on feedback from non-technical users. This sharpened my communication skills and made me more confident owning a project end-to-end.

I had a good level of support. My team were always available if I needed help, and I could contact them at any time for questions or technical checks. We ran weekly check-ins and monthly in-person meetings to review progress, unblock issues, and make sure the project was on track.
At the same time, they gave me enough autonomy to design and build the system myself, the support was there when I needed it, but I was trusted to drive the work independently day-to-day.

The culture was solid and supportive. I worked mainly from home, so most of my interaction was through online meetings, but the team were approachable and easy to work with. Communication was straightforward, expectations were clear, and people were willing to help when needed. The atmosphere wasn’t especially loud or high-energy, but it was dependable, focused, and collaborative when it mattered.

Yes, I enjoyed the internship and got a lot out of it. The work suited me because I had real ownership and could build something end-to-end rather than just doing small support tasks. I liked the autonomy, the chance to make technical decisions, and the fact that the project actually got used. It wasn’t the most social or high-energy environment since I worked mostly from home, but overall the experience was positive and genuinely valuable.

Yes