My Experience as a Intern


My Experience as a Fresher After Joining My First IT Role

Joining my first IT role as a fresher was a completely new experience for me. I was excited, but at the same time, I knew that real industry work would be very different from learning on my own or during internships.

First Week: Understanding Before Doing

My first week was mainly about understanding things. I did not start coding immediately, and that was actually a good thing. I spent time getting familiar with:

  • The technologies used in the company

  • The work culture and communication style

  • Ongoing projects and their purpose

Most of the projects were GovTech projects, which made me feel proud because these applications are used at a large scale and require responsibility and accuracy.

During this week, I understood that in real companies, understanding the project and requirements is more important than jumping directly into coding.


Second Week: First Task and Real Learning

In the next week, I was assigned my first task — working on a static website. Even though it sounded simple, it was my first real contribution to a live project.

The tech stack included:

  • React

  • Tailwind CSS

  • Git version control

I took help from my colleagues whenever I was stuck. This taught me an important lesson:
Asking for help is not a weakness, it is part of teamwork.

Slowly, I started understanding how real projects are structured, how components are managed, and how design is handled using Tailwind CSS.


A Big Mistake I Made (Very Important for Juniors)

While working on this project, I made a mistake — a common but serious one.

I forgot to work on my own Git branch and directly made changes on the main branch.

I knew the rule:

Never work directly on the main branch.

But due to time pressure and urgency to deliver the project to the client, I forgot at that moment. The changes were needed immediately, and the team handled it carefully.

This was completely my fault, and I accepted it.


A Lesson for My Juniors 

Never repeat this mistake.
Always remember:

  • Create a separate branch

  • Make changes in your branch

  • Test properly

  • Then raise a pull request

The main branch is critical. One wrong change can affect the entire project.

Mistakes happen, especially when you are new — but learning from them is what matters.


What Working in a Real Team Taught Me

This experience taught me many things that books and tutorials cannot:

  • Real projects have deadlines

  • Team coordination is very important

  • Git discipline matters a lot

  • Communication saves time

  • Pressure is part of the job

I also learned how seniors support freshers and how teamwork helps everyone grow.


My Biggest Takeaway

As a fresher, you don’t need to know everything on day one. What matters is:

  • Willingness to learn

  • Responsibility towards work

  • Accepting mistakes

  • Improving every day


This journey is still ongoing, but every week is teaching me something new — not just about technology, but about professionalism and growth.

If this story helped or motivated you, feel free to visit my profile Linkedin.com and connect.

Comments

Popular posts from this blog

My First Stipend-Based Internship💻🚀

How I Fixed the Prisma Error

Design Web Pages using CSS