I’m the kind of person who likes solving puzzles, understanding how things work, and staying with a problem until it finally makes sense.

My path into cybersecurity did not start here. I come from a background in full-stack development and business intelligence, where I spent time working with applications, data, systems, and problem-solving at a technical level. That experience shaped how I think, not just in terms of using tools, but understanding how things are built and how they behave when something goes wrong.

Development taught me how systems connect: how applications work, how APIs pass data, and how different components depend on each other. Business intelligence added another layer by helping me think about patterns, reporting, and how to explain technical information in a way that actually makes sense to other people. Over time, I started to focus less on just building systems and more on understanding failure, why something breaks, what the signs look like, and how you would even begin to detect or prevent it.

That shift in thinking is what led me into cybersecurity. Instead of seeing systems as something to build, I started seeing them as something to analyze, test, and challenge. What happens under stress? What happens when something is misconfigured? What does suspicious behavior actually look like in logs or system activity?

Now I am building on that foundation in a more focused way. I use my development background to understand how systems can be misused, my analytical mindset to review logs and behavior, and hands-on lab work to test and validate what I am learning. This is not a reset for me, it is a progression. I am taking what I already know and pushing it further into security, one step at a time.

My background before cybersecurity includes full-stack development and business intelligence. That background matters because it gave me a strong foundation in how systems are built, how data moves, how applications are structured, and how technical decisions affect the bigger picture.

Development taught me to think like a builder. When I look at an application or an API, I think about how the pieces connect, what assumptions are being made, where trust is being placed, and how something could break if those assumptions are wrong. Business intelligence taught me to think about data, patterns, reporting, and how to explain information clearly to people who need to make decisions.

Cybersecurity brings those experiences together. It lets me use the builder mindset to understand systems, the analyst mindset to review evidence, and the documentation mindset to explain what happened in a way that is useful to others.

I work best when I can get hands-on with the problem. Reading and studying are important, but I understand things better when I build them myself. That is why I set up lab environments, test different scenarios, generate logs, review alerts, and document the process from start to finish.

I also take troubleshooting seriously. A lot of learning happens when something fails. In my projects, I have had to deal with rules not triggering, services failing, syntax errors, configuration problems, and results that did not match what I expected. Those moments are frustrating, but they are also where the real understanding starts.

When I work through a problem, I try to slow down enough to understand it instead of rushing to a quick answer. I look at what changed, what evidence I have, what the logs are showing, and what the most likely cause is. Then I test, adjust, and keep going until the result makes sense.

I am early in my cybersecurity career, but I am building toward roles where I can support detection, investigation, secure design, and security operations. SOC Analyst, Security Analyst, Junior Security Engineer, detection support, cloud security support, and API security support all connect with the direction I am going.

I know I still have a lot to learn, and I am okay with that. What matters to me is that I keep improving and keep building real evidence of that improvement. Every project teaches me something: how to set up a better lab, how to document more clearly, how to validate a detection, how to explain risk, or how to think more like a defender.

I am not trying to pretend I am already senior. I am trying to show that I am serious, consistent, and willing to do the work. I want my portfolio to show progression, not perfection.