#about
back to home ↗I became a software engineer almost by accident.
I didn't start with a grand plan. I started with one programming course I happened to enjoy, and kept following the next layer of technology I didn't yet understand.
I'm Zeeshan Ashraf, a senior full-stack engineer who leads SaaS, MVP, and AI product builds for founders and small businesses. I've been building software professionally since 2018, and I work across the whole product: scope and architecture, NestJS, Node.js, TypeScript, Next.js, and PostgreSQL, AWS infrastructure, CI/CD, and DevOps.
#story
2016 · The accidental start
I got into BS Computer Science at UET's KSK campus when the programme there had just started. It wasn't my first preference; my merit placed me there. I honestly didn't know what a Computer Science graduate did. I thought I might end up working somewhere as a computer operator.
Year one · Programming Fundamentals
Then one course changed things. I liked that programming hands you a problem and says: figure it out. Break it down, try something, debug it, make it work. That loop hooked me.
Hostel · Badminton and programming
Hostel life at KSK was quiet. The internet wasn't great and there wasn't much to do, so my days revolved around two things: badminton and programming. Teachers like Sir Amjad and Sir Fahad pushed me to take projects seriously instead of doing just enough to pass.
2018 · First apps, first paying clients
I taught myself Android, built small apps and published some on the Play Store. They were simple, but seeing something I built go live felt huge. By 2018 I was being paid for Android work on Fiverr, the first proof that someone outside university valued what I could build. All of this was before AI coding assistants: documentation, Stack Overflow, and a lot of trial and error.
2019 · A job before graduation
Near graduation I set one rule: I wouldn't spend a single day after university working out what came next. I had my first software job before I graduated, as a full-stack engineer working mostly on Android, with Node.js APIs on the side.
Since · The scope kept expanding
Every layer I understood made me curious about the next one: mobile, then enterprise systems and databases, SaaS products, AWS and cloud infrastructure, startups and DevOps, and now AI products and AI-native engineering.
Today · Leading product builds
Today I lead product builds for founders and small businesses, from the first MVP to production on AWS, and I stay hands-on in the code. I still work the way I started: curiosity, followed by consistency.
The longer version: I thought I would become a computer operator
#what-that-means-for-you
Because I learned each layer by shipping it, I can lead the whole product: scope and architecture, the frontend and backend, the AI features, and the AWS infrastructure they run on. I can also join your team and work hands-on wherever you need a senior engineer.
- SaaS MVP Development: From idea to a production MVP on AWS: the one workflow that proves your product, built properly and ready for real users.
- AI Product Development: AI products and AI features that work in production: LLM integrations, document and OCR pipelines, and automation on a reliable backend.
- AI-Native Engineering: I build AI products, and I build with AI: Claude, MCP, skills and subagents in a workflow where a senior engineer stays accountable for every line.
- Technical Lead for Your Product: When you need more than a developer: someone to own the technical side of your product, from scope and architecture to hands-on delivery.
- AWS & DevOps for Small Teams: AWS infrastructure, CI/CD and production hardening for startups and small teams that need reliable deployments without a dedicated DevOps hire.
Building something?
Building a SaaS or AI product and need someone to lead the build, or a senior engineer hands-on? Let's talk.