Malamal
Inventory & Order Management for Small Businesses
A multi-tenant inventory and order management system built for small businesses across five industry verticals, with role-based access and plan-gated features.
Software Engineer
Specializing in full-stack applications, backend systems, and workflow automation. I build reliable systems with clean architecture, scalable APIs, and thoughtful engineering.
SELECTED WORK
Products, platforms, and tools I’ve worked on—from SaaS systems to automation and developer tools.
Inventory & Order Management for Small Businesses
A multi-tenant inventory and order management system built for small businesses across five industry verticals, with role-based access and plan-gated features.
Financial education platform with video streaming and multi-gateway subscriptions
A financial education platform with structured trading courses, subscription billing across four payment gateways, and a community for learners.

Browser-based vector drawing app with cloud sync
A canvas-based drawing app with a file-system organizer, cloud sync, and public sharing — works offline without an account.
ENGINEERING PHILOSOPHY
Great software isn't just written—it's designed. I focus on understanding systems, trade-offs, and data flow before writing code. Explore the architecture below to see how I approach building production-ready software.
Stateless Node.js / Express application cluster processing HTTP requests.
Executes core business logic, orchestrates database calls, and formats API responses.
Central logic layer for web applications and backend APIs.
Horizontal scaling requires strict stateless server design.
Career History & Track Record
Production-grade SaaS engineering, scalable API architecture, payment infrastructure, and team collaboration.
TECH STACK
I prefer technologies that are stable, well-documented, and production-tested. My focus is choosing the right tool for the problem rather than following trends.
BEYOND THE RESUME
I’m Khalid, a software engineer who enjoys understanding problems before building solutions. I often open source code just to understand how something works under the hood—figuring out why a system behaves the way it does, and finding the simplest solution that will scale tomorrow.
Lessons I've Learned
Before implementing a feature, I like understanding the business problem, constraints, and trade-offs. Better questions usually lead to better software.
I've learned that small compromises made today often become tomorrow's technical debt. I try to choose solutions that age well.
Every release is another opportunity to learn from users, improve performance, and simplify the system. Iteration is part of engineering.
Jumping into code too quickly usually leads to rewrites. Taking time to map out data flows and edge cases upfront makes the actual implementation faster and cleaner.
Quick Facts
WHAT PEOPLE SAY
OPEN TO OPPORTUNITIES
Every system tells a story. I enjoy figuring out why it works—and how it can work better. I’m open to full-time software engineering roles and selected freelance projects. If you think we’d work well together, I’d love to hear from you.