Becoming a Software Engineer: Learning Through Real Challenges

Over the past couple of weeks, something has started to shift for me, for the first time, I truly feel like a software engineer, not because I know everything, but because of the daily rhythm: developing features, debugging issues, fixing edge cases, improving code, and constantly learning how systems behave in real scenarios. Being immersed in this process every day makes it feel real; it’s no longer practice in theory, it’s practice in action.

We recently finished our second sprint, and it came with its own set of challenges; due to access limitations, we weren’t able to deploy the project to the official staging environment creating some uncertainty, especially because at the same time we were dealing with features that weren’t working exactly as expected, and we couldn’t fully validate them in the real environment.

For a moment, it felt like everything was happening at once, but instead of getting stuck, we adapted. We set up our own staging environment to continue testing and preparing a demo; it wasn’t the ideal scenario, but it worked. In the end, we were able to present our progress, and that moment felt like a small victory, not just because of what we built, but because of how the situation was handled.

That experience taught me something important: things won’t always go as planned, and that’s part of the job.

After the sprint, we had our review, and I was able to see improvement in my performance metrics; it’s a small indicator, but it reflects something bigger: I’m becoming more efficient, more confident, and more comfortable with the workflow. There’s still a long way to go, but I can see the progress.

I’m also learning how to manage my days better, by organizing tasks, knowing when to focus deeply, and even recognizing when I need a break. Sometimes stepping outside, getting some sun, and letting my mind breathe makes a bigger difference than pushing through without stopping.

Outside of the core work, there are moments that make this experience even more meaningful. Ping pong has officially turned into “lessons.” One of my coworkers is incredibly good, and apparently has been playing since he was a kid thanks to his grandfather, so now, every game feels like both a challenge and a learning session. We joke about it, compete, laugh, and enjoy those moments that break the routine in the best way possible.

There’s also a strong culture of sharing knowledge. Other interns have been giving presentations about trending topics in software development with AI, exploring tools and approaches to become more efficient. Seeing that level of initiative and curiosity in others is genuinely motivating.

Something that stood out to me recently was a conversation with another developer from a different project. After a previous interaction, he reached out to discuss some ideas and challenges related to AI in his own work. It turned into a really valuable exchange of ideas, but more than that, it changed how I feel.

Now I felt part of the team. Not just my project — the whole team.

Being able to contribute, share opinions, and know that what you think has value… that’s a powerful feeling, it gives you confidence, and it reinforces the idea that you belong in the space you’re in.

At the same time, the responsibility is very real. There’s a lot of work to do, and I genuinely want this project to go well. Not only because of academic requirements or professional expectations, but because I want the result to reflect what I’m capable of; the effort, the mindset, and the way I approach problems, I want it to speak for me.

Also, I had a meeting with my university advisor and my mentor from Pernix, where we aligned expectations for the upcoming months. I presented the scope and deliverables I committed to, almost like setting things in stone, as my professor said. It made everything feel more formal, but also more intentional.

As we moved into the next sprint, we made an important decision: some features needed adjustments, so we rolled back certain tickets and planned them again; at first, that might feel like going backwards, but I’m starting to understand that it’s actually part of building things well. Not everything works perfectly the first time, and that’s okay, what matters is recognizing it, improving it, and making sure things are done right. Testing, refining, and iterating are just as important as building.

Now, a month and a half into this journey, I can say this:

I’m still learning every day. I’m still making mistakes. But I’m also growing — and I can feel it.

Step by step, I’m getting closer to becoming the kind of software engineer I’ve been aiming to be for years, and this, more than anything, keeps me moving forward.