where I started
Electronics gave me the hardware instinct.
Circuits, signals and physical systems taught me to care about what is happening underneath the interface—not only what appears on top of it.
Muzammil Alam / Karachi / building across layers
I'm an AI and full-stack software engineer, Computer Systems Engineering student, and hardware-curious builder. I like the point where code stops being a collection of files and starts behaving like one coherent machine.
Origin / signal map
I did not pick one lane and stay there. Electronics pulled me toward hardware. Software pulled me toward systems. AI added a new layer. Product work keeps forcing all of those ideas to survive contact with reality.
where I started
Circuits, signals and physical systems taught me to care about what is happening underneath the interface—not only what appears on top of it.
where I moved
I shifted into Computer Systems Engineering at NED because software, architecture, low-level computing and product building started connecting into one picture.
where I am going
I am exploring LLMs, generative AI, agents and automation with the same question I bring to everything else: how do we make the intelligence genuinely useful?
Current operating state
Manifesto / internal notes
Normal is fine. It's just not the goal. I want enough depth to move between product thinking, software systems, AI, interfaces and the machine underneath without treating any one layer like someone else's problem.
I want to understand the machine, not just decorate its output.
I like products where interface, logic, motion and infrastructure agree with each other.
I would rather build one coherent system than five disconnected features.
I care about the strange edge cases because that is usually where real engineering starts.
My current tech tree
Where this shows up
The projects I enjoy most sit across layers: interface, application logic, data, automation, sometimes hardware, and the small decisions that make all of it feel intentional.
Open the project wallI use the journal as a place to turn experiments into explanations—AI, software engineering, build notes and ideas I want to understand well enough to write down.
Read the journalI am interested in the point where engineering meets a real user, a real business problem and a real constraint. That collision makes the work more alive.
Start a conversationFinal handshake
AI product, full-stack platform, strange prototype, systems problem, or an idea that needs someone willing to look across layers—I'm always up for the right conversation.