There was no predefined roadmap.

I had to figure out what to learn, what to build, and where to go next.

I started with the fundamentals and gradually moved deeper into:

APIs. Databases. Authentication. Architecture. Transactions. Performance. Frontend systems.

Over time, I became less interested in simply making things work.

I wanted to understand why they work — and what happens when they don't.

That shift changed the way I approached engineering.

Today, I don't see software as a collection of functions.

I see systems.

How data moves.

How services communicate.

Where failures happen.

How state changes.

How databases behave under load.

How systems can grow without becoming difficult to maintain.

Backend engineering became where my curiosity naturally went deeper.

But I also care about the other side of software — interfaces, interaction, motion, and the experience a product creates.

Engineering and creativity don't have to compete.

For me, they are part of the same work.

I didn't take the usual path into software.

And I don't think taking a different path is an achievement by itself.

What matters is what you do with it.

For the past three years, I've chosen to learn independently, build continuously, and keep going deeper without a predefined curriculum.

That experience taught me something more valuable than following a roadmap:

how to create my own.

I'm still learning.

And I intend to stay that way.

I'm not looking for a title just to have one.

I'm looking for the right environment.

Real problems.

Real systems.

People I can learn from.

Challenges that push me further.

The path I took was different.

But it gave me the ability to learn independently, stay curious, go deep, and keep building when the answer isn't obvious.

I don't need an opportunity because of my story.

I need one to show what I can build.

And I'm ready for it.