Available for new projects· updated September 2026
I'm Owais Raza, a software engineer. I design and build production backends and internal platforms — the data models, integration boundaries, and operational choices that decide whether a system grows with the business or fights it.
Production systems in daily business use
Backend architecture, owned end to end
Internal platforms, from schema to deployment
Load-tested and observable before launch
These are not portfolio demos. Each is a production system serving a real business, and each writeup walks through the decisions behind it — the options I considered, the one I chose, and the tradeoff I knowingly accepted. What a system does matters less than how it was reasoned about, because the reasoning is what you're actually hiring.
An internal platform that moves planning into Google Calendar — configurable hierarchies, one Bun process, built to cut Jira licensing costs.
An offline-first Windows billing app built with Tauri v2 and Rust for a real drone repair business — invoicing, inventory, and customers, no cloud required.
The projects above follow from a small set of defaults. None of them are aspirations — each exists because I've watched systems fail without it, and each names the cost I accept by holding it. If you want to know how I'll behave when a deadline and a shortcut are both on the table, it's written here.
The stack serves the roadmap, never the reverse.
Clever code is a liability the client pays for later.
No performance work without a baseline number.
Production is not the place for novelty.
Maintainability is a deliverable, not a virtue.
Three kinds of work, one approach: start from the business problem, choose the simplest system that solves it, and leave behind something your own team can operate and change without me.
APIs, data models, and integrations designed so that the parts most likely to change are the parts easiest to change — growth shouldn't require a rewrite.
Tools your team uses every day — planning, billing, operations — built around how your business actually works instead of bending your workflow to fit a vendor's.
Automation and AI added to existing systems where they remove real manual work, held to the same reliability standards as everything else in production.
Most engagements go wrong on the parts that aren't code: unclear ownership, silent progress, and a dependency on one person's head. I structure work to prevent all three. You own everything I produce — code, infrastructure, documentation — I communicate in writing you can forward to your team, and I design for handoff from the first commit. Working with me should never become a dependency on me.
The first call is a conversation about your problem, not a pitch. You describe what you're facing, I ask questions, and you leave with my honest read on whether I'm the right person for it — including when I'm not.