To Whoever Is Reading This Next

To my next team,

My path into DevOps wasn't a traditional one. I started out in Economics, but somewhere along the way, I became curious about technology and the systems behind the applications people use every day. That curiosity eventually led me into cloud engineering, and the more I learned, the more I wanted to understand not just how to deploy something, but how to build it, automate it, monitor it, and make it reliable.

Most of what you'll see in the project section of my portfolio came from that curiosity. I learned by building projects, deploying them, running into problems, researching what I didn't understand, and trying again. Each project has taught me something different, and each one has made me more interested in what happens behind the application which in this case is the infrastructure, the automation, the deployment process, and the decisions that keep systems running.

I'm also aware of where I am in my journey. I haven't spent years working inside a production engineering team, and I don't want to pretend that I have. There is still a lot for me to learn from people who have operated systems at scale and worked through problems I haven't encountered yet.

What I can bring is a willingness to learn and adapt. If I join your team, I don't expect to arrive knowing your systems better than the people who built them. I want to understand how your team works first; your tools, your processes, your standards, and your culture. I believe good engineering isn't only about knowing the right technology; it's also about knowing when to listen, when to ask questions, and when to challenge an idea respectfully.

I'm comfortable learning something new when the situation calls for it. I've had to do that throughout my own transition into technology. Moving from Economics into cloud engineering meant being a beginner again, learning unfamiliar concepts, and consistently pushing myself beyond what I already knew. That experience taught me that not knowing something isn't the problem. Being unwilling to learn it is.

I also care about being a good teammate. I want to be someone who communicates clearly, asks instead of guessing, takes responsibility for mistakes, and is willing to help when something needs to get done. I don't expect to know everything on day one. I do expect myself to keep learning, contribute where I can, and become more useful to the team over time.

The engineer I am today is still growing, and I'm comfortable with that. I'm building toward becoming someone who can design, automate, operate, and improve reliable systems not just someone who knows how to use a collection of tools.

So if you're reading this because you're considering having me on your team, I hope you see more than the technologies listed on my CV. You see someone who chose a different path, taught herself a new discipline, kept building, and is genuinely excited about becoming better at the work.

I don't know exactly where the next part of the journey will take me. But I'm ready to learn.