Start with the problem, not the stack.
The tools are a means. I figure out what a problem actually needs — then pick, or learn, whatever gets it shipped. Angular one year, on-chain integrations the next.
About
A generalist, on purpose.
I'm a software engineer who refuses to be defined by a single stack. Handed a problem, I work out what it really needs — a React frontend, a C# service, an on-chain integration, a desktop app, a two-month MVP — and I ship it.
Six years in, that range is the point. I've picked up new stacks on the job under deadline, rebuilt critical systems from scratch, and now lead a team building software BMW depends on. The code is only half of it: I hire, review, mentor, and stay the calm one when production is on fire.
How I work
Four things I hold to.
Ship, then harden.
Get it in front of real users, then stabilize and raise the bar. A two-month MVP taken to production beats a perfect thing that never ships.
Raise the floor for the team.
Standards, review, tooling, hiring, mentoring. I lead a 4-engineer team — my job is making everyone around me faster and safer, not just writing code.
Use AI like an engineer.
I rolled out Claude Code org-wide with a structured CLAUDE.md hierarchy and custom commands. Leverage, applied with judgment — not hype.
Capabilities
Evidence, not identity.
A broad toolkit picked up across real projects. The list is long by design — none of it is the point on its own.
Languages & frameworks
TypeScriptReactNext.jsAngularNode / ExpressC#Python
Mobile & desktop
IonicElectron
Data & infrastructure
PostgreSQLSupabaseLinuxDigitalOcean
Web & chain
Ethereum / Tron integrationdApps & walletsWeb VitalsLighthouse
AI engineering
Anthropic SDKClaude CodeMCP
Practice
TypeScript strictnessESLint / PrettierHuskyMonoreposCode reviewTechnical hiring
Education
- BSc, Computer Science
- FAST — NUCES, Lahore
- 2015 — 2021
- Google Project Management (Specialization)
- Coursera
- 2025