M. Talha Atif

I started with Android development, doing small freelance projects like a plant care app.
I used to sit in direct client meetings myself to catch up on requirements.
That's where I learned that building something a real person depends on is different from finishing a tutorial.

Then I built a side project, Moodly, that changed how I think, less about just coding, more about user experience and systems.
It taught me event-driven design with RabbitMQ.
I learned to improve user experience by cutting down clicks, not adding more screens.
I added a mood-detection based experience discovery feature, one of the standout parts of the app.

Then at Intimec, in the IGA domain, the hardest part was untangling complex business requirements: multiple approval stages, multiple approvers, multiple approval items, multiple users.
I broke that complexity into microservices through an event-driven approach, built for scalability and failure isolation.
I used gRPC to cut down latency between services.
This is where I shaped real, practical experience with microservices, gRPC, and user experience.

My working style evolved from just writing code to actually caring about the person using it.
Outside of code, I like reading about systems, backend design, and databases.
My take is simple: if you build a feature in a vacuum, you end up in a vacuum too.
You find the real pain points by being the user first, then bring your tech skills in to solve them.