Professional case study · 2023-2024
OOSHMAN
Operations platform.
Built and maintained connected operational, ordering, driver-tracking and customer-registration workflows for a hospitality business.
- Role
- Full Stack Web Developer
- Focus
- Operations, ordering and delivery
- Stack
- Laravel, Vue, MySQL, Auth0
Several users. One connected journey.
The work connected customer ordering, staff operations and delivery rather than treating each interface as an isolated feature.
Customer
Registration, ordering and account experiences formed the customer-facing entry point.
Operations
The CMS and Laravel application logic coordinated staff-facing workflow and shared state.
Delivery
Driver tracking extended the same order journey into fulfilment and customer visibility.
One product.
Several users.
The work crossed internal operations, customer ordering, registration and delivery tracking. Each surface served a different user while relying on connected application and data workflows.
My role covered both frontend and backend delivery: translating operational requirements into Vue interfaces, Laravel application logic and MySQL-backed workflows.
Engineering approach
Several journeys. One operational system.
A representative view of how I approached the connected customer, staff and delivery workflows without claiming outcomes that were not independently measured.
Separate the users
I mapped what customers, operations staff and drivers needed to see and change, then treated their interfaces as different views of connected business workflows.
Keep rules central
Laravel application logic and MySQL-backed state remained the shared source of workflow behaviour, instead of repeating important decisions independently across interfaces.
Integrate identity deliberately
Auth0 and Google Sign-In were introduced as part of the registration journey, with the surrounding application flow kept clear for both new and returning customers.
Verify connected journeys
I checked changes through the relevant customer, staff and driver paths so an improvement in one surface did not leave an adjacent operational step inconsistent.
Connecting customer and operational workflows.
This summary separates the work I performed from outcomes that were not independently measured, keeping the case study specific without overstating impact.
Operations CMS
Built and maintained internal tooling that brought operational content and workflows into a manageable system for the team.
Ordering workflows
Worked across customer-facing ordering experiences and the supporting Laravel and MySQL application behaviour.
Driver tracking
Developed a driver-tracking application that connected delivery operations with staff and customer workflows.
Identity and engagement
Integrated Auth0 and Google Sign-In to simplify registration and implemented automated email-marketing workflows.
Full-stack delivery shaped by
real operations.
The project demonstrates my ability to work across interfaces, application logic, data and third-party identity services while keeping several user journeys connected.