Week 3: another week of nothing but one thing extra

This week was not much different from the previous one in terms of actual workload, but it gave me more clarity about the people around me, the company structure, and who I should focus on connecting with as my internship continues. My work on the Document AI project remained limited, with only small daily tasks and little progress on the actual project itself. At this point, a lot of my experience has been more about learning the environment and understanding the company’s processes rather than doing technical work. Even though that can feel slow at times, I am starting to understand that internships are not always about jumping directly into projects, but also about building a foundation and understanding how everything works.

A large part of this week was spent setting up my development environment. I installed Python and Visual Studio Code, which are both tools that I will need for upcoming technical tasks. What seemed like simple installations turned into a longer process because of company security policies and the permissions required to install software on company devices. Each installation took about a day to complete because approvals had to go through different channels. Although it felt like a small task, it reminded me of how security and compliance are major parts of working in a large financial institution. It also showed me that even basic technical work can be slowed down by organizational processes.

One important update this week was meeting with my manager’s manager. During that meeting, she explained that there is work available for us and that our team assignments may be changing soon. This was encouraging because it gave me reassurance that my responsibilities will become clearer and more active. Up to now, the uncertainty of not knowing exactly what I would be doing every day made it harder to feel fully involved. Hearing that there is a plan moving forward made me feel more optimistic about the rest of the internship.

The most significant experience of the week, however, was meeting with the Chief Information Officer (CIO) and his leadership team, alongside interns from other locations. This stood out to me because it was my first time interacting directly with someone at such a high level of leadership. Before this meeting, I had a very different image of what executives like a CIO would be like. I expected someone very formal, distant, and serious all the time. Instead, the CIO came across as playful, easygoing, and approachable while still being highly respected and clearly competent in his role.

That meeting changed my perspective on leadership. It made me realize that professionalism does not always mean acting serious or putting on a “professional mask” every moment. The CIO showed me that authenticity can be part of leadership. He was comfortable being himself, joking around, and connecting with people in a natural way, but at the same time everyone respected him because of his position and his knowledge. That balance between authority and personality was something that stood out to me the most.

It also made me reflect on my own future and where I could see myself in the long term. For the first time, I could realistically imagine myself working toward becoming a CIO one day. Not only because of the influence and responsibility that come with the role, but because of the ability to shape the technological direction of an organization and guide teams toward innovation. I also connected with the way he carried himself because it matches the type of leader I would want to become.

I see myself as someone who values honesty, directness, and humor. For example, if someone asked me what the best part of work is, I would consider any answer that does not include “money” to be dishonest. To me, pretending otherwise would feel like lying, and I strongly dislike dishonesty. Of course, work can also be meaningful in other ways, but financial reward is a major truth that many people avoid saying openly. I would want to bring that kind of honesty into leadership while balancing it with professionalism and responsibility. I think being honest in that way can make people trust you more because they know you are genuine.

Looking ahead, my goal for next week is to schedule a meeting with the CIO. I want to build a stronger professional connection with him, gain insights that can help me prepare for my capstone presentation, and improve my chances of getting into the Technology Development Program (TDP). I think building relationships with leaders is just as important as building technical skills, especially in a professional environment like this.

Another new development this week was participating in training for building AI agents, which will be the focus of our capstone project. This was one of the more exciting parts of the week because it connects directly to the growing field of artificial intelligence. While I do not fully understand the scope of the project yet, I plan to explore it more deeply next week once my day-to-day responsibilities become more defined. Overall, even though this week was slower in terms of technical output, it was valuable in helping me understand leadership, company culture, and my own future goals more clearly.