How I built FieldOps:
from the problem to a
complete platform.
A full-stack project designed to showcase architecture, product thinking, quality and technical decisions in a real-world operations system.
Model a complete operation,
not just an interface.
Manage requests, quotes, work orders, visits, technicians, invoices and payments in a single system, while keeping data isolated per organization (tenant) and permissions controlled by role.
Product
Complete, end-to-end flows.
Architecture
Clear separation between domain, application and infrastructure.
Experience
Portals tailored to staff, technicians and customers.
A foundation built to grow.
A layered architecture that clearly separates responsibilities, eases maintenance and lets the system evolve without touching the business core.
- Clean ArchitectureWell-defined layers with low coupling.
- Tenant isolationData isolated per organization.
- Role-based accessAccess control by role and branch.
- Auditable actionsKey events are logged.
- Versioned database migrationsVersioned and reviewed migrations.
Chosen for capability, not hype.
Frontend
- Angular 22.1
- TypeScript
- Signals
- RxJS
- PrimeNG
- SCSS
Backend
- .NET 10
- C#
- CQRS
- DDD
- EF Core
- REST APIs
Data & infrastructure
- PostgreSQL
- Docker Compose
- GitHub Actions
Quality
- ESLint
- Prettier
- Tests (unit and integration)
- Code review
- Audit trail
Every feature started with
explicit decisions.
Design, business rules and acceptance criteria before writing any code.
- DesignMockups and states
- SPECRules and scope
- ArchitectureContracts and data
- ImplementationFrontend and backend
- AuditQA, security and accessibility
The challenges that shaped the project.
Multi-tenancy
Prevent data from leaking between organizations.
States and transitions
Keep requests, quotes, jobs and visits consistent with each other.
Role and branch permissions
Authorize both the interface and every server operation.
Traceability
Log important changes without exposing sensitive information.
Built as if it were going to production.
- CI for frontend and backend
- Migrations reviewed, never applied automatically
- Per-organization isolation checks
- Tests for permissions and critical flows
- Visual, responsive and accessibility review
I designed the product and
also built its foundations.
I defined the flows, designed the experience, modeled the domain and built the full-stack architecture, using an AI-assisted iterative process validated through technical reviews.