Developer who understands the "why" behind the code

I believe great software starts with understanding people's needs. As a front-end developer, I combine technical expertise with user-centered design to build application that make sense.

Here's what I'll cover:

• • Educationt that shaped me to think in business metrics, not just technical specs
• • Building with purpose, not just pixels
• • Where I'm headed next

Building with purpose, not just pixels.

This mindset comes from my unique path - studying organization of information systems and business informatics for my master's taught me to see technology through business lens.
Now, with 2+ years of hands-on experience as a developer I approach every project differently. When I'm building a feature, I'm not just thinking about clean code or smooth animations - I'm asking myself: How does this help business grow? What problem does this solve for users?
This perspective has made me a better developer and a more valuable teammate.

I get genuinely excited when I can use both sides of my brain – when I'm not just coding in isolation but understanding why users clicks where they click, what keeps them coming back, and how my code can make their experience better.
Some of my favorite projects have been the messy ones where I needed to dig into analytics, talk to actual users, and then build something that solved real problems. That's when coding feels less like work and more like solving puzzles that actually matter.

What I do differently

Need someone who can dive into your analytics, identify the real problem, bring everyone along, and then build it? That's where I thrive. I focus on outcomes that matter – the kind that show up in KPIs, not just git commits.

This isn't just about being a "good communicator." It's about solving the right problems, not just solving problems right.

Where I'm headed

I want to keep building at the intersection of business and technology. Whether that's front-end development, product management, leading software projects or something in between, I'm drawn to roles where understanding both sidesis an advantage.

If you're working on something where this mindset would be valuable, I'd love to hear about it.