I started as a freelancer. My first clients were small businesses that needed software built cleanly, delivered on time, and explained clearly. In that period I shipped project-based work end to end, including Career Connect, a full job portal with an integrated assessment module, and a multi-restaurant, multi-vendor management platform for a Saudi client, where I owned the dynamic backend and GraphQL API. Those engagements set the standard I still hold: understand the problem fully before writing a line of code, communicate clearly throughout, and hand over something that actually works.
At Algorithm, a software development company in Pakistan, I moved from individual contributor to lead engineer. I worked directly with the founders on architecture decisions, ran sprints, mentored junior engineers, and owned products from their first line to production. I built Maktab, a school management platform now serving a solid portfolio of private schools, from a blank schema to a live, fee-processing system used daily by administrators, teachers, and parents. I also contributed to Medpost, a professional publishing platform for the medical community.
Now I lead engineering at Skyware IT Solutions, where I manage a team of five and am responsible for four production products used by hotels and resorts in Germany. The products are Crito Smart PMS, Crito Voice AI, Crito iKiosk, and an IoT integration layer currently in development. Crito Voice AI I built independently, end to end, for Skyware as part of that suite. The work here ranges from backend architecture and microservices design to real-time voice agents and Electron applications on hotel kiosk hardware.
Chatevo is my own product. It is an embeddable AI chatbot platform with document ingestion, RAG retrieval, live tool integrations, and multi-tenant configuration. The core product is built; I am in final preparation for public launch.
I use AI tools in my development process deliberately and with judgment. I use them to move faster, to explore approaches, and to handle parts of the work that do not require human reasoning. The judgment about what to build, how to structure it, and whether it will hold up under real conditions still comes from the engineer. My development approach is research-driven: before building, I understand the problem space, study how others have solved it, and make deliberate choices rather than default ones.