Healthcare & education · 1 min read
PhysioMaster: collaborative product delivery and team coordination
I worked with another engineer across PhysioMaster’s backend, user application, and administration interface, while coordinating tasks and meetings across the team.
- My role
- Collaborative engineering and team coordination
- Project scope
- Client/product work · private source
Result and scope
Collaborative backend and interface work, alongside coordination of team tasks and meetings.
The main responsibilities in this workflow.
- User and administration applications
- NestJS authentication and application modules
- Education / scenario / exam / practice workflows
- Persistence, queued work, and communication
Working across three applications
I worked with another engineer across PhysioMaster’s backend, user application, and administration interface. I also coordinated team tasks and meetings, keeping work across the three applications connected.
A user-facing feature depends on the backend contract and the administration workflow behind it. My role combined implementation with discussing the scope, tracking tasks, and coordinating the work across those interfaces.
The application behind the interfaces
The NestJS backend contains authentication, education, scenario, exam, practice, and chat modules. It uses MongoDB, Redis, Bull queued work, and WebSocket support, with separate user and administration applications.
The project brought together content and learning workflows, application state, and communication. Contributing across the applications meant following how a backend change affected the people using and administering the product.
Shared implementation and delivery
Technical work was shared with my collaborator. I managed tasks and meetings alongside contributing to the applications, giving the team a place to agree what a feature needed and how the pieces would fit together.
This project extends my experience beyond commerce and trading into a product with education, practice, and assessment workflows.
Project notes
Collaborative product work; source is private. This account covers the implemented applications and my team-coordination role. Later proposals and clinical outcomes are outside this case study.