A journey shaped by curiosity.

I was born in Kadıköy, and my family's roots are in Şile. These two sides of Istanbul, a busy city and a quieter coastal town, are part of my story. Computer engineering is an important part of who I am today, but I do not define myself only by the technologies I use. What excites me most is learning a subject from the ground up, understanding its parts, and turning that knowledge into something that works.

That is how I approach software. I think about the architecture behind a screen, the path data takes, and the small decisions that shape the experience for a user. A good product should do more than work: it should be clear, reliable, and made with enough care that people want to use it again. This portfolio brings together what I have learned, what I have tried, and the questions I am still exploring.

My interest in technology does not end when I close my laptop. I enjoy looking at well-designed digital products and asking why an interface feels smooth or how a small detail changes an experience. Football and sport are part of my life, too. Interests outside work help me ask better questions and look at the things I build from another angle.

I completed high school at İstek Belde Anatolian High School. It was an important time for discovering what interested me and how I learn best. I still carry the habit of researching, asking questions, and comparing different approaches when I face a problem.

I studied Computer Engineering at Beykent University. I tried to take what I learned about algorithms, data structures, databases, and software development beyond the classroom. Designing an application, dealing with its bugs, modeling data, and building a usable flow helped me understand the theory. University taught me to develop a way of thinking that can adapt to new technologies rather than memorize just one tool.

I strengthened my backend foundations through hands-on work with C#, ASP.NET Core, Web API, and SQL Server. I focused on how application layers, database relationships, and client-facing APIs fit together. Bringing those lessons into my own projects has been the natural continuation of this training.

My software testing experience at Artiwise CXM taught me to look at a working feature from more than the developer's point of view. I worked on test scenarios, expected behavior, bug reporting, and reproduction. Working with Cypress, Playwright, and TypeScript showed me how even a small automated test can contribute to a reliable product.

My internships at Netoloji and İdea Teknoloji gave me a chance to see how different teams work. At Netoloji, I became familiar with business processes and the role software plays within an organization. At İdea Teknoloji, work involving Python and Pandas brought me closer to data analysis. These experiences helped me look at a problem from product, process, and data perspectives.

I build data-driven applications with C#, ASP.NET Core, Web API, Entity Framework Core, and SQL Server. When implementing a feature, I think beyond the endpoint: how data is stored, where authorization belongs, and how the client receives a clear response. Mülken and my portfolio are among the projects where I have applied this end-to-end approach.

I work with Python, Pandas, and SQL to clean datasets, frame useful questions, and present results clearly. I see data as more than a report: it can support better product decisions. I want to deepen these skills and bring them together with software development.

When writing test scenarios, I consider both real user flows and possible failure cases. Cypress and Playwright taught me the value of consistent, repeatable checks behind an interface. Thinking about quality from the beginning, rather than leaving it until the end, is part of the software I want to build.

In interfaces built with Next.js and TypeScript, I care about readability, accessibility, speed, and visual consistency. In this portfolio and my other projects, I try to connect backend and interface without placing unnecessary work on the user. I appreciate striking design, but I think its real value shows when the experience also feels effortless.

I want to grow in a team where I can take responsibility for products used by real people. I am especially interested in the connection between backend development, responsible use of data, and software quality. I know there is still much to learn, so I keep strengthening the fundamentals and testing what I learn in working projects.

In the long run, I hope to become an engineer who can shape the technical architecture of an idea while understanding its user experience, communicate clearly with a team, and take responsibility for the work after it ships. The writing and projects here are notes from that journey, not a finish line. You can reach out with an idea, a collaboration, or thoughtful feedback.