Service Operations Platform at HazelSoft

Snapshot

Role: Software Engineer

Sanitized: Yes

Context

The product needed to support field service teams managing requests from submission through completion, with role-based access and third-party integrations.

Challenge

Coordinating multiple workflows across different user roles while integrating external APIs and maintaining a consistent UX.

Constraints

• Legacy and greenfield surfaces coexisting during migration.
• Third-party API reliability and rate limits affecting integration design.
• Need for audit trails and approval flows in service operations.

Architecture

A hybrid stack with Angular and React frontends, .NET and Node.js backends, and SQL Server and MySQL for persistence.

Frontend

• Angular and React interfaces for service request and field operations.
• Role-based views for different user personas in the workflow.

Backend

• .NET and Node.js services for business logic and API orchestration.
• SQL Server and MySQL for transactional and operational data.

Integrations

• Third-party delivery and mapping APIs for logistics and dispatch.
• External systems for approval and notification flows.

Data Flow

• Requests flow from submission through dispatch and approval to fulfillment.
• Status updates propagate to stakeholders via integrated channels.

Execution

Responsibilities

• Built FieldTrack24 service request workflows covering submission, dispatch, approval, and fulfillment.
• Integrated third-party APIs including delivery providers and mapping services.
• Improved existing scripts and UI flows for operational efficiency.

Delivery

• Delivered end-to-end service request workflows on schedule.
• Integrated multiple third-party APIs with error handling and fallbacks.
• Iterated on UI flows based on operational feedback.

Outcomes

• Streamlined service operations with clear workflow visibility.
• Reduced manual handoffs through integrated approval and dispatch.
• Established patterns for third-party integration that scaled to additional providers.

Leadership

• Owned feature delivery across frontend and backend layers.
• Balanced technical debt with delivery pace in a mixed-stack environment.

Lessons

Lessons are intentionally omitted in the public sanitized narrative.