About me
I currently work as an Application Support Engineer in a banking environment, where I’ve gradually moved from business support and operational roles into more technical responsibility. Over the years, I’ve worked close to real production systems, data, and processes that must work reliably, consistently, and under strict regulatory constraints.
A large part of my current role revolves around documents and data flows across the company. While this was not originally part of my official responsibilities, it naturally pushed me toward automation. I became the person the team relies on whenever a manual process becomes slow, error-prone, or repetitive. That led me to building internal tools, scripts, and small applications that support agents, simplify workflows, and reduce human bottlenecks — always with GDPR and production safety in mind.
I work daily with incident investigation, system configuration, SQL-based data extraction and validation, lifecycle checks of financial products, and close communication with business stakeholders. Business is the primary customer in my role, which taught me to think in terms of impact, clarity, and responsibility rather than “just code”. At the same time, I’m very aware that there is still a lot I don’t know — and that’s exactly what keeps me moving forward.
I want to move into a junior developer role because programming has always felt like the most natural way for me to think and create. Working with data feels almost like shaping the environment itself — taking something raw and transforming it into something useful, structured, and predictable. I’ve always been someone who experiments and learns by doing, whether that was 3D modeling, working with materials, or building things simply to understand how they work. Code gives me the same freedom, but without limits on where it can be applied.
My interest in AI grows from the same place. Not from hype around language models, but from curiosity about patterns in data and how systems can assist humans in understanding complex structures. I’m especially drawn to approaches where AI supports decision-making instead of replacing it — systems that learn from human feedback, operate within clear constraints, and stay transparent about their confidence and limits.
What motivates me most is building things that make complex systems more understandable and manageable. I’m looking for a role where I can grow as a developer, learn from more experienced engineers, and gradually move deeper into data-driven and AI-assisted solutions — responsibly, realistically, and with respect for real-world constraints.