Technical Overview
For hiring teams, clients, collaborators, and engineers — how I build, ship, and maintain production systems
Where to start
This site is for everyone — recruiters, clients, collaborators, and curious engineers. Pick the path that matches why you're here.
- See flagship work
Path 1 · ~3 min
Just browsing
Get the quick picture — who I am and what I build.
- Read Northstar case study
Path 2 · ~8 min
Potential client or collaborator
Understand how I scope, design, and deliver real systems.
- Technical overview
Path 3 · ~12 min
Hiring or evaluating fit
Technical overview, evidence spectrum, and engineering depth.
- Jump to engineering depth
Path 4 · ~15 min
Engineer or peer
Artifacts, mistakes, rejected alternatives, and scale paths.
This page exists to give a clear, technical overview of how I work as an engineer.
It is intentionally concise and grounded in real systems. No marketing language. No inflated claims. Whether you're hiring, scoping a project, or just evaluating how I think — this page highlights the most relevant signal.
What I Build
I specialize in designing and delivering production-grade software systems with an emphasis on reliability, security, and long-term maintainability.
Typical work includes:
- Backend platforms and APIs designed for durability
- Cloud-native systems with clear operational boundaries
- Role-based access control and security-first design
- Systems that support real business workflows, not demos
- Codebases built to be read, tested, and extended by other engineers
How I Work
I approach engineering with a systems mindset rather than a feature-first mindset.
That means:
- Designing APIs and data models before writing UI
- Treating security, testing, and observability as first-class concerns
- Favoring explicit, boring solutions over clever abstractions
- Writing code that another senior engineer can confidently maintain
- Making tradeoffs explicit and documented
I optimize for clarity, correctness, and durability over speed alone.
How I evaluate tradeoffs
I don't expect reviewers to take my word for architectural choices. On flagship case studies I publish rejected alternatives, engineering mistakes, repo-sourced artifacts, and labeled 10× scale paths — so you can evaluate judgment, not just outcomes.
- Northstar — full engineering depth (verified from public code)
- Northstar postmortem — authorization & async notifications
- PulseForge — why it exists (design intent, pre-ship)
- PulseForge — full engineering depth
- PulseForge — rejected alternatives
Evidence Spectrum
Not every project on this portfolio is production-shipped code. Each is labeled honestly — here is what to look for at each tier.
Shipped / public code
Northstar Platform
Review the GitHub repo, tests, and case study. This is verifiable production-grade backend work.
Active build
PulseForge Platform
Architecture complete; implementation in progress. Shows domain-driven design from real coaching experience — not a finished product yet.
Design exercises
CloudSync, FinanceAI, MediConnect, ShopFlow, SecureVault
Reference architectures and systems design exercises. Useful for tradeoff thinking — not production deployment claims.
Flagship Technical Proof
If you review only two things, review these:
Northstar Platform
Backend Architecture
Production-grade service marketplace backend demonstrating defensible technical decisions.
- Modular NestJS architecture with strict TypeScript
- PostgreSQL + Prisma data modeling
- Redis + BullMQ background job processing
- JWT authentication with role-based authorization
- Audit logging, rate limiting, and observability
- Comprehensive unit and end-to-end testing
This project exists to demonstrate how I design, secure, test, and ship production-grade backend systems.
PulseForge Platform
In Development · Domain-Driven Design
Coaching platform architecture from real domain experience. Implementation in progress — case study shows design intent, not shipped code.
- Domain model shaped by years of fitness and kickboxing coaching
- Multi-tenant architecture with tenant-scoped query isolation
- Role-based coach/client model with scheduled check-ins via queues
- Architecture documented; public repo pending MVP ship
This project demonstrates domain-to-architecture translation — evidence tier increases when the public repo ships.
What I'm Strong At
- Backend system design and API architecture
- Data modeling and performance-aware querying
- Authentication, authorization, and security boundaries
- Cloud and container-based deployment workflows
- Writing testable, maintainable TypeScript
- Owning systems end-to-end in production
What I Care About
- Systems designed for durability that fail predictably and recover cleanly
- Code that explains itself through structure
- Making tradeoffs visible instead of hiding complexity
- Building software that other engineers trust in production
How to Evaluate This Portfolio
If you're evaluating fit, I recommend:
- Review the Northstar GitHub repository
- Explore the Northstar interactive demo
- Read one backend-focused case study
- Scan the resume for scope and ownership
If those align with what you're hiring for, I'm happy to go deeper.
Contact
Email: workarman9@gmail.com
Portfolio: armanhazrati.dev
GitHub: github.com/BloatedMonkey
LinkedIn: linkedin.com/in/arman-hazrati-512728183