Enterprise Field Operations Platform
Backend development and Azure cloud integrations for an enterprise platform used by thousands of field-based workers across regulated industries including facilities management and healthcare.
Proprietary commercial software. No screenshots or links. This page documents my individual contributions as part of a backend engineering role.
Context
This was an enterprise mobility platform for industries where fieldwork must be logged, audited, and compliant. The platform supports thousands of users doing work orders, inspections, and compliance tasks in real time from the field. The codebase is large, mature, and runs in a high-availability environment. Bugs here have direct operational consequences.
My role
As a Junior Backend Developer I worked across the full C# / ASP.NET Core backend and the Blazor WASM frontend, delivering features, fixing production incidents, and contributing to the CI/CD pipeline.
- ·Designed and implemented backend features following Clean Architecture and Repository pattern principles, improving separation of concerns in a large-scale codebase
- ·Integrated Azure Functions, App Services, and Storage Accounts to build scalable, reliable cloud-based data flows
- ·Built and consumed RESTful APIs across microservice and modular monolith boundaries in collaboration with cross-functional teams
- ·Debugged and resolved production incidents spanning the API, MSSQL / PostgreSQL database layers, and Blazor WASM frontend
- ·Contributed to CI/CD pipelines in Azure DevOps, improving deployment reliability and expanding automated test coverage
What I learned
Working on production software at this scale made it clear how different enterprise development is from side-project work. The discipline of Clean Architecture (CQRS, Repository pattern, clearly separated bounded contexts) stops being theoretical when you are the person debugging an incident at 2am and need to trace through layers quickly. I also learned how much of senior backend work is about the seams between services: getting contracts right, versioning carefully, and not breaking consumers. Azure DevOps pipelines went from unfamiliar to second nature within the first few months.