Principal Engineer
Osama
Sets the architecture behind Midwave AI builds — and keeps it fast under real load.
Remote · Pakistan
Booked on active builds
Architecture
Owns system design
Core Web Vitals
Performance budgets held
Zero-downtime
Deploys & migrations
Profile
About Osama
Osama is the engineer who decides how a system is put together before anyone writes a feature. He works from the data model outward: what the domain actually is, where state lives, what has to be transactional, and what can be cached. That ordering is why Midwave AI projects tend to stay fast as they grow instead of needing a rescue at year two.
He owns the parts of a codebase nobody wants to inherit badly — authentication, background jobs, migrations, deployment topology — and he leaves them documented. When a feature team hits something genuinely hard, he pairs on it rather than handing down a verdict.
Focus areas
Most performance problems are architecture problems that were still cheap to fix six months ago.
Architecture
The stack I own, layer by layer
Layer 01
Interface
- React Server Components
- Design-system components
- Accessibility & keyboard paths
- Core Web Vitals budgets
Layer 02
Application & API
- Typed REST / GraphQL contracts
- Validation at every boundary
- Authn, authz, and rate limiting
- Background jobs & queues
Layer 03
Data
- Normalised relational modelling
- Reversible migrations
- Query plans and indexing
- Caching and invalidation strategy
Layer 04
Platform
- Reproducible environments
- CI/CD with preview deploys
- Logs, traces, and alerting
- Backups and tested restores
Boring beats clever
Conventional patterns the next engineer already knows, so the codebase survives a change of team.
Budgets, not opinions
Performance targets are numbers checked in CI. If a PR blows the budget, the build says so.
Secure by construction
Validation and authorisation live at the boundary, so a missed check in a feature cannot become a breach.
Review as teaching
Every review explains the why. The goal is a team that needs fewer reviews, not a gatekeeper.
Capabilities
Where the depth is
The work Osama is trusted with on an engagement, and how confident we are handing each of them over.
System architecture
96%Service boundaries, data flow, and failure modes designed up front.
TypeScript & Node.js
94%Typed end to end, from the database row to the rendered component.
Performance engineering
92%Profiling, caching strategy, and budgets enforced in CI.
Cloud & infrastructure
88%Reproducible environments, observability, and safe rollbacks.
Security engineering
90%Authn/authz, input validation, secret handling, dependency hygiene.
Way of working
How Osama works
01
Model the domain
The data model comes first. Get the entities and their relationships right and half the hard decisions disappear.
02
Draw the seams
Define the boundaries and contracts between parts of the system, so teams can work in parallel without collisions.
03
Prove the risky part
Whatever is most likely to break the plan gets a spike in week one, not a discovery in month three.
04
Instrument it
Logs, traces, and budgets ship with the feature. A regression should page us, not the client.
Toolbox
Day-to-day tools
Services